- xwiki-users@xwiki.org - lists.xwiki.org

[xwiki-users] [Brainstorming] Home Page concept (was Re: New Page Has No Parent)
by vincent＠massol.net 06 Jan '16

06 Jan '16

Hi Edy and all, On 5 Jan 2016 at 11:52:24, Eduard Moraru (enygma2002@gmail.com(mailto:enygma2002@gmail.com)) wrote: > Hi Randy, > > From your choice of words (and your continued usage of the now deprecated > "spaces" macro on the homepage, as observed in the screenshot you`ve > provided), I understand that you still see things in terms of "creating > spaces" and "creating documents inside spaces" in 7.4 and, IMO, that`s > really the issue. > > In case you`ve missed it from the release notes, starting with 7.2, we`ve > introduced the notion of Nested Pages [1], which means that you no longer > have the notion of "pages inside spaces", but always "pages inside pages". > Technically, it is actually implemented by always creating a "space" when > you create a page from the UI, but the user should see it as if he is > always creating a page. > > = Use Case 1 = > > When your users go to your homepage and create a new page "under the Main > space", they are actually creating a nested page (old "space"), under the > homepage (document called "Main") of your wiki. If you change [2] the > homepage of your wiki to point to a different document instead (say > "Some.Other.Homepage"), I`m fairly sure that you do not want your users to > start creating new pages as children of that page (e.g. > "Some.Other.Homepage.NewUserPage"), because that is what the alternative > would lead to. > > The logic behind the original decision of handling the homepage differently > was that, even as Guillaume was hinting, the homepage is seen as the "root" > of your wiki. Creating a page from the root should result in creating top > level pages, not child pages. If you wanted to create a child page of > something from the homepage, you would explicitly do so by selecting a > parent. Not selecting a parent while on the homepage would logically imply > that you want to create a page in the wiki (i.e. top page). > > I`m curious why do you find it normal the other way around, i.e. landing on > the wiki (i.e. not navigating somewhere in particular) + creating a new > page => resulting in creating a child page of the "Main" page (which > happens to be the homepage). > > If you always create child pages of the homepage ("Main" page), on the long > run, all your URLs will be /Main/This/Page, /Main/That/Page, > /Main/That/Other/Page, etc... but ultimately, what is this "Main", and why > is it that important to drag it along in all your page URLs? (of course, > again, if you change your homepage to "Some.Other.Homepage", all your urls > will be prefixed by that!) > > = Use case 2 = > > Now, another way of looking at this would be that, for some reason, you > *really* want to keep all your content under some top level page (e.g. as > Vincent suggested, a "Content" container page), perhaps to separate it from > applications (which, for historic reasons, currently are also located in > the top level) like Blog, Sandbox, etc. or any other reason. > > The only limitation in this usecase is if you also want to use that > container page ("Main", "Content", etc.) as your homepage. In this case, > indeed, I see no other solution but to modify the createinline.vm template > or for us to drop this behavior altogether. > > --- > > Conclusion so far: > We have 2 use cases regarding a new page's parent. They can both coexist, > except that, in some cases, the 2nd use case is limited by the first use > case. If we consider this limitation to be a deal breaker, then we are left > with 2 choices: > A. Drop use case 1 (i.e. always propose the current page as parent of the > new page, regardless if the current page is the homepage or not) > B. Make use case 1 configurable (i.e. enable or disable it completely, in > case you are suffering from the limitation of the second use case; this > allows the user to decide if it's useful or not) > > Of course, if option B is what we go for, we also need to figure out where > we would put such a configuration. > > I would be in favor of option B (since I obviously believe that use case 1 > is something useful for the majority of cases), but have no idea on the > location of the configuration. > > WDYT? I agree about what you’ve said above. However I think the main problem comes from the fact that the user doesn’t know: * That he’s on a special page (home page). He sees himself/herself on the Main/WebHome page, i.e. in the Main space. * The user doesn’t realize that the home page of his/her wiki is a virtual page that can be configured to point to any page and that it just happens that by default it’s been set to point to Main.WebHome. * It can even be argued that the home page doesn’t exist and that the user is redirected to the page configured in the main wiki’s descriptor, i.e. Main.WebHome and thus when you click “+” to add a new page you’re not on the home page anywhere but on Main.WebHome. So, I see 2 choices: 1) Option A, i.e. "drop use case 1 (i.e. always propose the current page as parent of the new page, regardless if the current page is the homepage or not)." 2) Find a way to make the home page special and different from Main.WebHome. It could be a special URL as suggested by Guillaume in a previous post, such as http://localhost:8080/xwiki/bin/view/ and it would redirect to a special resource type for the home page, which would be served as a template. For example: http://localhost:8080/xwiki/home. This would be easy to implement. Of course we would keep the ability to configure where the home page of the main wiki points to in the Admin UI and /home would be used only when no custom configuration is defined so that it would still be easy for users to configure what they want to display on the home page. In order to make it simpler we could even introduce a "Home Page” entry in the Admin UI. We would also need to find some different content for Main.WebHome. I haven’t thought about all the consequences of 2) but at first sight it seems it could be something that could work and could even solve the issue we currently have of it being hard to edit. Note that the home page wouldn’t have an Edit button. Seen differently, the home page would be controllable only by an Admin, which IMO can make sense. So, all in all, I think I’d be in favor of solution 2) (unless some gotchas). Barring that, I’d prefer solution 1) instead of option B above. WDYT? Thanks -Vincent > Thanks for all your feedback so far and I`m counting on your help and > anyone else interested to reach a conclusion regarding this. > > -Eduard > > ---------- > [1] http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization > [2] > http://www.xwiki.org/xwiki/bin/view/FAQ/How+to+change+the+home+page+destina… > > On Mon, Jan 4, 2016 at 3:13 PM, Randy Havens < > Randy.Havens(a)cityofrochester.gov> wrote: > > > > So if we bring > > > back the old behavior as-is we'd still have to find a solution for > > > top-level space creation. > > > > That’s already taken care of. This is how I always created spaces before: > > (this is a screenshot from my 7.4 instance, so I know that it is still an > > option) > > > > [cid:image001.png@01D146C6.3625A240] > > > A suggestion I had now that nested spaces are activated by default was to > > > make the home page of the wiki be "above" every other space. Said > > > differently, the home page would reside directly at > > > https:///xwiki/bin/view/ > > > without anything else being mentioned. From that page you'd be able to > > > create top-level spaces, and every other page would behave as expected, > > > including Main.WebHome. I think this is what would feel the most natural, > > > but it causes many underlying issues, notably because a page with no > > > document reference cannot really exist in XWiki right now. > > > > I agree. This seems to be a sensible solution. > > > > > > image001.png (23K) < > > http://xwiki.475771.n2.nabble.com/attachment/7597376/0/image001.png>

