xwiki-devs

xwiki-devs@xwiki.org

9399 discussions

Start a nNew thread

[xwiki-devs] Space Creator Name

by Prathap Pandian

Hi, How to print the space creator in wiki page. getcreator() this is getting the page creator. -- Prathap

17 years, 2 months

[xwiki-devs] XWiki - Print Page Creator In Panel

by Prathap Pandian

Hi, I want to print the page creator in the panel. And i have used the following code: #panelheader($doc.web) #foreach($subdoc in $xwiki.getSpaceDocsName("$doc.web")) #set($web = $doc.web) #set($page = $subdoc) #set($document = "$web.$page") $document.getCreator() #end #panelfooter() but it seems not working. -- Prathap

17 years, 2 months

[xwiki-devs] [GSOC] Distributed Search status and problem committing the source code

by saikrishna venkata pendyala

Hi David and Ludovic, I have finished implementing distributed search for XWiki using the existing plugin "lucene". In short what the new code does. (on each individual installation) 1. As soon is XWiki is started, lucene plugin is initiated, during the process of initialization, the machine makes is index remote available. 2. A Parallel searcher is created over all the remotely available indexes, during the initialization of lucene plugin. These 2 steps will achieve a simple distributed search. But Index updates would not be reflected. 3. As and when there is an index update, index reader which was made remotely available earlier in step 1 is re-opened and is made remotely available. With this Index updates on remote machines are reflected in search process. But what if one the machines go down during the process ?? 4. When ever there is an error while performing distributed search, the parallel searcher in step 2 is redefined, i.e instead of searching 'n' machines (earlier) it will search only 'n-m' machines. At some point the machines went down will be started again. How to search on these machines again? 5. A thread keeps on checking if searcher is set to search over all the slaves defined in xwiki.cfg or not . If it is not searching on all the slaves, It will try to redefine the searcher in step 2 as did in step 4. 6. I have modified existing XWiki.Results to make compatible to both distributed/normal search. 7. Modified xwiki.cfg.vm, to have fews options for distributed search. I have tested this on a cluster of 5 machines and it is working fine. In addition to distributed search I have also attempted to fix 2 bugs/issues in earlier implementation of lucene. a. Fix Lucene plugin scoring algorithm -- *XPLUCENE-8<http://jira.xwiki.org/jira/browse/XPLUCENE-8> *b. Remove duplicates from Lucene search results -- *XPLUCENE-5<http://jira.xwiki.org/jira/browse/XPLUCENE-5> *All these changes exist in the modified version of lucene plugin. *Cannot commit the source code : *I was trying to commit the source code to https://svn.xwiki.org/svnroot/sandbox/plugins/lucene, but I couldn't This is what I did, 1. svn co https://pvsaikrishna@svn.xwiki.org/svnroot/sandbox/plugins/~/xwiki-sandbox-… 2. svn export lucene ~/xwiki-sandbox-plugins 3. cd ~/xwiki-sandbox-plugins 4. svn add lucene 5. svn commit --username pvsaikrishna -m 'distributed search using lucene' *I got the following error* svn: Commit failed (details follow): svn: MKACTIVITY of '/svnroot/sandbox/!svn/act/e5cbc51c-1643-4805-9019-0ce92d036d2b': 500 Internal Server Error (https://svn.xwiki.org) --Sai Krishna

17 years, 2 months

LANG property in startup script in standalone version

by Vincent Massol

Hi, Does anyone know why we have the following LANG property defined in our startup scripts: #!/bin/sh export LANG=fr_FR.ISO8859-1 JETTY_HOME=. JETTY_PORT=8080 JAVA_OPTS=-Xmx300m java $JAVA_OPTS -Dfile.encoding=iso-8859-1 -Djetty.port=$JETTY_PORT - Djetty.home=$JETTY_HOME -jar $JETTY_HOME/start.jar I think this is bad as it's french and I don't think we should set it for the user. That said, if it's there its probably because it was required in the past, hence my question here. To summarize: anyone sees any issue if I remove that "export LANG" line? Thanks -Vincent

17 years, 2 months

[xwiki-devs] [ANN] XWiki Watch 1.0 release candidate 2 released!

by ancapaula.luca＠xwiki.com

The XWiki development team is pleased to announce the release of XWiki Watch 1.0 RC 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download#HXWikiWatch ! This is the second and hopefully the last release candidate for the 1.0 version. It fixes several bugs, notably the ones regarding skin and browser compatibility. The final release is planned for the next week. Changes from 1.0RC1: * Inconsistencies caused by feed renaming are now all fixed (XWATCH-122, XWATCH-158, XWATCH-175, XWATCH-173) * XWiki Watch is now fully compatible with the toucan skin (XWATCH-113) * Performance has been improved and bugs have been fixed for uniform usage across browsers (XWATCH-161, XWATCH-167, XWATCH-172) * Various bug fixes and improvements: (XWATCH-143, XWATCH-170, XWATCH-171) For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesWatch10RC2 Thanks -The XWiki dev team

17 years, 2 months

[xwiki-devs] [VOTE] Release XWiki Watch RC 1.0 RC2

by ancapaula.luca＠xwiki.com

Hello devs, Already with a quite big delay, I would like to release XWiki Watch 1.0 RC2 as soon as possile, with the following changes from RC1: http://jira.xwiki.org/jira/secure/ReleaseNote.jspa?version=10756&styleName=… . Here's my +1, wdyt? Happy coding, Anca

17 years, 2 months

[xwiki-devs] [VOTE] Bring forward XE 1.5 final + create 1.5 branch

by Jean-Vincent Drean

I'd like to bring forward the release dates for XE 1.5 final, as follows: * 1.5RC1 - 07/07 * 1.5Final - 15/07 I'd also like to create a branch for 1.5 since it's now in RC stage and trunk will become 1.6-SNAPSHOT so that committers eager to work on 1.6 can start doing so and so that we're not tempted to push non bug changes in 1.5. Reasons: * Some of us would like to work on 1.6 (like Jerome who'd like to fix our captcha mechanisms) * There's an ongoing vote to drop the 1.3 branch, as usual we'd have 2 branches with 1.4 and 1.5 (our standard rule is to support 2 versions). Here's my +1 to both the new dates and the branch creation. Thanks, JV.

17 years, 2 months

[xwiki-devs] [ANN] XWiki Enterprise 1.5 Release Candidate 1 Released

by Jean-Vincent Drean

First release candidate of the XWiki Enterprise 1.5 version. Main changes: * Updated french translation * Updated spanish translation * LDAP authenticator no longer creates a local user if it exists at the global level * Mail sender plugin now supports SMTP authentication * Arguments passed to radeox macros like {image} or {attach} are not rendered anymore * UTF-8 characters are now all correctly rendered in PDF exports * Statistics database mapping working well under oracle For more details about this 1.5 Release Candidate 1 release, see : http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise15RC1 Thanks -The XWiki dev team

17 years, 2 months

[xwiki-devs] Parser Issuer

by malaka ekanayake

Hi vincent Now I'm working on the costume implementation of the IDocument Partitioner which uses the XDOM parser. But in order to to register partitions with the IDocument,requires the offset and the length of each token returned by the parser. But the current implementation of the parser don't have that information.Do I need to look at that issuer as well or what? I have very little understanding of the implementation of the parser and I will be difficult for me to implement that functionality. Vincent can you help me on this issuer. -- Malaka Ekanayake CSE UOM

17 years, 2 months

[xwiki-devs] XWiki - Moving users into newly created group.

by Prathap Pandian

Hi, I have created a new group in the space, then i have added a new user, while creating a new user i need that user to be moved in the newly created group by default. Already the users are adding in the XWikiAllGroup (Default group in xwiki). Is there any document to do this...? -- Prathap

17 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