xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] Loading a Groovy Script from another Script

by Andreas Schaefer

When I try to load a Groovy script using xwiki.parseGroovyFromPage() then I fail when this Script is enclosed inside '{{groovy}}'. This means I have to use two different documents when I want to use the same document to be loaded by XWiki and by xwiki.parseGroovyFromPage() because one needs the be enclosed by '{{groovy}} and the other can't. Isn't there a way to remove '{{groovy}}' when parsed so that the scripts can be used for both? In addition the 'GroovyScriptEngineImpl' which is used for the Binding does throw a NoSuchPropertyException when a property is not available. This makes it cumbersome to test for properties and add them if not already put inside. For example I need some objects over and over like 'BlogParams' and so I would like to store them inside the bindings. In order to avoid the exception I either have to catch the Exception (time consuming) or I need to get the properties map and check if the property is already added to the map. Is there a better way to do that? Cheers - Andy

15 years, 2 months

[xwiki-devs] XWiki developer conference

by Sergiu Dumitriu

Hello friends of XWiki, Several XWiki members will be participating at FOSDEM next year in February ( http://fosdem.org/ ), and we're trying to determine if there's interest in applying for a devroom, which would mean half a day or more of XWiki-related presentations. - Are there any people interested in participating to such presentations? - Does anybody want to do such a presentation, besides XWiki committers? I'd need answers to these questions soon, since the deadline for application is in two days. Note that FOSDEM is a developer-oriented conference, so presentations should be rather technical. FYI, there is no participation fee, anybody can attend FOSDEM as long as there are places in the rooms. -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 2 months

[xwiki-devs] [ANN] XWiki Enterprise 2.1 Milestone 1 released

by Jean-Vincent Drean

The XWiki development team is pleased to announce the release of XWiki Enterprise 2.1 Milestone 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download It's the first and only milestone of the 2.1 version. Main changes from 2.0.3: * Re-design of the actions menus. Split the top menu into 2: one for wiki and space level actions and one for page level actions. * New renderer for mathematical formulae based on the Google Chart APIs. * Added PHP support through a new PHP Macro (note that this Macro is not bundled by default, you'll need to install it). * Lots of improvements and bugfixes in order to conform to the Web Content Accessibility Guidelines (WCAG). * Macro parameter pretty names are now displayed in the WYSIWYG * WYSIWYG editor performance improvement (Minimize and aggregate WYSIWYG editor stylesheets at build time to reduce the number of HTTP requests) * Upgraded to JbossCache 3.2.1GA version * Upgraded to Groovy 1.7 Beta 2 * Lots of bugs fixes For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise21M1 Thanks -The XWiki dev team

15 years, 2 months

Re: [xwiki-devs] [xwiki-notifications] r25212 - platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc

by Vincent Massol