3 2

[xwiki-users] migrating from .war to Debain apt package
by shouldbe q931 06 Jan '16

06 Jan '16

Hi, I'm struggling with migrating a 6.3 .war instance to a Debian APT/package 7.3 instance. I had hoped I would be able to install as per http://platform.xwiki.org/xwiki/bin/view/AdminGuide/InstallationViaAPT choosing the xwiki-enterprise-tomcat7-mysql package, then edit hibernate.cfg.xml to point at the existing (external) MySQL instance hosting the database, then edit server.xml, xwiki.cfg and xwiki.properties to match the previous. The new instance connects, and after editing xwiki.cfg, I can login as superadmin, the previously setup LDAP auth not working), I was expecting to see the xwiki updater run, but it did not, and the top bar of xwiki is empty, it only has the logo on the far left and the three little lines on teh far right under which the only option is logout. Do I need to to do a .war update to get it up to 7.3 before migrating to a Debian APT/package instance ? or is there something that I have missed ? Cheers

3 10

[xwiki-users] Path-based wiki access and Domain-based wiki access
by Hugor Mbuta 06 Jan '16

06 Jan '16

Hi All, I created one wiki page on my windows 7 machine with some sub pages and some documents inserted so everything is good so far. But I would like to change URL name of wiki page at moment it’s call: http://localhost:8080/xwiki/bin/view/Main/?srid=EiLr8Qmn I would like to change that by a pretty name instead the the default path and also able to access the wiki page from another computer on my network. I checked some document on the xwiki.org regarding Path-based wiki access and Domain-based wiki access. The documentation is not enough clear for me so someone can give the full steps to change the path and make this access everywhere in the network, please Regards, Thanks H. Hugor Mbuta IT Support Analyst direct dial +44 (0) 20 7332 9995 H.mbuta(a)gasstrategies.com [http://www.gasstrategies.com/gslogo.jpg]<http://www.gasstrategies.com> Gas Strategies 10 St Bride Street London, EC4A 4AD +44(0) 20 7332 9900 www.gasstrategies.com<http://www.gasstrategies.com> This e-mail, including any attached files, may contain confidential and privileged information for the sole use of the intended recipient. Any review, use, distribution, or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive information for the intended recipient), please contact the sender by reply e-mail and delete all copies of this message. Please note that we do not accept any responsibility for viruses and it is your responsibility to scan the email and attachments (if any). Gas Strategies Group Limited is a company registered in England and Wales under company number 2225820. Gas Strategies is the trading name of Gas Strategies Group Limited. Registered company address: 10 St Bride Street, London, EC4A 4AD

