Hi, Matt! See answers below.
Fri, 10 Aug 2012 20:07:31 -0400 от Matt Lamoureux <mml...@gmail.com>: >Hi all, > My department is migrating from JSPwiki to Xwiki. We want to keep > things simple, so when importing your war file I did not import the sandbox > or blog spaces. That left Main, Xwiki, AppWithinMinutes, and Dashboard. > AWM is fine, but I found out the hard way that Dashboard and Xwiki both > contain parts of the software, so I can't delete or hide them. First of > all - is that accurate?Actually you can delete them also, as far as I know. But some scripts will really "keep things simple", I'd say MUCH simplier, than without them. So, I'd advise to play with all this staff first :-) Sandbox you can delete also, but just think about some playground for users who see XWiki first time. Sometimes it was more useful than useless for me. > My second question is around the Main space. I thought we could import > our files directly into that space, but apparently not - we had a page > called "Search" which appears to have overwritten the search results page. > I couldn't find any documentation about best practices when importing - > like file names to avoid, etc. Do I have to create a brand new space, > leaving Main, Dashboard and Xwiki alone? I just worry people will start > clicking around and editing or creating pages in one of those other > spaces... > My experience says following: LEAVE XWiki's Spaces (e.g. Main and XWiki), customise it as you need AND use other spaces for data. In the future, in a case of upgrades or moving/renaming/deleting spaces you would highly appreciate keeping data OUT of sctripting :-) To avoid "smart hands desease" - just restrict edit rights to Main and XWiki (maybe some more) spaces. Simple view rights would make your scripting almost unbreakable. :-) There is more complicated way - change default page on XWiki start and build everything you need "from scratch". But depending on your future plans I'd recommend just to keep it in mind, but not implement at once: it is set globally for XWiki. For example, in a case of XEM, each Workspace would have non-standard default page, that may cause additional work in template customization. Probably, there are another ways to do this, but I didn't explore it yet. As a conclusion: much-much more easier to customise existing spaces-pages to you needs, especially from the very beginning. > Any advice or information would be greatly appreciated! > > Thanks! > - Matt L. > > > I really don't want people to see the other spaces (to avoid confusion). I > had thought that the main parts of Xwiki were kept in the Xwiki space, so I > did the import into Main. However, that appears to have caused some other > issues, since we had a page called "Search" which seems to have overwritten > the default search results page. > _______________________________________________ > users mailing list >users@xwiki.org >http://lists.xwiki.org/mailman/listinfo/users > Keep in mind NATIVE XWiki structure: - Spaces - Pages for XE - Workspace/subwiki - Spaces - Pages for XEM So, stripping you data into this logic would make possible all benefits migration to XWiki. BTW, besides the fact, that XWiki has access rights at page level even for each user, I use this very seldom. Much easier to use Groups and set access rights to Spaces. As for "confusion": if you will check Document Index link in top menu - you will see ALL spaces and pages you have view access rights. In my case - I didn't have any confusions at this point. But you're free to make a little Guide to users :-) It helps much. Other way is to customise XWiki's appearance and remove "extra" links. BUT if someone smart will use direct links - it won't help much: someone smart will have access according to his access rights :-) Kind regards, Dmitry _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
