- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] 1.8M2: suggest public vs private v-hosting option to prevent access to other wikis
by Niels Mayer 08 Feb '09

08 Feb '09

In numerous places in the XE1.8m2 interface, the user is exposed to more information than is necessary, when virtualhosting ( http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Virtualization ) is enabled. The current virtualhosting implementation seems to assume a shared farm of wikis where one may want to expose other wikis in the farm. However, one may also want to use virtualhosting in implementations where there is no sharing between virtual hosts. So for example, we have: (1) the column 'Wiki' in Main.SpaceIndex ( e.g. http://nielsmayer.com/xwiki/bin/view/Main/SpaceIndex?space=Main ) as well as Main.WebSearch (e.g. http://nielsmayer.com/xwiki/bin/view/Main/WebSearch?text=fedora&x=0&y=0 ) -- shows "host_xe_nielsmayer_dot_com" but it doesn't really need to. (should be optional). (2) in the wysiwyg editor's "link editor" ... there's an option-menu "Choose a wiki: " that exposes the names of all the wikis, and all their database names. (should be optional: if "standalone" default to current wiki). For these, and potentially other cases, I think this behavior should be optional, not default. Most virtual wiki setups would not want their wikis to "see" each other, IMHO. This includes a fairly common scenario -- the private/public wiki setup -- people inserting links via wysiwyg in the public wiki shouldn't see all the link-names and spaces in the private wiki. Likewise, the notion of global and local users having potential access to the wiki should be based on whether the virtual-wiki setup is "shared" or "standalone." Finally, exposing the database name of the virtual-wiki (to all search engines as well) is a small, but unecessary security risk. In #2, for example, the link editor allows people to see the database names of *all* the virtual hosts. Also, if one ends up choosing unsightly but descriptive names like host_xe_nielsmayer_dot_com, users shouldn't need to see it. Niels http://nielsmayer.com

2 1

[xwiki-devs] Setting and saving Object properties
by Vivian Richard 06 Feb '09

06 Feb '09

Hello, I would greatly appreciate a little clarification clarification on the following two points regarding objects. 1. In current wiki page if I access an object attached to a different page and then sets it's value, how do I save the property values programmatically? Apparently the new property values appear in the object view of the corresponding page but a database search does not show the new values unless I manually save the page (to which the object is attached). 2. In current wiki page I created a couple of objects and then set the property values. $doc.save saves the objects but seemingly has some interesting limitations. Number of property values it can save is limited. Say for example: if I have 12 properties and their values set, $doc.save works say, for example, after 6 of those property values are set. If I put $doc.save after one additional obj.set statement it gives error. I also found $doc.save to be dependent on string length of the property values. If string lengths are small it can save , for example, 13 properties. In such cases, again, manual save works fine (although I want to avoid that). A solution/workaround with a little code example will be greatly appreciated..... Thanks

1 1

[xwiki-devs] listing pages with a keyword in their title
by WILSON Scott 06 Feb '09

06 Feb '09

Hi, I need to create a page that lists all of the pages in the wiki with a keyword in its title. For example: List all pages with the phrase 'Class_' in the title. It is important it is only the title that is searched - the body of the pages may contain lots of mentions of 'Class_' but we don't want those returned I found threads that almost answer this but none that get me 100% of the way so... How do I do this? Many thanks, Scott ____ This message and any files transmitted with it are legally privileged and intended for the sole use of the individual(s) or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by reply and delete the message and any attachments from your system. Any unauthorised use or disclosure of the content of this message is strictly prohibited and may be unlawful. Nothing in this e-mail message amounts to a contractual or legal commitment on the part of EUROCONTROL, unless it is confirmed by appropriately signed hard copy. Any views expressed in this message are those of the sender.

2 2

[xwiki-devs] [Proposal] Use livevalidation.js for client-side validation
by Jerome Velociter 06 Feb '09

06 Feb '09

Dear devs, I propose we bundle the "validation as you type" livevalidation.js library [1] in XWiki, and use it to improve user experience on several forms in XWiki Enterprise (I can think of registration form, export wiki form, page creation panel, etc.) There are several advantages I see in livevalidation compared to the other libraries I took a glance at : * It's small (12Kb minified) * It does not have any dependency (but there is version based on prototype available, too) * It is not intrusive. No need to modify the html structure or to add css classes to input fields to add validation. * It has an nice feature which allows you to precise the delay after which the validation should occur once the user stopped typing If you want to see it "live" in XWiki, I added some basic presence, password confirm and email validation on the register form on http://incubator.myxwiki.org CSS-class based validation seems to be in some sort of fashion, though I'm personally not very convince we can express all our validation using only class names (sounds intricate to do cross-field validation for example, or to validate against a custom regular expression), and for us it is not really an option right now, since we would need to make modifications in the core of XWiki for object fields displayer to add the proper class names to the inputs when calling APIs like $doc.display (or do it in javascript, but the CSS-based becomes pointless then). Last, if we really want class based validation, I believe building it with prototype and livevalidation would be very easy. Here are the other alternative I looked at rapidly: * JS-Validate [2] 67 Kb, requires prototype + scriptaculous, CSS-based , licence? * really-easy-field-validation [3] requires prototype, CSS + JS based, MIT licence * wForms [4] 81Kb minified, CSS-based , LGPL Better alternatives you would see? Otherwise, my +1 for livevalidation, Regards, Jerome. [1] http://www.livevalidation.com/ [2] http://www.jsvalidate.com/ [3] http://tetlaw.id.au/view/javascript/really-easy-field-validation [4] http://code.google.com/p/wforms/

2 4

[xwiki-devs] [VOTE] Support spaces before any "standalone block" syntax
by Thomas Mortagne 05 Feb '09

05 Feb '09

Hi dev, We decided that spaces are meaningfull in XWiki 2.0 syntax with some exception for lisibilities issue for lists and headers. With embedded documents, the need for this appear for almost all standalone blocks (tables, macros, etc.). For example in: * list item 1 ((( | cell1 | cell2 ))) * list item 2 the table will not be recognized because of the spaces before the "|" that make the parser think it's a "|" in a paragraph and not a table. We could add another exception for tables lke lists and header but I would prefer to define a rule about all kind of standalone blocks. WDYT ? Here is my +1 -- Thomas Mortagne

4 3

[xwiki-devs] Possible project ideas for XWiki in GSoC 2009
by Thilina Buddhika 04 Feb '09

04 Feb '09

Hi all, I have a growing interest on XWiki and willing to take part in its development. I am also planning to apply for GSoC 2009 (yet to be announced) and I have realised that XWiki is a challenging and promising open source project for GSoC 2009. When watching the developer list, I found this mail by Niels Mayer with the subject,* "Social Networking via OpenID support in Xwiki?"*. And It looks like an intersting idea. I also found that there was a GSoC 2008 project related to this idea [1]. So is it possible to continue this project further ? Other than the above idea, I would like to know the other possible project ideas for GSoC 2009. If it is too early I am posting about this, then lets leave it for the next couple of weeks. Anyway I am trying to get familiarized with Xwiki until the GSoC 2009 is announced. Thanks in advance. best regards, / thilina [1] - http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SSOAndOpenIDSupport

5 6

[xwiki-devs] Security Review
by Markus Lanthaler 04 Feb '09

04 Feb '09

Could be interesting for XWiki..: https://owasp.fortify.com/teamserver/welcome.fhtml

1 0

[xwiki-devs] [ANN] XWiki Enterprise 1.8 Milestone 2 Released
by Thomas Mortagne 04 Feb '09

04 Feb '09

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.8 Milestone 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download Last milestone of the XWiki Enterprise 1.8 version before release candidate. Main changes: * New Wiki Dashboard * New way of displaying tags * Page loading time reduced by 30% * Improved information section in document footer * Added wiki syntax for embedded documents * Improved authentication performance for LDAP Important bug fixes: * Many bug fixes and improvements in the new GWT WYSIWYG editor * Add support for Velocity and HTML as well as many bug fixes and improvements in the XWiki syntax converter to convert from 1.0 syntax to 2.0 syntax. Note that general goals for XWiki Enterprise 1.8 are: * Office Importer * New Blog * REST API * Finish new rendering/syntax * Finish new WYSIWYG * French XE * MediaWiki import For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise18M2 Thanks, The XWiki dev team

2 1

[xwiki-devs] Creating groups and adding users to them
by Juergen Lorenz Simon 04 Feb '09

04 Feb '09

Hi, sorry for being thick, but I can't find any documentation at all how to do this in Java and I still need some help with this. In our authenticator I'd like to check if users coming from a certain angle (i can check on that through cookies) are in a special group. If they are not, I'd like to add the to this group. Furthermore this group needs to asserted of, so I need to be able to reliably find out if it does exist and if not, create it. So far I've been frustrated by failure by attempting to use the XWikiGroupService to achieve this. Also I don't seem to be able to find a clean documentation on how users and groups and done in XWikI (in java, especially). Is there such documentation? The following code, to much bewilderment, creates a USER?! public void checkPortalGroup(XWikiContext context) { if (!_portalGroupChecked) { try { boolean groupExists = false; List<String> groupList = context.getWiki().getGroupService(context).listAllGroups(context); for (ListIterator<String> groups = groupList.listIterator(); groups.hasNext() && !groupExists;) { groupExists = groups.next().equals(PORTAL_GROUP_NAME); } if (!groupExists) { log.info("Group "+PORTAL_GROUP_NAME+" does not exist and will be created."); BaseCollection portalGroup = context.getWiki().getGroupClass(context).newObject(context); portalGroup.setName(PORTAL_GROUP_NAME); context.getWiki().getHibernateStore().saveXWikiObject((BaseObject) portalGroup, context, true); } } catch (XWikiException e) { log.error("Exception while locating or creating group "+PORTAL_GROUP_NAME+" : "+e.getMessage()); e.printStackTrace(); } _portalGroupChecked=true; } } I need some serious pointers on how the xwiki objects/classes thing is supposed to work for users/groups. Thanks a lot, J.L.Simon

3 5

[xwiki-devs] [Proposal] Install Nexus Professional & implement staging releases
by Vincent Massol 03 Feb '09

03 Feb '09

Hi, I'd like to propose that we replace our Archiva install with Nexus Professional since it's much better and would allow us to do staged releases. For details on staged releases, see http://blogs.sonatype.com/people/2009/01/nexus-professional-what-is-staging/ Basically it means the workflow for releasing would be: 1) do a release as normal 2) nexus pro intercepts the release before it goes to our release repository and moves the artifacts to a temporary staging repository 3) an email is sent to the users/devs mailing list asking for people to test the staged release to ensure it works fine 4) we allow 1 to 2 days for testing 5) the release manager then goes in the nexus UI and either promotes the staged release as a release or discards it if important problems are found 6) the release manager then continues with the release by uploading the files to the OW2 repo, modify the xwiki.org web site, etc Note that we should move towards the goal of removing the need to have RCs and thus give us more time to provide added-value in our releases. This can only be done by increasing our quality and namely it means: A) Improving our test suite and test practices (no code should be released without tests) B) Improving our manual QA tests for the release to ensure nothing is amiss The idea of staged release implements the B) point above. Ideally we shouldn't find any problem at all during step 3) above and thus B) should just be a formality. In practice it's probably a good thing to have it, just to be extra careful and give us the ability to catch last minute errors. WDYT? Thanks -Vincent http://xwiki.com http://xwiki.org http://massol.net

2 1