2 1

[xwiki-users] Why deleted page still appear in the UI?
by Giordano Ninonà 06 Jan '16

06 Jan '16

Hi users, I'm developing a java component that offer APIs accessed through script services to perfom modification to the wiki. When I delete a document (thus the related page I guessed) from my java code with the "*.deleteDocument(doc, context)*", on my browser I see the last modification as a page deletion but the page is still accessible on the tree representation. The XWikiDocument's method ".setHidden(true)" solve my problem, but I can't catch the relations between xwiki pages-->Documents-->Document reference and how to handle deletion of non-terminal pages preserving the information contained in them like: the wiki and the nested page to whom they had been belonged, the content and the comments. Thanks for your help, Giordano.

4 11

[xwiki-users] [myxwiki] new wiki request
by Metamechanic 05 Jan '16

05 Jan '16

Hi. I’d like to register a second new community Xwiki please. Description: It is a wiki called Enough For All. It is designed to be an open community repository for information related to poverty at all levels. It aims to have a social network and collaboration aspect to it. Owner name: Adam Duus Username: metamechanic Wiki name: EnoughForAll Thank you. Regards, Adam Duus.

2 1

[xwiki-users] New Page Has No Parent
by Randy Havens 05 Jan '16

05 Jan '16

When I create a new page in my Main space, the "Parent" field defaults to empty, but when I create a new page in any other space, it defaults to the name of that space. When a user tries to post a new page with the parent empty, they get an "access denied" message, but if you put "Main" in the parent it works as expected. Is there a way to default this value to "Main" when not in another space, instead of having it default blank? This wasn't an issue up to XWiki 7.1.2, but it is an issue in 7.3 and 7.4 - when nested pages started getting worked on. -- View this message in context: http://xwiki.475771.n2.nabble.com/New-Page-Has-No-Parent-tp7597344.html Sent from the XWiki- Users mailing list archive at Nabble.com.

5 10

[xwiki-users] XWiki java client authentication
by Bryn Jeffries 05 Jan '16

05 Jan '16

Hello, I need to write a small Java utility to interact with my XWiki server - it's main purpose is to take a file containing paths to various files, and then upload (POST) them to the server. It looks as though this cannot be done from within the browser directly since sandboxing prevents working with file paths directly. Having read through the RESTful client information (http://platform.xwiki.org/xwiki/bin/view/Features/XWikiRESTfulAPI) I am not sure I need to completely go down this route as I don't need access to representations of the XWiki objects. AFAICS I will simply need to GET and POST to specific URLs of the wiki. However, I would greatly appreciate advice on how best to handle authentication. Guest users are not allowed, so username and password should be provided, and in some way a session needs to be maintained. Are there any simple examples for logging in to XWiki and maintaining a session from within a Java client? I'm wondering if I still might need the RESTful API for this, but the documentation doesn't really cover this in detail. Thanks, Bryn

2 1

[xwiki-users] CMS feature: to define a document manual tree and then export the pages as PDF
by Andrea Belli 05 Jan '16

05 Jan '16

Dear all, I'm a happy XWiki user since 2013, deployed as internal wiki for a tech team. Now I'm evaluating the usage of XWiki as CMS for writing product documentation. In the past I used Alfresco but I think the XWiki approach is more flexibile and easy for non-technical guys. The latest version I tried was the 6.4 which it works pretty well for all the use cases I'd like to fit, except for this need: I'd like to write a set of pages, and then arrange them in a structured manual with a table of Content, i.e. using a tree view and moving pages from a section to another, and then export them as PDF. For example, I'd like to write 4 wiki pages, and then I'd like to create a PDF picking up three of them defining a table of contents such as * page1 o page4 o page2 * page3 I saw this feature as plugin for Confluence: is this available in XWiki or scheduled for one of the next releases? Best Regards Andrea

2 1

[xwiki-users] [myxwiki] new xwiki request
by Metamechanic 04 Jan '16

04 Jan '16

Hi. I’d like to register a new community Xwiki please. Description: It is a wiki called Global Effort, which stands for Global Energy Futures, Foresight and Transitions. It is designed to be an open community repository for information related to global energy futures. (Futures as in scenarios, backcasting, forecasts etc and not stock market speculation.) It aims to have a social network and collaboration aspect to it. Owner name: Adam Duus Username: metamechanic Wiki name: globaleffort Thank you. Regards, Adam Duus.

2 1

Re: [xwiki-users] import of a XAR and versions
by vincent＠massol.net 04 Jan '16

04 Jan '16

Hi Peter, No it’s not been fixed in 6.4.x. Maybe Thomas has decided not to backport it since it could a bit dangerous? Thomas? Thanks -Vincent On 4 Jan 2016 at 11:02:58, Peter Huisman (p.huisman@ximm.nl(mailto:p.huisman@ximm.nl)) wrote: > Hi Vincent, > > Thanks for the prompt response and great to hear that it is already fixed! I am wondering (since I can’t find it easily) if you also have fixed in the latest 6.x series since we are not ready to move to 8. > > Br, > > Peter > > Op 4 jan. 2016, om 10:59 heeft vincent@massol.net(mailto:vincent@massol.net) het volgende geschreven: > > Hi Peter, > > On 4 Jan 2016 at 10:55:49, Peter Huisman (p.huisman@ximm.nl(mailto:p.huisman@ximm.nl)(mailto:p.huisman@ximm.nl)) wrote: > > > > > Hi, > > > > > > I have a question regarding the import of a XAR. > > > > > > When we do an import of a XAR (exported with the History), we have noticed that - when the document NOT contains an attachment - the version history of the document is identical to the original (obviously as expected). However, when the document contains an attachment, it look like a new version of the document is created with the comment being identical to the last available comment. We have experimented with file an DB store (since we have multiple servers in use with different setups) but that does not solve this issue. > > > > > > 1 - Is this the expected result? > > > 2 - Is there a way to work around this (in our case) unwanted result? > > > > > > Thanks in advance for looking at this. > > > > I think you’ve experienced http://jira.xwiki.org/browse/XWIKI-9960 which we’ve just fixed. > > > > Thanks > > -Vincent > > > > > Br, > > > > > > Peter

3 4