Hi,
+1.
Silvia
Pe 10.11.2010 15:35, Guillaume Lerouge a scris:
> Hi XWiki Devs,
>
> I've been performing some XWiki demos recently and it came to my attention
> that when adding a comment to a page and then going back to the homepage, my
> comments didn't show up in the recent activity section of the dashboard.
> This is due to the fact that adding a comment is considered a minor event.
>
> This behavior is still taking place in the most recent versions of XWiki
> Enterprise (I tested a XE 2.7 snapshot this morning). I believe that
> comments should be treated as major events, the same way that adding an
> object or an annotation to a page is.
>
> Therefore I propose making adding a comment a major event instead of a minor
> one.
>
> Here's my +1 for this.
>
> Thanks,
>
> Guillaume
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
Hi,
I want to create an application similar or based on the attachment panel
application at the bottom of the xwiki pages. The application should let the
user select the file to upload to the xwiki server and write a description
of the file. Then, the file name and description should be automatically
added to a table. The first column of the table is the file name, that is a
link to the file. The second column of the table is the description of the
file. So, the table is like a repository of the files and its respective
descriptions.
My question is. Is there a macro or code snipped to add a file to the
attachment panel application?
Regards,
Abel
Hi XWiki Users,
I've been performing some XWiki demos recently and it came to my attention
that when adding a comment to a page and then going back to the homepage, my
comments didn't show up in the recent activity section of the dashboard.
This is due to the fact that adding a comment is considered a minor event.
This behavior is still taking place in the most recent versions of XWiki
Enterprise (I tested a XE 2.7 snapshot this morning). I believe that
comments should be treated as major events, the same way that adding an
object or an annotation to a page is.
Therefore I propose making adding a comment a major event instead of a minor
one.
Here's my +1 for this.
Thanks,
Guillaume
Hi All,
I want to show a dialog window similar to the one that is shown when you
want to add a user. A "Registration" window is shown. I was looking for
documentation on how to do that but I couldn't find it. So I used the Modal
Box component. But I want to keep the consistency on the look of my xwiki
site. Could somebody point me some documentation on how to add a dialog
window similar to the one that is shown when you want to add a user? I want
to show the dialog window using groovy or velocity code, if possible.
Regards,
Abel
Hi all,
it's a couple of weeks that the daily scheduling for watchlist notification
doesn't work anymore. in particular, i get the following error message on
catalina.out log file:
2010-11-02 15:15:11,642 [DefaultQuartzScheduler_Worker-2] ERROR
watchlist.WatchListPlugin - Exception while running job
java.lang.NullPointerException
at
com.xpn.xwiki.plugin.watchlist.WatchListNotifier.sendEmailNotification(WatchListNotifier.java:84)
at
com.xpn.xwiki.plugin.watchlist.WatchListJob.executeJob(WatchListJob.java:262)
at
com.xpn.xwiki.plugin.scheduler.AbstractJob.execute(AbstractJob.java:75)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
java.lang.NullPointerException
at
com.xpn.xwiki.plugin.watchlist.WatchListNotifier.sendEmailNotification(WatchListNotifier.java:84)
at
com.xpn.xwiki.plugin.watchlist.WatchListJob.executeJob(WatchListJob.java:262)
at
com.xpn.xwiki.plugin.scheduler.AbstractJob.execute(AbstractJob.java:75)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
as you can see, the message is not very explanative, and can't find out any
solution. I already tried to unschedule -> change the fire time ->
reschedule. Is there an already known issue and, maybe, its solution? The
hourly scheduler works (good) as before, so i don't think this problem is
about malformed documents.
Any idea?
Thanks a lot,
claudio
--
View this message in context: http://xwiki.475771.n2.nabble.com/watchlist-daily-notifier-doesn-t-work-tp5…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi guys,
I am trying to export my xwiki workspace so but every time i try it i get
the following error
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2882)
at
java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:100)
at
java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:390)
at java.lang.StringBuffer.append(StringBuffer.java:224)
at org.suigeneris.jrcs.rcs.impl.Node.toText(Node.java:719)
at org.suigeneris.jrcs.rcs.Archive.toString(Archive.java:914)
I know this is an error where the JVM has not enough memory. My JVM memory
settings are set as follows
set "JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=UTF8 -Duser.timezone=GMT
-Xmx1024m -XX:MaxPermSize=1024m"
Everytime i try to increase it to anything above the above values Tomact
does not startup. Any clues as to how i can fix this?
I am running xwiki on the following environment
Tomcat 6.0.29
Xwiki 2.4.3
Mysql 5.1
Windows Xp
Thanks
You guys are moving too fast for me.
I was busy trying to install release 2.5 and now i find out release 2.6 RC1
is already out.
I bet release 2.6 GA will be available when i finish installing release 2.5?
:)
Hello,
I try to test Activity macro in my Wiki (XWiki 2.5) with the provided sample:
{{recentactivity space="$doc.space" author="XWiki.Admin" tag="xwiki" /}}
and also
{{velocity}}
{{recentactivity space="$doc.space" author="XWiki.Admin" tag="xwiki" /}}
{{/velocity}}
Test page returns:
> Unknown macro: recentactivity
> The "recentactivity" macro is not in the list of registered macros. Verify the spelling or contact your administrator.
So my questions are:
1- Since which XWiki version Activity macro is bundled within XWiki?
2- Could we update all pages of macros bundled with XWiki with the
minimal XWiki version there are bundled with or at least the last
XWiki version we made significant update on?
Regards,
Arnaud.
Hi everybody!
I just started using XWiki and I'm liking a lot! But, I was having
some trouble with attachment versioning. I was using XWiki with Tomcat
as a Service with Windows Server and I couldn't sotre more than one
revision of my attachments. All the old attachment revisions were lost
after restarting XWiki...
The fast workaround is: Configure Tomcat to run as a User account, not
a System Account (in the service properties window).
The explanation is: XWiki uses a "kind of" CVS repository to store the
attachment revisions. When Tomcat is running as a service with a
System account, XWiki stores the author name with a "$". This
"corrupts" the repository and XWiki can't load it again! Using a User
account is a simple workaround for this! Maybe this could be changed
in the next version....
Best regards!
Felipe Luiz Christófolli Giotto
Linux User #497287
I can't use 'update' in HQL expressions in Velocity scripts. Stack trace:
org.xwiki.rendering.macro.MacroExecutionException: Failed to evaluate
Velocity Macro for content [{{html wiki="true"}}
{{/html}}
#if($request.searchDocumentsQuery)
== Ergebnis ==
#if(!$request.privapi||$request.privapi==''||$request.privapi=='false')
## Simple API
#set($results=$xwiki.searchDocuments($request.searchDocumentsQuery.trim()))
#else
## Privileged API, cp.
http://platform.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamples
#set($results=$xwiki.search($request.searchDocumentsQuery.trim()))
##
#set($results=$xwiki.queryManager.xwql($request.searchDocumentsQuery.trim()).execute())
#end
#foreach($result in $results)
* $result
#end
#end]
at
org.xwiki.rendering.internal.macro.velocity.VelocityMacro.evaluateString(VelocityMacro.java:125)
at
org.xwiki.rendering.internal.macro.velocity.VelocityMacro.evaluateString(VelocityMacro.java:44)
at
org.xwiki.rendering.macro.script.AbstractScriptMacro.evaluateBlock(AbstractScriptMacro.java:299)
at
org.xwiki.rendering.macro.script.AbstractScriptMacro.execute(AbstractScriptMacro.java:191)
at
org.xwiki.rendering.macro.script.AbstractScriptMacro.execute(AbstractScriptMacro.java:58)
at
org.xwiki.rendering.internal.transformation.MacroTransformation.transformOnce(MacroTransformation.java:184)
at
org.xwiki.rendering.internal.transformation.MacroTransformation.transform(MacroTransformation.java:129)
at
org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:85)
at
com.xpn.xwiki.doc.XWikiDocument.performSyntaxConversion(XWikiDocument.java:7401)
at
com.xpn.xwiki.doc.XWikiDocument.performSyntaxConversion(XWikiDocument.java:7351)
at
com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:829)
at
com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:780)
at
com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:872)
at com.xpn.xwiki.api.Document.getRenderedContent(Document.java:527)
at sun.reflect.GeneratedMethodAccessor263.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:389)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:378)
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:252)
at
org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:493)
at
org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
at
org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
at
org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:196)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:161)
at
com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:116)
at com.xpn.xwiki.XWiki.evaluateTemplate(XWiki.java:1855)
at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1793)
at com.xpn.xwiki.api.XWiki.parseTemplate(XWiki.java:896)
at sun.reflect.GeneratedMethodAccessor118.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:389)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:378)
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:252)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:332)
at
org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:212)
at
org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:247)
at
org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175)
at
org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87)
at
org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:196)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:161)
at
com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:116)
at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1903)
at com.xpn.xwiki.XWiki.evaluateTemplate(XWiki.java:1825)
at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:155)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:225)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:129)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at
org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:218)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at
org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
at
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
at
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:536)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:930)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:405)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: org.xwiki.velocity.XWikiVelocityException: Failed to evaluate
content with id [xwiki:Sandbox.tst-2010-11-05-001]
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:205)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:161)
at
org.xwiki.rendering.internal.macro.velocity.VelocityMacro.evaluateString(VelocityMacro.java:118)
... 93 more
Caused by: org.apache.velocity.exception.MethodInvocationException:
Invocation of method 'search' in class com.xpn.xwiki.api.XWiki threw
exception com.xpn.xwiki.XWikiException: Error number 3223 in 3: Exception
while searching documents with sql update XWikiDocument doc set
doc.title='asdf poiu quer' where doc.fullName='tst-2010-11-03-lIqw'
Wrapped Exception: Not supported for DML operations [update
com.xpn.xwiki.doc.XWikiDocument doc set doc.title='asdf poiu quer' where
doc.fullName='tst-2010-11-03-lIqw'] at xwiki:Sandbox.tst-2010-11-05-001[line
30, column 22]
at
org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337)
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:252)
at
org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:493)
at
org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
at
org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
at
org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106)
at
org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:196)
... 95 more
Caused by: com.xpn.xwiki.XWikiException: Error number 3223 in 3: Exception
while searching documents with sql update XWikiDocument doc set
doc.title='asdf poiu quer' where doc.fullName='tst-2010-11-03-lIqw'
Wrapped Exception: Not supported for DML operations [update
com.xpn.xwiki.doc.XWikiDocument doc set doc.title='asdf poiu quer' where
doc.fullName='tst-2010-11-03-lIqw']
at
com.xpn.xwiki.store.XWikiHibernateStore.search(XWikiHibernateStore.java:2398)
at
com.xpn.xwiki.store.XWikiHibernateStore.search(XWikiHibernateStore.java:2327)
at
com.xpn.xwiki.store.XWikiHibernateStore.search(XWikiHibernateStore.java:2315)
at com.xpn.xwiki.store.XWikiCacheStore.search(XWikiCacheStore.java:660)
at com.xpn.xwiki.XWiki.search(XWiki.java:1728)
at com.xpn.xwiki.api.XWiki.search(XWiki.java:512)
at sun.reflect.GeneratedMethodAccessor458.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:389)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:378)
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270)
... 106 more
My script is basically:
{{velocity filter="indent"}}
#set($searchDocumentsQuery="update XWikiDocument doc set doc.title='asdf
poiu quer' where doc.fullName='tst-2010-11-03-lIqw'")
#set($results=$xwiki.search($searchDocumentsQuery))
{{/velocity}}
Am I missing something?
(XWiki 2.2 and 2.4.)
--
View this message in context: http://xwiki.475771.n2.nabble.com/Failed-to-execute-the-velocity-macro-DML-…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello,
I would like to use this wiki for the purpose of exchanging informations
with colleagues involved in a collaborative research project in my
university and abroad.
my user name is pascalvenier
I would like to use the following server name for the wiki: complexite
Merci d'avance.
Pascal
Hello,
I am having some issues with the "order by" clause in HQL - the following
query:
$xwiki.searchDocuments("where doc.hidden = false and doc.id='${doc.parent}'
order by doc.title asc")
is returning the expected set of documents, but the title order is erratic.
The documents are reordered, but it is not alphabetized as anticipated.
Instead, there are several alphabetized "spurts" -- for example, I have 'A',
'C', 'P', ... 'A', 'A', 'B', 'C', 'D', 'E', etc. Within one of these spans,
no items appear out of order, but the 'span' separation is not expected or
desired. Is there a common issue that I could be overlooking?
Thank you,
Chris
--
View this message in context: http://xwiki.475771.n2.nabble.com/Unexpected-Order-By-Results-tp5702753p570…
Sent from the XWiki- Users mailing list archive at Nabble.com.
The XWiki development team is pleased to announce the release of XWiki
Enterprise 2.5.1 and XWiki Enterprise Manager 2.5.1. These are bugfix
releases on the 2.5 branch.
The highlights of this release are: fixed and improved the PDF export,
fixed broken images from the office importer, fixed a severe performance
problem with many blog categories, and fixed broken scheduler functionality.
For more information, see the full release notes at:
- http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXWikiEnterprise251.
- http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXEM251.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
This may sound like a daft question and I ask in advance for your
forbearance for a neophyte.
I am attempting to have a wiki created on myxwiki.org and have followed to
the letter the instructions given:
"If you’re interested in having a wiki hosted on this farm please send an
email to the XWiki user mailing list with a subject of [myxwiki] new wiki
request and explaining briefly what you want to use this wiki for (give a
brief description). You’ll also need to register on myxwiki.org and give
your user name in the mail, as well as the server name you want for your
wiki (the name that will be used before .myxwiki.org to access the wiki).
Then one of the community Admins will create it for you"
However nothings seems to happen. Could someone please be of assitance.
Many thanks in advance.
Pascal Venier
Hi Mark,
On Nov 5, 2010, at 2:37 AM, mwallace(a)modusoperandi.com wrote:
>
> Apology for cross posting.
> Can someone point me to where in the XWiki code I could implement an
> extended XWiki link syntax? E.g. if I'd like to handle something like
> this:
> Berlin is a city in [[locatedIn::Germany>>Germany]]
> where I'm adding the double-colon syntax before the usual link info.
This is so cool that you have this need since we've just implemented extensibility for this in XE 2.5+:
http://jira.xwiki.org/jira/browse/XWIKI-5486
The doc is now available at:
http://code.xwiki.org/xwiki/bin/view/Modules/RenderingModule#HAddinganewLin…
Thanks
-Vincent
Hello,
I've just updated a 2.4 test installation to 2.5 and when accessing the
first page I got an exception: the WYSIWYG plugin is missing and so the
WYSIWYG editor is disabled. I guessed I should find it in
xwiki-web-gwt-wysiwyg-server-2.5.jar but there is no editor class
included. In the older versions the class was available?!
Is there a quick fix available?
Best wishes
Werner Greßhoff
On 11/01/2010 12:50 PM, Gregory GUENEAU wrote:
> Hi everyone,
>
> I am +1 to make stabilization work, on a couple of releases
> I am +1 to have soon a 3.0 release
> And i am +1 on the content vincent propose
>
> But my point of view is -1 stepping the release family number because the main purpose of what is discussed here is stabilization, and not showing the path of 3.x family.
>
> Therefore :
> - do we consider a january 2011 release to be stable enough ?
> - stabilization work wouldn'it be leading then to the last 2.x version instead of the first 3.x family version ?
> - is there behind it a consensus on what we will concentrate our effort in 3.x versions ? I mean thematics we can talk about.
> - therefore, are we in a situation where we can vote on the global thematics we will develop in 3.x releases ?
> - do we have a clear consensus short list of features that show the path of 3.x family ?
> - in consequence of that, is the release content here send a clear message to uneducated publics about what is in this future 3.x versions ?
> - do educated people care this much about release number, that we absolutely have to release a 3.0 with the content presented below ?
From the committers' point of view, it makes perfect sense for 3.0 to
be the culmination of the 2.x releases, but I'm not sure the users
understand this as well, so I'm extending the question to the users list.
Traditionally, proprietary software is developed behind the curtains,
and it's normal to have one big release every two years, with lots of
new features and some bugs which get fixed in subsequent bugfix
releases. Marketing comes mostly from the proprietary software world, so
from a marketing point of view, this is the "normal" way releases work.
In the open source world, since the development is done in the open, it
doesn't make sense to stash code away in a repository and only release
it once every two years. Still, most big projects use a release
versioning scheme similar to the proprietary products, but with a slight
difference which deeply changes the meaning. While proprietary products
use only a number (3, 8, 2010...), with eventual bugfixes versions (SP2,
5.5), open source usually has 3 numbers in its versions, with the
following meanings:
The first number changes rarely, and when it does, it signals a critical
change, like a complete rewrite of the codebase, a change of paradigm,
or major new features. The second number is the one that actually
identifies a release. The third number is the bugfix version. So, when
we say that PHP 5.3.2 was released, we actually say that version 3 of
PHP5, which is a different thing than PHP4, has been released again,
giving the second bugfix release. KDE 4.5.1 means version 5 of KDE4 saw
its first bugfix release.
Another tendency is for open source software to linger towards a major
release. For example, lots of software have a lot of releases before
1.0, going nearer and nearer: 0.6, 0.9, 0.9.9... And everybody knows
that 0.x comes before 1.0, and it's not just a bugfix version of an
imaginary 0.0 release.
A different topic is that of agile development, with very short releases
(2-3 weeks) for which traditional version number make no sense, since
such a product would reach version 42 in a couple of years. Either an
identifier, such as the SCM version number is used, or a continuous
counter (v1.42) is used. Since the software evolves in a fluid manner,
without a "breakthrough" version coming out of the regular releases, a
"major" version is released when the current features are stable and
they mix well together in a coherent product. Since releases come so
frequently, it's normal for users to be split into two categories: those
that follow the releases and know how the software is evolving, and
those that only monitor the major releases, and which see all the
continuous improvements at once.
While XWiki Enterprise is used in the enterprise environment, and it is
backed by commercial companies, it is a true open source project,
following an open source release model, so I don't think that a
proprietary product release scheme is suited.
Our development/release style is closer to the agile development
practice, albeit with mixed release types. In the future, once the core
is more stable than it is now, we'd like to move even closer to a full
agile release process, with 2-3 weeks between final releases. Thus, I
believe that the last release versioning strategy is the best for XWiki
Enterprise.
Note that we're already using this strategy in a more obvious way for
smaller modules (applications, skins, tools), where we do have 1.32 as a
stable version number.
Also note that although 1.9 was followed by 2.0, this was just a
coincidence, and not a natural version evolution, since we also felt
that the code was mature enough to receive a major number bump, but it
could just as well have been followed by a 1.10.
So, there are two different opinions here. One that 3.0 should present
the groundwork/roadmap for the following 3.x releases, and one that 3.0
should be the culmination of the work done so far on the 2.x releases.
The committers (with the exception of Ludovic) believe that the latter
is the better one, and it is in accordance with what we've been doing so
far. What do our users think?
As a final remark, the XWiki Open Source projects are governed by the
committers, so in the end the decision lies in the hands of the
developers, but we're always open to the larger community. If no
consensus is reached about when to release 3.0, we will continue
releasing 2.x versions.
What do XWiki users think? Is 3.0 as a culmination of the 2.x releases,
with no major new features besides what 2.5 already provides, something
the community expects?
> We have to make 100% sure our message will be understood by market. We are now in the Gartner magic quadrant and will increase our visibility outside the opensource community. In a world where new release number families means : "we show the path of the future of this software, even if the features we present are not perfect", i will strongly promote to answer in details the questions i mentionned before deciding 2.8 to be in fact 3.0.
XWiki SAS is in the Gartner report, as a vendor. The XWiki Enterprise
project is not in that report. I think the marketing direction that
Gregory and Ludovic are supporting is better suited for the company
offerings.
> Then here is the two elements that are probably the biggest things in the roadmap for 3.x versions :
> - going social (workspaces in xem, twitter like app, page stats for the user, etc.)
> - going to be an easy place to develop in (extension manager of course, but also documentation for dummies and a first app like "app within minute" proposed by guillaume and strongly needed by our front team)
>
> Is there a consensus on this list ? Then what should be the "demo" features we could present to be consistent for a 3.0 release ?
Yes, these should be central in the future 3.x releases, but not in 3.0,
which should be as stable as possible, without any "demo" features.
> Best
>
>
>
> On 1 nov. 2010, at 09:23, Vincent Massol<vincent(a)massol.net> wrote:
>
>> Hi everyone,
>>
>> Sergiu started mentioning the idea of a XE 3.0 when we defined the XE 2.6 roadmap. We need a more general agreement that we want a XE 3.0 and how to reach it.
>>
>> As Sergiu I believe we need a XE 3.0 ASAP for the following reasons:
>>
>> - it's been a bit more than 1 year since the XE 2.0 release and I feel it's good to have one major release every year
>> - we've added **lots** of features since XE 2.0. Check http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotes to get a feeling
>> - it's good for open source marketing
>>
>> Before being able to release XE 3.0 I think:
>>
>> - XE 2.6 is already planned for the 18th of November (with "mail this page" and "recent activity" features + icon/emoticon and wikiword support that was sneaked in surreptitiously)
>> - We should have a XE 2.7 release (1 month duration, ie leading us to the 18th of December) to finish started stuff:
>> -- Finish the Gadget integration since it's been started already and it's important. That said I'd actually be ok to not finish it if we think it's too much to release XE 3.0 quickly according to the dates below. Anca to tell us if it's possible in the timeframe.
>> -- First working extension manager that can be used to install XARs (replaces the old Packager on the back end side). Thomas to tell us if it's possible in the timeframe.
>> -- Recent Activity with apps sending events (XE 2.6 will already have a good part of it)
>> -- UI finishing touches
>> -- Some additional Security and Performance improvements if possible
>> -- etc (add what you'd like to see absolutely here - it should be work already started as much as possible and no new stuff)
>> - Release XE 3.0 one month after the XE 2.7 release, ie around 18th of January - ie end of January 2011)
>>
>> Very important: XE 3.0 should be a maturation/conclusion release, i.e. concluding all the work started in the 2.x series (same as what we did for XE 2.0). It shouldn't be seen as revolutionary stuff that we should add from now on since it'll take a year more before those can be fully stabilized and we would loose the window of opportunity of doing a major release now.
>>
>> Note: We shouldn't try to cram too much things in since that'll extend the lead time to release XE 3.0 and we'll loose the stabilization effect.
>>
>> WDYT?
>>
>> Thanks
>> -Vincent
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
You can access your new wiki on http://vg-concept.myxwiki.org
Enjoy :)
On Wed, Nov 3, 2010 at 21:00, Vladimir Goloubtzoff
<vladimir.goloubtzoff(a)gmail.com> wrote:
> Hi
> My register on myxwiki.org. is Vladimir
> Could you please activate my account
> Thanks
>
> 2010/11/3 Thomas Mortagne <thomas.mortagne(a)xwiki.com>
>>
>> Hi,
>>
>> You are supposed to register yourself on myxwiki.org.
>>
>> On Mon, Nov 1, 2010 at 11:35, Vladimir Goloubtzoff
>> <vladimir.goloubtzoff(a)gmail.com> wrote:
>> > Hi,
>> >
>> > As stated in my previous mail my wiki account has not yet been
>> > activated.
>> > Could you please take any necessary steps to activate my account?
>> > Thank you in advance
>> > Yours truly,
>> >
>> > 2010/10/28 Vladimir Goloubtzoff
>> >
>> >> Hi,
>> >> i would like to realize articles, manuals and activities
>> >> about the Internet, and the web.
>> >> username : vladimir
>> >> server name : vg-concept.myxwiki.org
>> >> Thank you.
>> > _______________________________________________
>> > users mailing list
>> > users(a)xwiki.org
>> > http://lists.xwiki.org/mailman/listinfo/users
>> >
>>
>>
>>
>> --
>> Thomas Mortagne
>> _______________________________________________
>> users mailing list
>> users(a)xwiki.org
>> http://lists.xwiki.org/mailman/listinfo/users
>
>
--
Thomas Mortagne
Hi,
i would like to realize articles, manuals and activities
about the Internet, and the web.
username : vladimir
server name : vg-concept.myxwiki.org
Thank you.
Hi,
I would like to realize activities, informational materials, personal
presentations.
Also, I assume to share with community materials about xwiki, prepared
myself.
username : ecolesnicov
server name : etvc.myxwiki.org
Thanks beforehand!
Eugen Colesnicov
--
View this message in context: http://xwiki.475771.n2.nabble.com/myxwiki-new-wiki-request-tp5690825p569082…
Sent from the XWiki- Users mailing list archive at Nabble.com.
I wanna a wiki to storage my small pice of idears, and diary.
I have a xwiki instlled at my co's pc, but I can't access it at home.
THX! ( Sorry for my bad english. )
Hi!
I'm trying to list the users' name in a form, but the name have complement
(p.e. Name: Carlos Eduardo da Silva / HR - manager). As in a "List of users"
property, I want to display, when someone is selecting a name, the full name
and complement, but when displaying in the results I want it to show the
user's Alias.
So what I did was a class (XWiki.dbClass) with two properties:
Name (String) (p.e. Carlos Eduardo da Silva / HR - manager)
Alias (String) (p.e.Carlos)
Which I used as a DataBase to the property "Name" in the other class
(XWiki.formClass).
So, I chose for this property:
XWiki Class Name: XWiki.dbClass
Id Field Name: Name
Value Field Name: Alias
But the result was not as in a "List of Users" property, in which when one
choose for example "Carlos Eduardo da Silva" the result in the table is
"Carlos".
The result was that both, selected and diplayed information, are in this
example "Carlos".
And another thing... I didn't understand the DB Tree property. One thing
that worked was:
XWiki Class Name: XWiki.dbClass
Id Field Name: doc.fullName
Value Field Name: Alias
Parent Field Name: doc.parent
But I don't understand the meaning of that...
Can anyone help me ?
--
Atenciosamente,
Erica Usui.
Hi XWikiers,
Each night, my wiki farm is stopped during the backup of the database.
In the morning, when the first user connects to the wiki, the following
error appears in the xwiki.log :
[http://localhost/xwiki/bin/loginsubmit/XWiki/XWikiLogin] ERROR
nager.ApplicationManagerPlugin - Refresh all applications translations
informations
com.xpn.xwiki.XWikiException: Error number 3223 in 3: Exception while
searching documents with SQL [, BaseObject as obj where doc.fullName=
obj.name and obj.className=? and doc.fullName<>?]
Wrapped Exception: null
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:2588)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:3037)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:3001)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:2989)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:2941)
at
com.xpn.xwiki.store.XWikiCacheStore.searchDocuments(XWikiCacheStore.java:552)
at
com.xpn.xwiki.plugin.applicationmanager.core.doc.objects.classes.AbstractXClassManager.searchXObjectDocumentsByFields(AbstractXClassManager.java:938)
at
com.xpn.xwiki.plugin.applicationmanager.core.doc.objects.classes.AbstractXClassManager.searchXObjectDocuments(AbstractXClassManager.java:900)
at
com.xpn.xwiki.plugin.applicationmanager.ApplicationManager.getApplicationList(ApplicationManager.java:129)
at
com.xpn.xwiki.plugin.applicationmanager.ApplicationManager.updateAllApplicationTranslation(ApplicationManager.java:310)
at
com.xpn.xwiki.plugin.applicationmanager.ApplicationManagerPlugin.init(ApplicationManagerPlugin.java:122)
at
com.xpn.xwiki.plugin.XWikiPluginManager.initPlugin(XWikiPluginManager.java:153)
at
com.xpn.xwiki.plugin.XWikiPluginManager.addPlugin(XWikiPluginManager.java:90)
at
com.xpn.xwiki.plugin.XWikiPluginManager.addPlugins(XWikiPluginManager.java:118)
at com.xpn.xwiki.XWiki.preparePlugins(XWiki.java:1155)
at com.xpn.xwiki.XWiki.initXWiki(XWiki.java:827)
at com.xpn.xwiki.XWiki.<init>(XWiki.java:756)
at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:383)
at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:471)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:136)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:129)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:304)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at
org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:861)
at
org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
at
org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1584)
at java.lang.Thread.run(Thread.java:619)
Wrapped Exception:
java.lang.IllegalStateException
at
org.apache.catalina.connector.ResponseFacade.sendRedirect(ResponseFacade.java:435)
at
com.xpn.xwiki.user.impl.xwiki.MyFormAuthenticator.showLogin(MyFormAuthenticator.java:95)
at
com.xpn.xwiki.user.impl.xwiki.MyFormAuthenticator.showLogin(MyFormAuthenticator.java:64)
at
com.xpn.xwiki.user.impl.xwiki.XWikiAuthServiceImpl.showLogin(XWikiAuthServiceImpl.java:396)
at
com.xpn.xwiki.user.impl.xwiki.XWikiRightServiceImpl.checkAccess(XWikiRightServiceImpl.java:211)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:2565)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:3037)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:3001)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:2989)
at
com.xpn.xwiki.store.XWikiHibernateStore.searchDocuments(XWikiHibernateStore.java:2941)
at
com.xpn.xwiki.store.XWikiCacheStore.searchDocuments(XWikiCacheStore.java:552)
at
com.xpn.xwiki.plugin.applicationmanager.core.doc.objects.classes.AbstractXClassManager.searchXObjectDocumentsByFields(AbstractXClassManager.java:938)
at
com.xpn.xwiki.plugin.applicationmanager.core.doc.objects.classes.AbstractXClassManager.searchXObjectDocuments(AbstractXClassManager.java:900)
at
com.xpn.xwiki.plugin.applicationmanager.ApplicationManager.getApplicationList(ApplicationManager.java:129)
at
com.xpn.xwiki.plugin.applicationmanager.ApplicationManager.updateAllApplicationTranslation(ApplicationManager.java:310)
at
com.xpn.xwiki.plugin.applicationmanager.ApplicationManagerPlugin.init(ApplicationManagerPlugin.java:122)
at
com.xpn.xwiki.plugin.XWikiPluginManager.initPlugin(XWikiPluginManager.java:153)
at
com.xpn.xwiki.plugin.XWikiPluginManager.addPlugin(XWikiPluginManager.java:90)
at
com.xpn.xwiki.plugin.XWikiPluginManager.addPlugins(XWikiPluginManager.java:118)
at com.xpn.xwiki.XWiki.preparePlugins(XWiki.java:1155)
at com.xpn.xwiki.XWiki.initXWiki(XWiki.java:827)
at com.xpn.xwiki.XWiki.<init>(XWiki.java:756)
at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:383)
at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:471)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:136)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:129)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:152)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:304)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at
org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:861)
at
org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
at
org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1584)
at java.lang.Thread.run(Thread.java:619)
Does someone else encounter the same issue ? Is this related to an open bug
? If you have any idea, don't hesitate to reply me.
Best regards,
Maxime Mathieu