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

by Colin Tay

Hi, I would like to retrieve the number of document that is viewable by the current user (Meaning it has the access to the document). How can i modified the following codes to achieve that feature? #set($query="select count(doc) from XWikiDocument doc") #set($resultsCount = $xwiki.search($query).get(0)) Thanks in adv, Colin Get your preferred Email name! Now you can @ymail.com and @rocketmail.com http://mail.promotions.yahoo.com/newdomains/sg/

16 years, 5 months

2
2
0 0

Re: [xwiki-devs] [xwiki-notifications] r18927 - platform/web/trunk/standard/src/main/webapp/resources/js/xwiki

by Sergiu Dumitriu

jvelociter (SVN) wrote: > Author: jvelociter > Date: 2009-04-22 02:16:46 +0200 (Wed, 22 Apr 2009) > New Revision: 18927 > > Modified: > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/xwiki.js > Log: > XWIKI-3175 Clean the javascript global object from method and properties that should not be exposed > > I think we can safely removed this XWikiAjax method definitely. Shouldn't it be placed in the deprecated file instead? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 5 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r18899 - in platform/core/branches/xwiki-core-1.8/xwiki-core/src/main: java/com/xpn/xwiki java/com/xpn/xwiki/doc java/com/xpn/xwiki/internal resources/META-INF resources/META-INF/plexus

by Sergiu Dumitriu

tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-04-21 14:46:05 +0200 (Tue, 21 Apr 2009) > New Revision: 18899 > > XWIKI-3563: Allow setting the default rendering syntax wiki by wiki > > Modified: platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/CoreConfiguration.java > =================================================================== > --- platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/CoreConfiguration.java 2009-04-21 12:30:36 UTC (rev 18898) > +++ platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/CoreConfiguration.java 2009-04-21 12:46:05 UTC (rev 18899) > @@ -19,16 +19,19 @@ > */ > package com.xpn.xwiki; > > - * > - * @version $Id$ > + * > + * @version $Id: CoreConfiguration.java 18237 2009-04-04 22:30:29Z vmassol $ This shows that the file doesn't have the proper svn:keywords. > Modified: platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/doc/XWikiDocument.java > =================================================================== > --- platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/doc/XWikiDocument.java 2009-04-21 12:30:36 UTC (rev 18898) > +++ platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/doc/XWikiDocument.java 2009-04-21 12:46:05 UTC (rev 18899) > @@ -293,9 +293,9 @@ > - private DocumentNameFactory documentNameFactory = > - (DocumentNameFactory) Utils.getComponent(DocumentNameFactory.class.getName()); > - > + private DocumentNameFactory documentNameFactory = > + (DocumentNameFactory) Utils.getComponent(DocumentNameFactory.ROLE); > + Are you sure this change is good? > Modified: platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/internal/DefaultCoreConfiguration.java > =================================================================== > --- platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/internal/DefaultCoreConfiguration.java 2009-04-21 12:30:36 UTC (rev 18898) > +++ platform/core/branches/xwiki-core-1.8/xwiki-core/src/main/java/com/xpn/xwiki/internal/DefaultCoreConfiguration.java 2009-04-21 12:46:05 UTC (rev 18899) > @@ -19,12 +19,17 @@ > +@Component Are you sure the 1.8 branch supports this kind of components? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 5 months

2
1
0 0

[xwiki-devs] [GSoc] Congratulation

by Keerthan MUTHURASA

Hello wikiers, Congratulation to all of you selected people for working on xwiki projects and I wish you a nice summer coding and playing with xwiki API !!! Regards, Keerthan Muthurasa

16 years, 5 months

1
0
0 0

[xwiki-devs] [Office Importer] Shall we allow height & width attributes of <img> tags under 'strict' filtering mode?

by Asiri Rathnayake

Hi Devs, First of all, sorry about the long email subject :) Our style filter is working quite nicely and users so far like it very much :). Still, word documents sometimes contain really really (I mean really) huge images embedded in them. In such cases since our style filter rips off height & width attributes of <img> tags, images run way off the page boundaries (looks very ugly). Following are the only attributes currently allowed with our style filter: a --> href, name img --> alt, src td --> colspan, rowspan I think we have to add height & width attributes into this set (under img tag) because heights & widths are not actually styling attributes (IMO). Note: We are discussing about cleaning OO generated html content that comes from a word document, not about general html cleaning. WDYT? Thanks. - Asiri

16 years, 5 months

5
8
0 0

[xwiki-devs] Practices for Front-end Development

by Jerome Velociter

Hi Guys, I've refactored a little http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices to introduce practices for Front-End development. Right now it's only a set of practices for JavaScript development (rules about external libraries, namespacing and backward compatibility/deprecation), but I'd like that in the future we add practices for Design (UI consistency, UX guidelines, etc.) and CSS development. Since the rules I've added for JS have not all been voted (none except the deprecation strategy has been voted in fact), they are of course open to discussion. Tell me what you think, Regards, Jerome.

16 years, 5 months

1
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r18877 - in platform/web/trunk/standard: . src/main/webapp/resources/js/xwiki/actionbuttons

by Vincent Massol