On Nov 19, 2009, at 1:48 PM, vmassol (SVN) wrote: > Author: vmassol > Date: 2009-11-19 13:48:06 +0100 (Thu, 19 Nov 2009) > New Revision: 25212 > > Modified: > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/ > XWikiDocument.java > Log: > [misc] web --> space ouch, I committed too much.... -Vincent > > Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > doc/XWikiDocument.java > =================================================================== > --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/ > XWikiDocument.java 2009-11-19 11:51:51 UTC (rev 25211) > +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/ > XWikiDocument.java 2009-11-19 12:48:06 UTC (rev 25212) > @@ -447,13 +447,13 @@ > * Constructor that specifies the full document identifier: wiki > name, space name, document name. > * > * @param wiki The wiki this document belongs to. > - * @param web The space this document belongs to. > + * @param space The space this document belongs to. > * @param name The name of the document. > */ > - public XWikiDocument(String wiki, String web, String name) > + public XWikiDocument(String wiki, String space, String name) > { > setDatabase(wiki); > - setSpace(web); > + setSpace(space); > > int i1 = name.indexOf("."); > if (i1 == -1) { > @@ -4166,8 +4166,9 @@ > } > > /** > - * Rename the current document and all the backlinks leading to > it. See > - * {@link #rename(String, java.util.List, > com.xpn.xwiki.XWikiContext)} for more details. > + * Rename the current document and all the backlinks leading to > it. The parent field in all documents which list > + * the renamed document as their parent is also renamed. > + * See {@link #rename(String, java.util.List, java.util.List, > com.xpn.xwiki.XWikiContext)} for more details. > * > * @param newDocumentName the new document name. If the space is > not specified then defaults to the current space. > * @param context the ubiquitous XWiki Context > @@ -4187,9 +4188,11 @@ > * <li>[Page?param=1]</li> > * <li>[currentwiki:Page]</li> > * <li>[CurrentSpace.Page]</li> > + * <li>[currentwiki:CurrentSpace.Page]</li> > * </ul> > * <p> > - * Note: links without a space are renamed with the space added. > + * Note: links without a space are renamed with the space added > and all documents having the renamed document as > + * their parent have their parent field set to > "currentwiki:CurrentSpace.Page". > * </p> > * > * @param newDocumentName the new document name. If the space is > not specified then defaults to the current space. > @@ -4228,43 +4231,57 @@ > return; > } > > + // Grab the XWiki object, it gets used a few times. > + com.xpn.xwiki.XWiki xwiki = context.getWiki(); > + > // Step 1: Copy the document and all its translations under > a new name > - context.getWiki().copyDocument(getFullName(), > newDocumentName, false, context); > + xwiki.copyDocument(getFullName(), newDocumentName, false, > context); > > - // Step 2: For each backlink to rename, parse the backlink > document and replace the links > - // with the new name. > - // Note: we ignore invalid links here. Invalid links should > be shown to the user so > - // that they fix them but the rename feature ignores them. > + // Step 2: For each child document, update parent. > + List<String> childDocumentNames = getChildren(context); > + if(childDocumentNames != null){ > + // Note: We're adding the fully qualified document name > (i.e. including the wiki name). > + String newParent = newDocName.getWiki() + ":" + > newDocName.getSpace() + "." + newDocName.getPage(); > + > + for (String childDocumentName : childDocumentNames) { > + XWikiDocument childDocument = > xwiki.getDocument(childDocumentName, context); > + childDocument.setParent(newParent); > + xwiki.saveDocument(childDocument, > context.getMessageTool().get("core.comment.renameParent", > + Arrays.asList(new String[] {newDocumentName})), > true, context); > + } > + } > + > + // Step 3: For each backlink to rename, parse the backlink > document and replace the links with the new name. > + // Note: we ignore invalid links here. Invalid links should > be shown to the user so that they fix them but the > + // rename feature ignores them. > DocumentParser documentParser = new DocumentParser(); > > for (String backlinkDocumentName : backlinkDocumentNames) { > - XWikiDocument backlinkDocument = > context.getWiki().getDocument(backlinkDocumentName, context); > + XWikiDocument backlinkDocument = > xwiki.getDocument(backlinkDocumentName, context); > > if (backlinkDocument.is10Syntax()) { > // Note: Here we cannot do a simple search/replace > as there are several ways to point > // to the same document. For example [Page], [Page? > param=1], [currentwiki:Page], > // [CurrentSpace.Page] all point to the same > document. Thus we have to parse the links > // to recognize them and do the replace. > - ReplacementResultCollection result = > - > documentParser.parseLinksAndReplace(backlinkDocument.getContent(), > oldLink, newLink, linkHandler, > - getSpace()); > + ReplacementResultCollection result = > documentParser.parseLinksAndReplace( > + backlinkDocument.getContent(), oldLink, > newLink, linkHandler, getSpace()); > > backlinkDocument.setContent((String) > result.getModifiedContent()); > } else { > backlinkDocument.refactorDocumentLinks(oldDocName, > newDocName, context); > } > > - context.getWiki().saveDocument(backlinkDocument, > - > context.getMessageTool().get("core.comment.renameLink", > Arrays.asList(new String[] {newDocumentName})), > - true, context); > + xwiki.saveDocument(backlinkDocument, > context.getMessageTool().get("core.comment.renameLink", > + Arrays.asList(new String[] {newDocumentName})), > true, context); > } > > - // Step 3: Delete the old document > - context.getWiki().deleteDocument(this, context); > + // Step 4: Delete the old document > + xwiki.deleteDocument(this, context); > > - // Step 4: The current document needs to point to the > renamed document as otherwise it's > - // pointing to an invalid XWikiDocument object as it's been > deleted... > - clone(context.getWiki().getDocument(newDocumentName, > context)); > + // Step 5: The current document needs to point to the > renamed document as otherwise it's pointing to an > + // invalid XWikiDocument object as it's been deleted... > + clone(xwiki.getDocument(newDocumentName, context)); > } > > private void refactorDocumentLinks(DocumentName oldDocumentName, > DocumentName newDocumentName, XWikiContext context)

15 years, 2 months

[xwiki-devs] Fwd: [ANN] Maven Checkstyle Plugin 2.4 Released

by Vincent Massol

We could upgrade now to get checkstyle 5. -Vincent Begin forwarded message: > From: Mark Hobson <markh(a)apache.org> > Date: November 19, 2009 10:22:34 AM CEST > To: announce(a)maven.apache.org, users(a)maven.apache.org > Subject: [ANN] Maven Checkstyle Plugin 2.4 Released > Reply-To: "Maven Users List" <users(a)maven.apache.org> > > The Maven team is pleased to announce the release of the Maven > Checkstyle Plugin, version 2.4. > > This plugin generates a report on violations of code style and > optionally fails the build if violations are detected. > > http://maven.apache.org/plugins/maven-checkstyle-plugin/ > > You should specify the version in your project's plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-checkstyle-plugin</artifactId> > <version>2.4</version> > </plugin> > > Release Notes - Maven 2.x Checkstyle Plugin - Version 2.4 > > ** Improvement > * [MCHECKSTYLE-105] - Update to Checkstyle 5.0 > * [MCHECKSTYLE-122] - Add Portuguese (Brazil) translation > * [MCHECKSTYLE-124] - Add Swedish translation > > ** Task > * [MCHECKSTYLE-119] - Review the Doxia Sink calls > * [MCHECKSTYLE-120] - Bump to Doxia 1.0 > * [MCHECKSTYLE-125] - Update to maven-reporting-impl-2.0.4.3 > > Enjoy, > > -The Maven team

15 years, 2 months

[xwiki-devs] Enabling/disabling monitoring

by Łukasz Skowroński

[XWiki Enterprise 2.0.3 on Windows XP] Hi, XWiki Enterprise\webapps\xwiki\WEB-INF\xwiki.cfg file contains the following lines: #-# Enable light monitoring of the wiki performance. Records various statistics, like number of requests processed, #-# time spent in rendering or in the database, medium time for a request, etc. Disable for a minor increase of #-# performance and a bit of memory. # xwiki.monitor=1 This is quite misleading because although xwiki.monitor=1 is commented out XWiki still monitor requests. To actully turn it off one has to put xwiki.monitor=0 I would vote to turn off monitoring if xwiki.monitor setting is not defined (i.e. is commented out). Kind regards Lukasz

15 years, 2 months

[xwiki-devs] [VOTE] Change search id to class to fix invalid XHTML/WCAG + various other changes

by Vincent Massol

Hi, Whenever a panel is displayed more than once (ie on the panel page itself if the page is also displayed in a panel column, in the panel wizard, etc) we have invalid XHTML for panels that use an HTML ID attribute. We have this in the search panel right now which I'd like to fix. In addition with Colibri we've hardcoded the search panel content in the header. Here's what I'd like to do: 1) Use class name of globalsearch and globalsearchinput instead of IDs Note: WCAG tests forbid using <label> without a FOR attribute which means we need an ID for the input. This can be achieved easily using velocity to increment a counter. This is a technical internal ID anyway so it won't matter. 2) In Colibri, use #displaypanel(Panels.Search) instead of hardcoding the panel content in the header. This allow users to edit the content for example to change the link to Main/Websearch to Main/LuceneSearch or do any other thing). Note: the only change between what is currently in the Search panel and in the colibri header is the image which can be overwritten in colibri I guess. A better solution (if someone with CSS skills can help me) might be to define the image to display in the CSS. 3) In the release notes, mention the change and tell users that if they want to keep the old behavior (for ex if they have a custom skin using the globalsearch* IDs) then they just need to edit the Search panel and replace "class" by "id". Here's my +1 Thanks -Vincent

15 years, 2 months

[xwiki-devs] NTLM Authentication

by ivm-dev

Hi, we found in the svn-sandbox, that some kind of ntlm authentication is implemented. In Jira we found the following request for that "XWIKI-2496 Single Sign on HTTP Negiotiate login" (hope we are right on that). Is this feature planned for an upcoming release? We would also be interested in testing! Thanks Helmut -- View this message in context: http://n2.nabble.com/NTLM-Authentication-tp4024303p4024303.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

15 years, 2 months

[xwiki-devs] [VOTE] Add getSyntax api to BlockRenderer components interface

by Thomas Mortagne

Hi devs, Currently it's not possible to list support BlockRenderer syntaxes like we do for Parser for example. So i propose to add Syntax getSyntax(); to BlockRenderer interface Here is my +1 -- Thomas Mortagne

15 years, 2 months

Re: [xwiki-devs] [xwiki-notifications] r25111 - platform/web/branches/xwiki-web-2.0/wysiwyg/src/main/resources/com/xpn/xwiki/wysiwyg/client/editor

by Vincent Massol

On Nov 18, 2009, at 12:44 AM, mflorea (SVN) wrote: > Author: mflorea > Date: 2009-11-18 00:44:21 +0100 (Wed, 18 Nov 2009) > New Revision: 25111 > > Modified: > platform/web/branches/xwiki-web-2.0/wysiwyg/src/main/resources/com/ > xpn/xwiki/wysiwyg/client/editor/Strings.properties > Log: > XWIKI-4581: Change the name for "Background Color" to "Highlight > Color" > > Merged from trunk, revision 25110. > > > Modified: platform/web/branches/xwiki-web-2.0/wysiwyg/src/main/ > resources/com/xpn/xwiki/wysiwyg/client/editor/Strings.properties > =================================================================== > --- platform/web/branches/xwiki-web-2.0/wysiwyg/src/main/resources/ > com/xpn/xwiki/wysiwyg/client/editor/Strings.properties 2009-11-17 > 23:43:13 UTC (rev 25110) > +++ platform/web/branches/xwiki-web-2.0/wysiwyg/src/main/resources/ > com/xpn/xwiki/wysiwyg/client/editor/Strings.properties 2009-11-17 > 23:44:21 UTC (rev 25111) > @@ -5,7 +5,7 @@ > apply=Apply > select=Select > attachment=Insert an Attachment Link > -backColor=Background Color > +backColor=Highlight Color Minor: Is it the background color or the highlight color? If highlight is the correct one then maybe the key name should be changed too? At the very least I think a comment would be necessary since someone reading this line will not know who's right... the key or the value... Highlight is a term that refers to me as a foreground color. Thanks -Vincent

15 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs