I've freshly installed XE 1.8.1 and am pleased to see that the email
registration process has been fixed.
I want to use XE for an admin wiki in a school environment and do not wish
to have students being able to register.
Ideally, I would like to have users self-register and then have to wait for
admin approval to activate account.
Is there anyway to do this with XE? Otherwise, what is the best strategy for
restricting user registration?
Thanks
Chris Ellis
The XWiki development team is pleased to announce the release of XWiki
Enterprise 1.8.1 and XWiki Enterprise Manager 1.6.1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
This release contains 118 big bugfixes and enhancements. Most of the
modifications are targeting the general replacement of old 1.0 code
and content by 2.0 syntax and architecture and the stabilization of
XWiki.
Summary of changes since XWiki Enterprise 1.8 :
* Many WYSIWYG bugs fixed and improvements
* Many 2.0 syntax bugs fixed
* Many 1.0 to 2.0 conversion bugs fixed
* Several XMLRPC and REST, LDAP, Office importer and Wiki Explorer
bugs fixed and improvements
* Many bug fixes in many other places
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise181
and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM161
Thanks
-The XWiki dev team
Hi,
Is there a way, in a multi-language xwiki, to show a page in default
language (in our case English) if no translation of that page is
available in the language of the session the visitor is in. It now
show a empty page in all languages that do not (yet) have a
translation for a page?
Gerritjan
Hi!
As the beginning I would like to say Hi! everyone, I'm new to XWiki.
I've read this guide:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/WritingComponents
I've got the main picture about this but how can I compile this component
(Should I?) and how can I include it in my XWiki installation?
So for example: I've make a HelloWorld component and I would like to use it
in a wiki page like this (using groovy):
<%
def greeter = com.xpn.xwiki.web.Utils.getComponent(org.xwiki.component.HelloWorld.ROLE);
println greeter.sayHello();
%>
How can I do that? What are the missing steps I need to do (currently i'm
having a directory with tree like this:
pom.xml
src/main/java/org/xwiki/component/HelloWorld.java
src/main/java/org/xwiki/component/internal/DefaultHelloWorld.java
src/main/resources/META-INF/plexus/components.xml
src/test/java/org/xwiki/component/HelloWorldTest.java
)?
Thanks for reading and your guidance!
--
Regards,
Bálint Kriván
Hi Ludovic,
Yes the hierarchical design used by Curriki would work for me, the layout is fine, but the implementation is a bit disconcerting, so if there is a way to work round the negative UI issues...
The aspects that I find are disconcerting and would be disorienting or frustrating for users with the example Curriki page is:
1. The noticeable lag between clicking on a tree link and the next level opening. My internet connection isnt *that* slow and I'd guess even at intranet speeds it would still be noticeable. Taking a guess maybe the page needs to have the tree/toc preloaded/cached to avoid this lag or some other approach, but the pregnant pause waiting for the toc/tree part of the screen to redraw is somewhat disconcerting.
2. Also the links themselves - one appears to need to click on a very specific location to get the link to open to the next level (and you know as well as I do that some users have trouble controlling their mice) - i.e. the little arrow, but if one clicks on the folder icon it also opens albeit slower, but if one goes a little bit further then one sees a popup tooltip obscuring the text and when one clicks on the text it goes to that linked page. Really its not immediately clear to a user what to click on to get the tree to open - if it works like Windoze (file) explorer then its probably an approach familiar to most GUI users. If you intend to implement tooltips IMO definitely include an option to disable them because power/frequent wiki users will get irritated by them quickly.
3. Maybe my eyes are being deceived by the very obvious screen refresh/redraw delay but it almost seems as if the web page contents moves up or down depending on which tree link one clicks on. IMO if the user expects a page to open then the menu must remain in a static position on the screen and the link they clicked on mustnt suddenly move a few cm up or down the screen because that is disorienting, rather leave it to the user to scroll up or down the page from their last viewing position if they want to.
If the xwiki team can work around the issues exhibited by Curriki, in their Xwiki implementation, I think it would be very usable.
I look forward to seeing the results of your efforts.
Thanks for your interest,
Cheers
----- Original Message -----
From: "Ludovic Dubost" <ludovic(a)xwiki.org>
To: "XWiki Users" <users(a)xwiki.org>
Sent: Wednesday, April 8, 2009 11:19:53 PM GMT +02:00 Harare / Pretoria
Subject: Re: [xwiki-users] How to navigate user pages as tree structure from main page?
I'm currently working on some different ways to implement the breadcrumb
and a Table of Content on a project.
It's using some of the ideas that are currently implemented in Curriki.
See this example:
http://www.curriki.org/xwiki/bin/view/Coll_curriki/RefineyourSearchforLearn…
Hi,
Is there a explanation on how to set the rights on the xwiki space in
a site that has registration enabled.
If I disable view rights for "non registered" users on xwiki space the
site skin is no longer used
If I enable view rights on xwiki space, every non-registered visitor
can see PROFILE PAGES of registered users (they are in the XWIKI space)
How should I deal with this, probably a mistake in our software or a
mistake in Xwiki?
Gerritjan
Hi Lee,
I'm no expert on this by any means, but I suspect that removing the Admin page (I assume you mean the XEM main page) will cause you problems in that you would find it difficult-impossible to administer your created Wikis (i.e the wikis in your 'farm')
Why not just give your users the direct link to their wiki home page they want and leave the XEM wiki admin login for yourself.
In my case I havent setup host/domain names (the default XEM approach) so I am using the URL approach to get to my wiki home pages - i.e. the pages the users are going to see and work in.
So for me I use (assuming I'm at the server) I use custom port 8380 so you may need to change this your side, and of course the access IP as well.
http://127.0.0.1:8380/xwiki/bin/view/Main
gets me to the Welcome to Wiki administrator page - the farm management page
I then created ia 2 wikis - one called 'home' and the other 'projects' so now.
http://127.0.0.1:8380/xwiki/wiki/home
gets me to my first wiki of the farm - which I called home
http://127.0.0.1:8380/xwiki/wiki/home
gets me to the project specific wiki of the farm
---------
to get the above working requires about 3 line edits in xwiki.cfg
the docs for it are at http://manager.xwiki.org/xwiki/bin/view/AdminGuide/AccessWiki
---
Alternatively there is the host/domain approach where I could have something like
home.mydomain.local
or projects.mydomain.local
This is the default approach used by XEM. It looked to be a bit more RTFM to setup so I've skipped trying it for now.
See http://manager.xwiki.org/xwiki/bin/view/AdminGuide/AccessWiki#HThedomainnam…
HTH
Cheers
>I want the first page that comes up on this wiki to be a custom page I made in lieu of this admin page.
>I tried to just edit the page, but it started throwing velocity exceptions...
I am out of the office until 04/14/2009.
Note: This is an automated response to your message "users Digest, Vol 21,
Issue 19" sent on 4/8/09 23:17:49.
This is the only notification you will receive while this person is away.
I tried to upgrade my XE version to XEM. I got it working.
I setup 5 sites plus what I call the "control" site.
Everything seemed to be going well until Last night. One of the
Farm sites (1 of 5) is no longer displaying it's home page correctly. When I
type in it's url,
It displays the "control" site. The other 4 farm sites come up ok as usual.
How do I fix this? Is there some parameter someplace that identifies the
wiki site that is
The control site and which ones are farm sites?
Please advise.
Lee
Hi JV and Vincent
Fabulous to hear :-) Yes that's IMO useful as a "tree" index" and would also be workable but it would be clumsy for what I really desire as a wiki nested page navigation menu.
To be workable from the main page or subpages IMO one needs a subset of this in the side panel to work as a hierarchical table of contents - think like the windows explorer file manager view when it shows directories - the drive letters and names would be the spaces, then the next link down would be the first wiki page of that space and then the next drill down would be the next wiki page below the first wiki page.
As one navigates to the first wiki page further deeper wiki page levels would be shown. The way it works with Dekiwiki is as one drills deeper the upper levels displayed are "closed" - i.e all upper levels are indented to the 0 position - so that the hierarchy width doesnt grow wider than the initial panel size.
Also looking at the tree display currently in XE 1.8, to be practical and not confuse users when used as a sidebar, the wiki page navigation panel one would need the option of "hiding" certain spaces. Many of the spaces created by the application import for example one doesnt necessarily want to display, often just the user spaces would be what is desired to display. So if one creates say a 'department' space then a user might want to browse around in that to navigate to a specific page they want quickly.
Really what I mean is like in XE we have spaces which in turn have pages, I'd like within each space to have subpages of main pages which are intuitive for users to navigate, almost like subspaces within a main space.
At present it appears to me as if all wiki pages within a space are at the same hierarchical level, which of course makes managing multiple pages on a certain topic/theme a bit of a challenge.
Also having this tree space context aware would be wonderful so that if one is in a space then the "tree sidebar" navigator shows only the pages in the space. One could have a main menu option so that a user can always get back to the home/main page but then again the "quicklinks" could also be used for that, but it might be more intuitive if its listed on the "tree sidebar" right as the first entry as well.
I did attach an example jpg to this mail but it appears it didnt get through so hopefully you don't mind that I have emailed it directly FYI. I can create a short video clip of it if you want as well to show how one can navigate pages easily in this manner.
Thanks for your interest. Integrating such a feature in the main sidebar would make Xwiki wiki pages considerably more navigable.
Thanks, Cheers
>We are actively working of an improved version of the treeview. It will be shipped with XE 1.8.1. Here's a preview:
>http://www.jean-vincent.org/xwiki/bin/download/Main/Screenshots/treeview.jpg
>Is this what you had in mind ?
>Note that this tree is highly customizable and that it will be
>possible to put it in a side panel.