Hi Sergiu, On Apr 21, 2009, at 12:27 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2009-04-21 00:27:36 +0200 (Tue, 21 Apr 2009) > New Revision: 18877 > > Modified: > platform/web/trunk/standard/pom.xml > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/ > actionbuttons/actionButtons.js > Log: > [misc] Velocity code inside JS breaks the minimization process > > > Modified: platform/web/trunk/standard/pom.xml > =================================================================== > --- platform/web/trunk/standard/pom.xml 2009-04-20 21:32:42 UTC (rev > 18876) > +++ platform/web/trunk/standard/pom.xml 2009-04-20 22:27:36 UTC (rev > 18877) > @@ -139,6 +139,7 @@ > <artifactId>maven-dependency-plugin</artifactId> > <executions> > <execution> > + <id>unpack-dependencies</id> >  > <phase>test</phase> > @@ -264,8 +265,9 @@ > </includes> >  > <excludes> > - <exclude>**/*-min.js</exclude> > + <exclude>**/*-min.js</exclude> > <exclude>**/*-debug.js</exclude> > + <exclude>**/actionButtons.js</exclude> Would be great to have a comment here to explain why this is execluded maybe? (I wonder if we'll remember in a few months/year). Especially since the comment 'exclude already minified files"' doesn't match. Thanks -Vincent

16 years, 5 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r18869 - in platform/web/trunk/standard/src/main/webapp: resources/icons resources/icons/xwiki resources/js/xwiki resources/js/xwiki/actionbuttons templates

by Jerome Velociter

Hi, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2009-04-20 22:25:52 +0200 (Mon, 20 Apr 2009) > New Revision: 18869 > > Added: > platform/web/trunk/standard/src/main/webapp/resources/icons/xwiki/ > platform/web/trunk/standard/src/main/webapp/resources/icons/xwiki/ajax-loader-large.gif > platform/web/trunk/standard/src/main/webapp/resources/icons/xwiki/ajax-loader-white.gif > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/actionbuttons/ > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/actionbuttons/actionButtons.js > Modified: > platform/web/trunk/standard/src/main/webapp/templates/edit.vm > platform/web/trunk/standard/src/main/webapp/templates/editactions.vm > platform/web/trunk/standard/src/main/webapp/templates/inline.vm > platform/web/trunk/standard/src/main/webapp/templates/macros.vm > platform/web/trunk/standard/src/main/webapp/templates/preview.vm > platform/web/trunk/standard/src/main/webapp/templates/previewactions.vm > Log: > XWIKI-3654: Improve editor and preview buttons > XWIKI-2597: Hitting 'Back to edit' after previewing an in-line form does not return to inline editing > XWIKI-3653: Edit comment and Minor edit settings lost when going to the preview and back to edit > Done. > > [snip] > > Added: platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/actionbuttons/actionButtons.js > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/actionbuttons/actionButtons.js (rev 0) > +++ platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/actionbuttons/actionButtons.js 2009-04-20 20:25:52 UTC (rev 18869) > @@ -0,0 +1,218 @@ > +// ====================================== > +// Form buttons: shortcuts, AJAX improvements and form validation > +// To be completed. > +if (typeof(XWiki) == 'undefined') { > + XWiki = new Object(); > +} > +if (typeof(XWiki.actionButtons) == 'undefined') { > + XWiki.actionButtons = new Object(); > +} > + > +XWiki.actionButtons.EditActions = Class.create({ Why do you make this a class and not an object ? It looks like it will never be instanciated more than once > + initialize : function() { > + this.addListeners(); > + this.addShortcuts(); > + this.saveAndContinueListener = new XWiki.actionButtons.EditActions.AjaxSaveAndContinue(this); > + }, > [snip] > + onCancel : function(evt) { > + evt.stop(); > + var location = evt.element().form.action; > + if (location.indexOf('?' == -1)) { > + location += '?'; > + } > + window.location = location + 'action_cancel=true'; > + }, > + onPreview : function(evt) { > + if (!this.validateForm(evt.element().form)) { > + evt.stop(); > + } > + }, > + onSaveAndView : function(evt) { > + if (!this.validateForm(evt.element().form)) { > + evt.stop(); > + } > + } > +}); Maybe we could fire custom events here for code that want to listen to cancel/preview/save clicks. I faced the case several times, and ended up using some wicked CSS selectors to find the buttons to observe. We could do something like : onSaveAndView : function(evt) { if (!this.validateForm(evt.element().form)) { evt.stop(); } else { document.fire("xwiki:actions:save:before"); } } Jerome. > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

16 years, 5 months

2
1
0 0

[xwiki-devs] Integration of XWiki with Magnolia CMS

by Pascal Voitot

Hello guys, I'm back after some months away... I wanted to create my small website looking like a website (and not like a blog) where I could express myself (even if I don't think it is very interesting ) and where I could test some technologies at the same time... my live public laboratory... I have been working with some CMS for some time now and also with wikis... Beyond the common discussions about the differences between CMS and Wiki I can find everywhere, I still think both approaches are compatible and complementary... Personnally, I prefer writing, formatting with Wiki syntaxes but I also like skinning and authoring/publishing mechanisms in CMS... I have decided to make an experimentation by designing my website using Wiki+CMS... I have chosen: - Magnolia CMS since it's designed around a Java lightweight architecture, fully implementing a JCR storage (this was one of my interests also), it provides publishing workflow between a private and public instances and it provides a nice skinning and authoring mechanism... There are lots of defaults and poor docs in it but this is not the question here. - XWiki for the wiki because as George says:"What else????"... I also decided to use only XWiki/2.0 syntax to test it deeply... I wanted: - to use the CMS as the content aggregator and XWiki as one content provider - to use XWiki remotely and enable content retrieval from several XWikis for example - to integrate XWiki pages as paragraphs into a magnolia page containing other contents - to allow remote XWiki edition using a "simplified" XWiki editor So I have developped: - a Magnolia module which manages the creation/edition/insertion of XWiki paragraphs into Magnolia. The XWiki pages are retrieved remotely from one XWiki server using the XMLRPC API for the time being... - a "light" XWiki editor based on velocity templates from the basic XWiki skin. You can see the resulting website in this site: http://www.mandubian.org It's a draft site so please don't look too much at the quantity of content (and the quality also ;) ) I will build progressively the website, deliver, document and improve the XWiki/Magnolia module also and bring new ideas also... This is a private server so don't be surprised when it is not very quick! regards Pascal Voitot

