February 2010 - xwiki-users@xwiki.org

[xwiki-users] preventing registration on workspaces under xem
by Daniel Svoboda 17 May '10

17 May '10

Hi, I'm using workspaces 1.2M1 as a virtual xwiki under xem 1.3. I have configured the XWikiServerClass object under XWikiServerServername to have the visibility property set to 'Private'. When I look at XWikiPreferences in the virtual xwiki, there are XWikiGlobalRights objects configured Deny, Groups:,Levels:Register,Users:XWikiGuest, and Deny, Groups:XWikiAllGroup, Levels: edit, register, Users: The registration form still appears on the login page, and upon filling in the fields and submitting, registration is successful. I need to not allow registration by anyone except Admin. Thanks, Dan Svoboda

5 6

[xwiki-users] Lucene defaultpage fails
by Gerritjan Koekkoek 16 May '10

16 May '10

Navigating to the Main.LuceneSearch page brings up the following error? Failed to execute macro: velocity org.xwiki.rendering.macro.MacroExecutionException: Failed to evaluate Velocity Macro for content [$xwiki.jsfx.use("uicomponents/search/search.js", true)## $xwiki.ssfx.use("uicomponents/search/search.css", true)## The page has worked, but what can be wrong now. The page itself is not changed from the distribution? Gerritjan

5 18

[xwiki-users] Deny Public registration Wiki Workspaces
by Chris Ellis 13 May '10

13 May '10

I really love the look and use of the xwiki products, but the lack of documentation and broken functionality is very frustrating. After finally getting smtp authorisation working in Enterprize I find the email which is generated is not forming URLs properly - grrr. So now I'm back to exploring Workspaces milestone 1.2 and I have found that setting Public Registration to Allow or Deny makes no difference - registration is just a matter of supplying a name and email address and you're in. No admin approval required. This is not acceptable for an admin setup intended for staff only. Can anyone explain to me how this might be fixed please? Cheers Chris Ellis Lorne-Aireys Inlet P-12 College

2 1

Re: [xwiki-users] is there a way to disable export to rtf, html and xar leaving just pdf
by dev geek 23 Mar '10

23 Mar '10

> Hi, > > is there a way to disable export to rtf, html and xar leaving just pdf? > > Is ther a way to disable exporting altogether? > >

3 3

[xwiki-users] Problems with links
by ndreher 18 Mar '10

18 Mar '10

Hello, sometimes after inserting Links in the WYSIWYG-Editor and saving the Document, mistakes occur on the site. Example before: Nach einer korrekten [[Benutzeranmeldung am WebClient>>BenutzeranmeldungAmWebClient]] einschließlich einer Autorisierungsprozedur hat der ... Example with mistake: Nach einer korrekten org.xwiki.gwt.dom.client.Element#placeholder[[BenutzeranmeldungAmWebClient]][[">Benutzeranmeldung am WebClient>>/xwiki/bin/view/CSC_AfTD_Hilfe/BenutzeranmeldungAmWebClient]] einschließlich einer Autorisierungsprozedur hat der ... I hope that you can help me soon. Looking forward to your reply. Best wishes Norbert [Germany] -- View this message in context: http://n2.nabble.com/Problems-with-links-tp4435123p4435123.html Sent from the XWiki- Users mailing list archive at Nabble.com.

5 26

[xwiki-users] [Proposal] Governance for xwiki.org
by Vincent Massol 16 Mar '10

16 Mar '10

Hi everyone (devs and users), While we have a clear governance for write access to our source repository (http://dev.xwiki.org) we're missing a clear governance for xwiki.org. The idea is to address mainly the following 2 questions: 1) who "owns" it and thus "controls" (or rather provides direction for) its content 2) can it be used for business advertising (support, paid packages, consulting services) Bit of History about XWiki SAS ======================== - XWiki SAS (http://xwiki.com) is the company founded by Ludovic Dubost the creator of XWiki (I'm the CTO of XWiki SAS in addition to being a committer here). - Most of the active contributors are also employed and paid by XWiki SAS to develop the XWiki software. Today that's -- 12.5 committers (developers) -- 1 open source product manager (see http://markmail.org/thread/ggaaw4u6yyci4oan for its definition) -- 1 designer -- 1 tester/technical writer - XWiki SAS sells services around the open source software, see http://www.xwiki.com/xwiki/bin/view/Services/ - XWiki SAS truly believes and understands open source, see http://www.xwiki.com/xwiki/bin/view/About/Values -- I also wrote a blog post on this some time back: http://massol.myxwiki.org/xwiki/bin/view/Blog/XWikiSASAndOpenSource - XWiki SAS has promised "not to do evil" ;), see its manifesto at http://www.xwiki.com/xwiki/bin/view/About/Manifesto - XWiki SAS is paying for the servers and maintenance of xwiki.org, myxwiki.org, the maven repo, the svn repo, the hudson build serversn the free JUG farm, and more Issue at hand =========== XWiki SAS would like to generate more revenue to be able to increase the development pace of the XWiki software. We'd like to fund even more the development of XWiki, so that it becomes an even better product. We've asked you what you'd like to see in the future in XWiki and you've answered on this survey result: http://www.xwiki.org/xwiki/bin/view/Blog/Features+Survey+Results We'd like to implement those features as fast as possible. For this we need to ensure that users interested in commercial services find easily the way to http://xwiki.com, even when they arrive on xwiki.org. This is true for XWiki SAS's services but also for any company willing to offer services around the XWiki open source project. There's no magic. Developers need to be paid when they work full time on some project. We need a commercial ecosystem around XWiki for it to progress as quickly as its competitors (the collaboration market). We need to allow for commercial companies the ability to generate revenue from their work on the XWiki open source project. However we also want to continue ensuring that all the XWiki development is done in open source, under a LGPL license. Governance Proposal ================= 1) xwiki.org is controlled by the XWiki committers. This means that important changes brought to it should be discussed/vote on the list, using the same practices as for code commits 2) xwiki.org stays open in edit mode to all external contributors (and XWiki committers continue to monitor it to remove spam, etc) 3) we agree to start with 3 zones where companies can advertise their commercial offers on top of the XWiki open source product: -- On the download page (for business packages, subscriptions, hosting) -- On the support page (for services: support, consulting) -- (still to be defined) Possibly on a "Products" tab in the new horizontal navigation. The idea would be to do as jboss.org is doing. Projects are open source and community and Products are commercial 4) the company offerings are listed by their amount of contributions to the XWiki open source project. The company that contributes most (XWiki SAS today) gets the best spots (top of the list, bigger space) 5) Companies who want to be listed should provide some proof of their contributions to the XWiki open source project 6) XWiki SAS gets some acknowledgment for paying for the xwiki.org server/maintenance of it. Probably somewhere in the footer of the site or on side panel somewhere 7) xwiki.org should always remain a site for the xwiki open source community Conclusion ========= We want to stress that this proposal is not about XWiki SAS making a commercial takeover of the xwiki.org site. It's about recognizing that if the XWiki open source software progresses quickly today, it's thanks to contributors but also for a very large proportion to companies paying developers to work on it, either directly (like XWiki SAS or other companies that have developers contributing) or indirectly (by paying for example XWiki SAS or other companies to work on specific features). It's also about recognizing that XWiki SAS is happy to see other companies willing to contribute to the progress of the XWiki open source project and thus to provide a place for these companies to be visible too. I hope that all our contributors but also users of the XWiki Open Source software will find this proposal acceptable and I welcome any feedback on it. Thanks -Vincent Massol Hat 1: XWiki SAS CTO Hat 2: XWiki committer

6 7

[xwiki-users] WYSIWYG editor language in user interface
by Frantisek Kall 11 Mar '10

11 Mar '10

Hello I've translated WYSIWYG editor's Strings.properties file into my language. Then I've putted it into place ( .../wysiwyg/client/editor) with name Strings_sk.properties but editor is still in English. What I am doing wrong? -- View this message in context: http://n2.nabble.com/WYSIWYG-editor-language-in-user-interface-tp4440246p44… Sent from the XWiki- Users mailing list archive at Nabble.com.

3 7

[xwiki-users] Removing comments, attachments, etc from certain pages
by Josh D 10 Mar '10

10 Mar '10

Hi, I was wondering if it was possible to remove the comments, attachments, history and information tabs from certain pages. Perhaps just by inserting some css or javascript on the pages where I don't want these things to show. Also, I was hoping to reduce the font size of the "Create New Post" text in the blog (I'm using the toucan skin if that helps). Which file would I look in do to this? Any help here would be greatly appreciated. Cheers, Josh _________________________________________________________________ Find out what’s new with your friends Download the new Windows Live Messenger http://download.live.com/

2 1

[xwiki-users] Still issues with livetables
by Jeremie BOUSQUET 02 Mar '10

02 Mar '10

Hello, I still have issues with livetables ... I'm willing to investigate, but a little help would be appreciated :) I'm basically wanting to show 2 fields of a custom class of mine. There are some hundreds of objects of this kind in my wiki. So I add the following in a page in 2.0 syntax {{velocity}} #set($collist = [ "subject", "startdate"]) #set($colprops = { "subject" : { "type" : "text" , "link":"view", "size" : 50, "filterable": true, "sortable":true}, "startdate" : { "type" : "text", "filterable":false, "sortable":true} }) #set($options = { "className":"My.Class", "tagCloud":true, "rowCount": 10 }) #livetable("myclass" $collist $colprops $options) {{/velocity}} This results in an empty array displayed ... If I filter by typing 3 to 4 letters of an existing "subject", then SOMETIMES, it displays the related objects, but not always. Result is identical if I put the velocity part in 1.0 syntax page. Tried to play and remove most of the fields options, still the same behaviour. I have retrieved the URL that generates the JSON data from the logs, put it in my browser, and it generates some JSON with 10 elements, as expected. There was an exception on date formatting though, so I removed the "startdate" field from the list, but still the same behaviour. How could I investigate this issue ? Do you think it might be related to my installation ? Because all other livetables in the wiki work well, except some of them that are linked to custom classes (alldocs works pretty well). Could it be some special characters in "subject" text ? ('/', '[', ... ?) I'm on xwiki 2.2-RC2, tomcat 6, linux RH4. Thanks for help, Jeremie

3 8

[xwiki-users] Where to improve the translation, resource file or l10i.xwiki.org
by Wang Ning 28 Feb '10

28 Feb '10

Hi, I have some question about translation. 1. Is the ApplicationResources_zh.properties exported from l10i.xwiki.org? But I find the resources file in xwiki 2.2.1 release package is not the same as the resource file I get from l10i.xwiki.org. 2. I think the （Total translations = Empty translations + Outdated translations + Translations to review）, but in the site I found it is not equal all the time, for example, Simplified Chinese (zh), Total translations: 2425 Empty translations: 477 Outdated translations: 29 Translations to review: 1454 477 + 29 + 1454 = 1960 != 2425. Does this mean the missing 465 items are Validated? What is the relationship between total empty and outdate translations. 3. If I want to improve the translation. Do I modify the resource file and submit a patch or I just edit l10i.xwiki.org. Thanks. Wang Ning

3 2