16 years, 5 months

2
1
0 0

[xwiki-devs] Getting your feedback about different texts for XWiki.org

by Emilie Ogez

Hi, I'd like your feedback about these different texts that would be put online on XWiki.org. *You are about to download XWiki* This is a short text that would be put there: http://www.xwiki.org/xwiki/bin/view/Main/Download --> http://dev.xwiki.org/xwiki/bin/view/Drafts/TextDownload *Manifesto* This Manifesto is cited in the previous text. It would be put on XWiki.com and/or XWiki.org Its objective is to give a clear vision of XWiki SAS involvement and commitment towards XWiki software. --> http://dev.xwiki.org/xwiki/bin/view/Drafts/Manifesto *Satisfaction survey about XWiki software* This survey will be sent to the people who downloaded XWiki enterprise or one of its applications, with the purpose of getting feedback about our software in order to make it better. It would only be sent to the people who downloaded XWiki Enterprise at first. --> http://dev.xwiki.org/xwiki/bin/view/Drafts/SatisfactionSurveyProducts Thanks in advance for your help and your time. Emilie

16 years, 5 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r18827 - in platform/web/trunk/standard/src/main/webapp: resources/icons resources/icons/datamodel resources/js/xwiki resources/js/xwiki/dataeditors templates

by Jerome Velociter

Hi Sergiu, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2009-04-19 21:40:15 +0200 (Sun, 19 Apr 2009) > New Revision: 18827 > > Added: > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/ > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/boolean.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/calendar.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/database.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/groups.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/move.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/number.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/password.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/propertyType-Generic.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/rights.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/staticlist.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/string.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/textarea.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/tree.png > platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/users.png > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/dataeditors/ > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/dataeditors/dataeditors.css > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/dataeditors/dataeditors.js > Modified: > platform/web/trunk/standard/src/main/webapp/templates/editclass.vm > platform/web/trunk/standard/src/main/webapp/templates/editobject.vm > platform/web/trunk/standard/src/main/webapp/templates/editpanelsvars.vm > Log: > XWIKI-3635: Improve the object and class editors > Done. L10N will be done afterwards. > > [snip] > Property changes on: platform/web/trunk/standard/src/main/webapp/resources/icons/datamodel/rights.png > ___________________________________________________________________ > Name: svn:mime-type > + image/png > > This image is not very comprehensive. I had to look twice before getting it is key ring. [snip] > +XWiki.XPropertyOrdering = Class.create({ Shouldn't this be namespaced under the XWiki namespace ? For example "XWiki.dataeditor.XPropertyOrdering" If we do not make submodules in the XWiki objects, we'll make the same mistake we did with the window object, and we will end up with a large collection of properties and functions that have nothing to do one with each other. I'd rather keep the XWiki object for both holding modules and functions/classes/properties that have sense in all XWiki pages, not just in one module. Jerome. > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

16 years, 5 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r18760 - in platform: core/trunk/xwiki-core/src/main/resources xwiki-applications/trunk/tag/src/main/resources/XWiki

by Sergiu Dumitriu

jvelociter (SVN) wrote: > Author: jvelociter > Date: 2009-04-16 20:03:35 +0200 (Thu, 16 Apr 2009) > New Revision: 18760 > > Modified: > platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties > platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources_fr.properties > platform/xwiki-applications/trunk/tag/src/main/resources/XWiki/TagCloud.xml > Log: > XE-430 In space dashboard, display tag cloud with tags of the space > > > Modified: platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties > =================================================================== > --- platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties 2009-04-16 17:21:20 UTC (rev 18759) > +++ platform/core/trunk/xwiki-core/src/main/resources/ApplicationResources.properties 2009-04-16 18:03:35 UTC (rev 18760) > @@ -1117,6 +1117,7 @@ > # Tag application > xe.tag.tags=Tags > xe.tag.notags=No document has been tagged yet. Documents can be tagged from the information section (footer) or from the Document information panel available in edit mode. For more information on tagging please refer to the <a href="http://www.xwiki.org/xwiki/bin/view/UserGuide/">User Guide</a>. > +xe.tag.notagsforspace=No document has been tagged yet in space *{0}*. Documents can be tagged from the information section (footer) or from the Document information panel available in edit mode. For more information on tagging please refer to the <a href="http://www.xwiki.org/xwiki/bin/view/UserGuide/">User Guide</a>. I think we should rethink how/if to use wiki markup in localization resources. This would fail if used in a document with the 2.0 syntax, since the bold markup was changed. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 5 months

2
1
0 0

[xwiki-devs] [VOTE] Add Rendering event begin/endGroup + remove (%%) + add params for macros

by Vincent Massol

Hi, * Thomas and I would like to split the current begin/endDocument() events by adding begin/endGroup(). We're currently reusing the same event for group usage (with the (((...))) syntax). * This will allow us to write things such as (%...%)(((....))) in order to add parameters for a group of standalone blocks * We also propose to remove the (%...%)...(%%) notation in favor of (%..%)(((...))) notation * (%..%) will always be applied only to the next element, even for inline content. * Add support for (%...%){{macro/}} Here's my +1 Thanks -Vincent

16 years, 5 months

5
5
0 0

Re: [xwiki-devs] Group Members in Velocity

by bruno.amaro

Thanks! It works like a charm ;) You are looking for something like: #if($xwiki.getUser("XWiki.Admin").isUserInGroup("XWiki.XWikiAllGroup")) ... #end Check the API of your XWiki (http://platform.xwiki.org/xwiki/bin/download/DevGuide/API/xwiki-core-1.8.1-…), please. Here a snippet where the prefix "XWiki." is handled in Velocity. Only the user login name and group name has to be entered. Have fun, Rudi #if(($request.action) && ($request.action == 'CheckGroupMembership')) #set($group = "XWiki.${request.group}") #set($user = "XWiki.${request.user}") #if($xwiki.getUser($user).isUserInGroup($group)) User $user IS in group $group #else User $user IS NOT in group $group #end #end 1 Check Group Membership <form action="$doc.getURL("view")" method="post"> <input type="hidden" name="action" value="null" /> <table> <tr> <td>Group:</td> <td><input type="text" name="group" value="$!request.group" size="60" /><td> </tr> <tr> <td>User:</td> <td><input type="text" name="user" value="$!request.user" size="60" /></td> </tr> </table> <input type="submit" value="Check Group Membership" onclick="document.getElementById('bequiet').style.visibility='visible';this.form.action.value='CheckGroupMembership'" />  <div id="bequiet" style="visibility:hidden"> <h1>busy...</h1> </div> </form> Hi I`m trying to figure a way to check if a user is a member of one group. I`m looking for something like: a) retrieve the groups membership of an user in velocity or b) check if a user is a member of a specify group. Thanks in advance Regards, Bruno -- View this message in context: http://n2.nabble.com/Group-Members-in-Velocity-tp2641137p2652257.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 5 months

1
0
0 0

[xwiki-devs] [VOTE] HTML and Velocity macro NL/WS behaviors

by Vincent Massol

Hi devs, We need to come to a conclusion for handling New Lines(NL) and white spaces (WS) in HTML and Velocity Macro. If you remember from http://markmail.org/thread/mhqhxnz5twhev5se the current problem is that we cannot indent scripts since WS and NL are meaningful. I'd like to reiterate the proposal that was sent but not enough people voted on it (only Thomas did). A) For the HTML macro, we propose to make the following changes: - strip NL/WS between elements (elements that don't accept CDATA) - strip leading/trailing NL/WS for element content before passing them to the wiki syntax parser B) for the Velocity macro we have 2 choices I can think of: 1) strip all leading spaces for all lines (but keep NL) Note that this means that inside a velocity macro you wouldn't be able to have a line break with the new line starting with spaces without escaping the leading space with ~(space). Note also that this means we will not be able to add extra new lines to format the text nicely (since that would add new paragraphs) or split a single line into several lines for extra readability. This is the case today with the old syntax and it's a pain not to be able to aerate the text with empty lines. Ex: some text ~ next line #if (...) this goes on the same line #something(...) #end This is a new paragraph In this example notice that we need the velocity #if to be on the same line since NL are significant. 2) strip all leading spaces for all lines + remove all NL too. This means we need to ensure we still have one space remaining between "words" (same as HTML). The user would use something like $nl and $sp to explicitely enter new lines and spaces. The advantage is that you control completely the formatting (no magic anymore) at the cost of a little extra work (adding the $nl where required). Basically this means the same pros/cons as when you work with HTML where you need to explicitly add <br/> when you want new lines. Ex: some text $nl $sp next line #if (...) this goes on the same line #something(...) <-- this is also on the same line #end $nl $nl This a new paragraph Note: I've aerated the text by putting extra new lines around the velocity #if to show that it would work. 3) Same as 1) + strip 1 NL (i.e. line breaks) and only allow "forced" line breaks with "\\". The exact algorithm is: if there's 1 NL remove it, if there's more than 1 leave them. Ex: some text\\ ~ next line #if (...) this goes on the same line #something(...) <-- this is also on the same line #end This a new paragraph I'm +1 for A) For B) I think the most flexible is 2) but I'm wondering if it's too big a change for our users or not. If not 2) then 3). Thanks -Vincent

16 years, 5 months

7
14
0 0

[xwiki-devs] Error number 3 in 0

by walido

Hi, i have this error since yesterday and all i did is trying to add a excel plugin so i followed the tutorial , i added the jxl jar in lib directory and i putted the line in xwiki.cfg but after having this error i rolled back all my changes i deleted the jar and restored the xwiki.cfg to the same old state but still have the error: HTTP ERROR: 500 Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: Error number 3001 in 3: Cannot load class com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager from param xwiki.store.migration.manager.class Wrapped Exception: Error number 0 in 3: Exception while hibernate execute Wrapped Exception: invalid configuration RequestURI=/xwiki/bin/view/Main/ Powered by Jetty:// what should i do, my work is lost? help on this one please thank you very much -- View this message in context: http://n2.nabble.com/Error-number-3-in-0-tp2642272p2642272.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 5 months

2
2
0 0

[xwiki-devs] [Proposal] New xwiki-text module?

by Vincent Massol

Hi, In the rendering code we have several places where we've had to create generic string manipulation classes/methods (for example a method to remove a single NL at start and end of string). I think it would be better to create one or several components for these string manipulation methods (same as we have xwiki-xml for xml manipulation). The idea is that we should use existing framework as much as possible (StringUtils from commons lang for ex) but when we cannot find an existing framework to manipulate text then we would put it in xwiki- text. WDYT? Thanks -Vincent

16 years, 5 months

3
5
0 0

Re: [xwiki-devs] [xwiki-notifications] r18727 - enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/selenium

by Vincent Massol

On Apr 16, 2009, at 12:56 PM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2009-04-16 12:56:05 +0200 (Thu, 16 Apr 2009) > New Revision: 18727 > > Added: > enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/ > xpn/xwiki/it/selenium/SimpleAdvancedTest.java > Modified: > enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/ > xpn/xwiki/it/selenium/AllTests.java > Log: > XAADMINISTRATION-35: Administrative users get their own setting on > usertype, and not the setting for the user whose profile they're > viewing > Added test. > Patch submitted by Arun Reddy Nelakurthi, applied with codestyle > changes > > > Modified: enterprise/trunk/distribution-test/selenium-tests/src/test/ > it/com/xpn/xwiki/it/selenium/AllTests.java > =================================================================== > --- enterprise/trunk/distribution-test/selenium-tests/src/test/it/ > com/xpn/xwiki/it/selenium/AllTests.java 2009-04-16 10:54:34 UTC (rev > 18726) > +++ enterprise/trunk/distribution-test/selenium-tests/src/test/it/ > com/xpn/xwiki/it/selenium/AllTests.java 2009-04-16 10:56:05 UTC (rev > 18727) > @@ -79,6 +79,7 @@ > addTestCase(suite, DocExtraTest.class); > addTestCase(suite, PanelsTest.class); > addTestCase(suite, SectionTest.class); > + addTestCase(suite, SimpleAdvancedTest.class); Shouldn't this go in the existing UserProfileTest.class instead? There seems to be some duplication too to create a user. Thanks -Vincent > return new XWikiSeleniumTestSetup(new XWikiTestSetup(suite)); > } > > Added: enterprise/trunk/distribution-test/selenium-tests/src/test/it/ > com/xpn/xwiki/it/selenium/SimpleAdvancedTest.java > =================================================================== > --- enterprise/trunk/distribution-test/selenium-tests/src/test/it/ > com/xpn/xwiki/it/selenium/ > SimpleAdvancedTest.java (rev 0) > +++ enterprise/trunk/distribution-test/selenium-tests/src/test/it/ > com/xpn/xwiki/it/selenium/SimpleAdvancedTest.java 2009-04-16 > 10:56:05 UTC (rev 18727) > @@ -0,0 +1,98 @@ > +/* > + * See the NOTICE file distributed with this work for additional > + * information regarding copyright ownership. > + * > + * This is free software; you can redistribute it and/or modify it > + * under the terms of the GNU Lesser General Public License as > + * published by the Free Software Foundation; either version 2.1 of > + * the License, or (at your option) any later version. > + * > + * This software is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > + * Lesser General Public License for more details. > + * > + * You should have received a copy of the GNU Lesser General Public > + * License along with this software; if not, write to the Free > + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA > + * 02110-1301 USA, or see the FSF site: http://www.fsf.org. > + */ > +package com.xpn.xwiki.it.selenium; > + > +import com.xpn.xwiki.it.selenium.framework.AbstractXWikiTestCase; > +import com.xpn.xwiki.it.selenium.framework.AlbatrossSkinExecutor; > +import com.xpn.xwiki.it.selenium.framework.XWikiTestSuite; > + > +import junit.framework.Test; > + > +/** > + * Verify Advanced and Simple User type settings. > + * > + * @version $Id$ > + */ > +public class SimpleAdvancedTest extends AbstractXWikiTestCase > +{ > + public static Test suite() > + { > + XWikiTestSuite suite = new XWikiTestSuite("Verify Advanced > and Simple User type settings."); > + suite.addTestSuite(SimpleAdvancedTest.class, > AlbatrossSkinExecutor.class); > + return suite; > + } > + > + protected void setUp() throws Exception > + { > + super.setUp(); > + open("Main", "WebHome"); > + } > + > + public void testSimpleAdvancedUsertype() > + { > + // Remove "JohnSmith" user if already exists > + loginAsAdmin(); > + deletePage("XWiki", "JohnSmith"); > + getSelenium().waitForPageToLoad("30000"); > + // Ensure that the user isn't logged in > + logout(); > + > + // Register new user "JohnSmith" > + getSelenium().click("headerregister"); > + getSelenium().waitForPageToLoad("30000"); > + getSelenium().type("register_first_name", "John"); > + getSelenium().type("register_last_name", "Smith"); > + getSelenium().type("xwikiname", "JohnSmith"); > + getSelenium().type("register_password", "JohnSmith"); > + getSelenium().type("register2_password", "JohnSmith"); > + getSelenium().type("register_email", > "JohnSmith(a)example.com"); > + getSelenium().click("//input[@value='Register']"); > + getSelenium().waitForPageToLoad("30000"); > + > + // Login as "JohnSmith" and chech for the user type. Verify > whether the Usertype Switch Link works. > + login("JohnSmith", "JohnSmith", false); > + getSelenium().waitForPageToLoad("30000"); > + open("XWiki", "JohnSmith"); > + assertTextPresent("Switch to Advanced edit mode"); > + getSelenium().click("link=Switch to Advanced edit mode"); > + getSelenium().waitForPageToLoad("30000"); > + getSelenium().click("link=Switch to Simple edit mode"); > + getSelenium().waitForPageToLoad("30000"); > + assertTextPresent("Switch to Advanced edit mode"); > + logout(); > + > + // Login as "Admin" and Verify whether usertype of > "JohnSmith" is Simple. > + loginAsAdmin(); > + open("XWiki", "JohnSmith"); > + assertTextPresent("Switch to Advanced edit mode"); > + > + // Switch Usertype of "JohnSmith" to Advanced. > + getSelenium().click("link=Switch to Advanced edit mode"); > + getSelenium().waitForPageToLoad("30000"); > + assertTextPresent("Switch to Simple edit mode"); > + logout(); > + > + // Login as "JohnSmith" and verify whether the usertype is > Advanced. > + login("JohnSmith", "JohnSmith", false); > + open("XWiki", "JohnSmith"); > + assertTextPresent("Switch to Simple edit mode"); > + logout(); > + } > +}

16 years, 5 months

2
1
0 0

[xwiki-devs] [Proposal] Improvements to the Office Importer Application

by Guillaume Lerouge

Hi devs, based on feedback from our system administrator & project managers, I'd like to suggest the following improvements to the Office Importer application (those improveents were initially suggested in 2 JIRA issues): * Administration - XAOFFICE-13 * - Ability to set the server path in xwiki.cfg or xwiki.properties (already done) - Ability to overwrite the server path in a field on .../xwiki/bin/admin/XWiki/XWikiPreferences?editor=globaladmin&section=XWiki.OfficeImporterAdmin - Provide an option to set the OOo server to start automatically when XWiki gets started - Ability to define this setting in xwiki.cfg or xwiki.properties - Ability to overwrite this setting on .../xwiki/bin/admin/XWiki/XWikiPreferences?editor=globaladmin&section=XWiki.OfficeImporterAdmin Ideally, we should also allow *remote access to the OOo server*, so that the same OOo server can be used by more than 1 wiki and be located on another machine. Asiri tells me that this is not possible with the current version of JOD converter. However this feature is going to be oft requested. *Is there any other way to make it work?* *User Experience - XAOFFICE-14* Right now, the link to the Office Importer is located in the action bar, under the "Actions" menu. The action bar is meant to let users interact with the current page (context actions), thus the "Import Office Document" link shouldn't be located there. - Move the "Import Office Document" link from the action bar to the Quick Links panel and rename it to "Office Import". - That's what we do with current default applications (Blog) and what we used to do with the Photo album and the calendar. Since the Office Import is a default application as well, I don't see why it should be trated differently. Additionally, it would make it easier for admins to remove the link if needed, by editing the panel (right now the link cannot be removed from the interface, which is annoying if the admin doesn't want to setup an OOo server and rather hide the feature). On the XWiki/OfficeImporter page, the import feature is displayed even if the OOo server is not currently running. Only after the user first tries to import a file is the "Open Office Server not available" message displayed. - If the OOo server isn't running when the user accesses the XWiki/OfficeImporter page, a message should be displayed saying that: - "You cannot import an Office document since the conversion server has not been started. Please ask an administrator to get it started." - If the current user is an admin, the message should read: - "You cannot import an Office document since the conversion server has not been started. You can start the OpenOffice server and manage it from this page (link to the OOo server administration page)." On the XWiki/OfficeImporer page, the user is expected to know the name of the space he will import the file into. This is not very user friendly. - Provide a select box displaying a list of spaces before the input field. If no space is selected (select box left empty), the value in the input field is used. If the input field is empty as well, a warning asking the user to choose a space is returned. - Change the text to read: "Please select a space: [space select box] or create a new one [create space input field]" If the user tries to import an Office Document on a page that already exists, an error message is dislayed but no "next step" is suggested. - Ideally, when the user types the name of the page he wants to create, a live JS validator should tell him whether the page already exists or not - If the JS solution isn't possible: the message should be improved to read: - "The target document Main.WebHome already exists. Please try again (link to the XWiki/OfficeImporter page) and choose another page name." The XWiki/OfficeImporter page offers little explanations as to its purpose and how it works. - An additional line should be added at the top, between the title and the import field, reading: - "This page allows you to import Office Documents into your wiki. It will turn the Office document you uploaded into a wiki page." - "Document" should be renamed to "Select a document to import" next to the input field I'm aware there's a lot of data in here, I'll create a separate thread to discuss a specific point if one of them turns out to be controversial. Thanks for your feedback, Guillaume -- Guillaume Lerouge Product Manager - XWiki Skype ID : wikibc http://guillaumelerouge.com/

16 years, 5 months

3
3
0 0

[xwiki-devs] [Important] Regression in XE 1.8.1 for multiwiki usage

by Vincent Massol

Hi everyone, We've just found that XE 1.8.1 is having some GWT service initialization issue in multiwiki mode. All applications using the XWiki GWT service fail on XE 1.8.1 (in multiwiki mode only). More specifically this will affects users in multiki mode and using the new WYSIWYG editor or XWiki Watch (both using GWT Services). For those users we recommend to wait for XE 1.8.2 which is planned for early next week (week of the 20th of April). Sorry for the inconvenience. -Vincent on behalf of the XWiki dev team

16 years, 5 months

1
0
0 0

Re: [xwiki-devs] dragging vertically in timelines

by Niels Mayer

In http://groups.google.com/group/simile-widgets on Tue, Apr 14, 2009 at 11:08 PM, David Huynh <dfhuynh(a)alum.mit.edu> wrote: I've updated the trunk to fix #1 http://trunk.simile-widgets.org/timeline/examples/compact-painter/compact-p… Let me know how it feels. This is a great improvement! I liked the new interface enough that I wanted to try it out in Xwiki: example: http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/test code: http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/test?raw=1 http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/StyleSheet?raw=1 http://nielsmayer.com/xwiki/bin/view/TimelineTrunk/DataJson?raw=1 Niels http://nielsmayer.com > > Larry, if you have some time, I'd be grateful for some help on > implementing your #2 point. It's been a while since I touch all the > settings in Timeline and don't remember how they propagate. After that, > maybe we should consider a 2.4 release. > > David > > David Huynh wrote: > > OK, sounds like we have consensus... I'll implement them when I get a > > chance. > > > > David > > > > John Callahan wrote: > > > >> I totally agree with both of Larry's cents. Items 1) and 2) as Larry > >> described them would work very well for my applications. > >> > >> - John > >> > >> > >> > >> Larry Kluger wrote: > >> > >> > >>> Hi, > >>> > >>> I like David's slim scrollbar, I think it's more attractive than the > >>> usual windows toolbar. > >>> I also agree with David's point that a standard window toolbar may > >>> influence people away from realizing that they can scroll a Timeline > >>> along the time axis. > >>> > >>> My 2 cents on the issue are: > >>> 1) The scrollbar should always be visible if there are more events > >>> than can be shown on the available tracks. It should be usable as a > >>> handle for moving the Timeline since its affordance is to act as a > handle. > >>> (Affordance is a UI term. An object's affordance is the behavior that > >>> we expect from an object, given its appearance and context.) > >>> > >>> 2) I think the bouncing off the top and bottom of the band effect is > >>> great for when the touch gesture is used on an iPhone, iTouch, or some > >>> of the newer Macs. But having it occur as the result of a > >>> mouse-interaction doesn't feel right to me. I'd appreciate some way to > >>> turn that behavior off and I don't recommend it as a default (except > >>> when the browser has a touch interface). > >>> > >>> Note that Timeline works pretty well out of the box on the iTouch. > >>> Enabling the Timeline to be scrolled vertically really solves one of > >>> the few problems with Timeline on an iPhone etc. The only other issue > >>> is to change the bubbles' show/hide UI when used with an iPhone. > >>> That's on my list. > >>> > >>> Regards, > >>> > >>> Larry > >>> > >>> > ------------------------------------------------------------------------ > >>> *From:* David Huynh <dfhuynh(a)alum.mit.edu> > >>> *To:* simile-widgets(a)googlegroups.com > >>> *Sent:* Wednesday, March 25, 2009 12:17:24 AM > >>> *Subject:* Re: dragging vertically in timelines > >>> > >>> > >>> David Karger wrote: > >>> > >>> > >>>> you mean use a native vertical scrollbar? That would seem to create a > >>>> "mixed metaphor" ui; > >>>> > >>>> > >>> That was one of the reasons I didn't want to use a native vertical > >>> scrollbar. > >>> > >>> > >>> > >>>> i am guessing you can come up with a better > >>>> consistent metaphor. It took me quite a while to notice the vertical > >>>> scrollbar, and I'm puzzled why it is "read only". > >>>> > >>>> > >>>> > >>> The intention is that it's only an indicator, and the body of the band > >>> is the interactor. > >>> > >>> I think people ain't used to scrolling horizontally as much, so if > >>> vertical scrolling were any more emphasized than it is, then that might > >>> totally inhibit any hint that horizontal scrolling is possible. (A > >>> native vertical scrollbar would really emphasize vertical scrolling.) > >>> But I could be wrong. > >>> > >>> > >>> > >>>> farfetched, but what if you made the timeline into a "barrel" that > >>>> rolled away at the top and bottom (images shrinking) to indicate there > >>>> is more present? > >>>> > >>>> > >>>> > >>> "Barrel" like this? > >>> http://z.about.com/d/ipod/1/0/e/3/-/-/iphone_gallery_10.jpg > >>> I can add some gradients. > >>> > >>> David > >>> > >>> > >>> > >>> > >>> > >>> > >> > >> > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "SIMILE Widgets" group. > To post to this group, send email to simile-widgets(a)googlegroups.com > To unsubscribe from this group, send email to > simile-widgets+unsubscribe(a)googlegroups.com<simile-widgets%2Bunsubscribe(a)googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/simile-widgets?hl=en > -~----------~----~----~----~------~----~------~--~--- > >

16 years, 5 months

1
0
0 0

[xwiki-devs] Group Members in Velocity

by Bruno Amaro Almeida - cubiX

Hi I`m trying to figure a way to check if a user is a member of one group. I`m looking for something like: a) retrieve the groups membership of an user in velocity or b) check if a user is a member of a specify group. Thanks in advance Regards, Bruno

16 years, 5 months

1
0
0 0

[xwiki-devs] integrating media streaming with xwiki? (was Re: Problems with scripting)

by Niels Mayer

walid.kharroubi(a)hraccess.com : > but do you think it's possible to implement a streaming service in xwiki > using groovy class with importing a streaming api(the streaming server will > be vlc for example)? > Xwiki is better suited as a framework for creating and presenting streaming applications but not for the actual streaming implementation. It is correct to look at implementations specifically designed for streaming (e.g. VLC, Darwin <http://developer.apple.com/opensource/server/streaming/index.html>, etc) rather than trying to tame performance issues such as object/thread overhead,. out-of-memory and running out of threads -- common issues when many long-running streaming downloads occur in a servlet environment.. On the client end, Xwiki creates the HTML/CSS/javascript scaffolding, with streaming implemented via streaming "plugins" in the web-browser (e.g. mozilla plugin, a java applet or flash). These plugins could be accessed in Xwiki via special velocity macros that cleanly encapsulate all the scaffolding required to achieve this. The macro would allow easy parametrization and placement of these "streaming UI objects" in a Xwiki-based document/application. For example VLC has a mozilla broser plugin that you can control with a javascript API. http://www.videolan.org/doc/play-howto/en/ch04.html#id310965 suggests the following could be encapsulated within a velocity macro to implement this functionality: <embed type="application/x-vlc-plugin" pluginspage="http://www.videolan.org" version="VideoLAN.VLCPlugin.2" width="640" height="480" id="vlc"> </embed> <script language="Javascript">  </script> In my experience, it is straightforward to integrate these kinds of things with Xwiki, once you get adjusted to the possiblity of "computation" happening in three places and at different times: browser, server and plugin; and figuring out the dependencies and interactions therein. Unfortunately, from a pragmatic perspective, expecting your users to install VLC or other special browser plugins is the kiss-of-death. Most users will just blow it off and move on to something else that uses Flash and "works right out of the box" for the majority of users. (Therefore you can be doctrinaire about being "purely open source" and it just means you'll be strongly limiting your customer base and needlessly limiting your own project's potential for success). It would be nice to have a truly abstract streaming media macro that would implement the same generic API for streaming media within Xwiki. The macro would determine at run-time, whether the browser is enabled with specific plugins needed to display a specific media type (such as the VLC moz plugin); if not available, the macro would dynamically switch-in the flash-based equivalent for people using IE or who don't want to install the VLC moz plugin. For example given a "mp4", the macro would first attempt to use VLC, on failure it might try the platform's browser-embeddable media presenter if media-compatible (e.g. MS windows media), and would finally try a "generic" flash player such as the Jeroen "JW" Wijering players ( http://www.longtailvideo.com/players/ ). Who else is working on streaming media issues in Xwiki? Would love to see some group interest and coding participation towards better integration of streaming media in Xwiki. Niels http://nielsmayer.com PS: some of my work-in-progress on some streaming clients in Xwiki (not actual velocity macros yet, but at least they work). http://nielsmayer.com/xwiki/bin/view/Macros/JW-Player?raw=1 http://nielsmayer.com/xwiki/bin/view/Macros/YT-Chromeless?raw=1

16 years, 5 months

4
5
0 0

[xwiki-devs] Need Help to Integrate Date Picker to Poll Application

by Chathura Prabuddha

Hai.. I'm trying to integrate the date picker to poll application date fields. I would like to know is there a way that to set the object property name (like $pobj.pollOpen) as the 'relative' in the javascript. ex: <script type="text/javascript"> var dpicker = new DatePicker({ relative : 'how to set the object parameter', language: "$context.language" }); </script> Also I want to know that can we use the date picker inside the #info macro. ex:#info("The poll is open from $pobj.pollOpen to $pobj.pollClose.") Thank you. ~ Chathura Prabuddha Ganegoda~ Undergraduate, Department of Computer Science & Engineering, University of Moratuwa, Sri Lanka. http://gacpganegoda.blogspot.com/

16 years, 5 months

3
2
0 0

[xwiki-devs] [ANN] XWiki Enterprise 1.9 Milestone 1 Released

by Jean-Vincent Drean

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.9 Milestone 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download First milestone of the XWiki Enterprise 1.9 version. Main changes: * New Office Importer feature: document splitting. * Document syntax can be changed from the WYSIWYG editor. Important bug fixes: * Various bugfixes in syntax 2.0. * Various bugfixes in the xwiki syntax 1.0 to 2.0 converter. Note that general goals for XWiki Enterprise 1.9 are: * Finish/stabilize/document new rendering * Finish/stabilize/document new wysiwyg editor * Finish/stabilize/document office importer + doc splitter/management * Finish/stabilize/document webdav * Finish/stabilize/document REST support * Usability improvements For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise19M1 Thanks, The XWiki dev team

16 years, 5 months

2
1
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs