May 2016 - xwiki-users@xwiki.org

[xwiki-users] Upgrade to 8.2: Failed to execute the [velocity] macro.
by rfr 08 May '16

08 May '16

Dear List, After a Debian Upgrade from Wheezy to Jessie, my XWiki 7.2 was also upgraded. But during the upgrade process, it seems there were some conflicts I did not really bother as the system told me it could manage them (Maybe I was a bit naive at this point ...). After the upgrade process finished, I landed on my XWiki with all the pages filled with "Failed to execute the [velocity] macro. Click on this message for details." Even the Admin user cannot access admin pages due to the error. I tried to dig in the database to find if I could resolve the problem but I did not succeed. Do you have any pointer on how to solve the issue? Thanks for all! Best Regards, Frédéric

3 8

[xwiki-users] Date format in FAQ application
by Ryszard Łach 06 May '16

06 May '16

Hi, again. How can I correct date format (to include leading zeros) in faq application? I suppose, that changing the default language of my wiki to 'pl' has broken the format and now 'Creation date' in list of faq entries looks like '2016-04-15 09:6:34' . TIA, R.

5 7

[xwiki-users] Missing menu bar
by dullfig 04 May '16

04 May '16

Hello: I installed XWiki 8.0 in tomcat 9 under windows 2008; The menu bar is missing!! I thought this was the new layout of the screen, but I looked up some screenshots, and apparently there is supposed to be a menu bar right next to the xwiki logo, with "home" "add" "space" "page" items just like in 6.0. Why is it not showing in my installation? I tried both chrome and ie. Dan -- View this message in context: http://xwiki.475771.n2.nabble.com/Missing-menu-bar-tp7599328.html Sent from the XWiki- Users mailing list archive at Nabble.com.

5 9

[xwiki-users] Cannot use Macros as the source for an image
by Peredo, Francisco 04 May '16

04 May '16

Hi! A few days ago I summited this as a bug http://jira.xwiki.org/browse/XRENDERING-448. I would like to thank Vincent for the quick response on it, but am a little surprised by the response and the change from "Bug" into "New Feature" request, because to me this feels like a bug in syntax precedence, where syntax tokens have a higher order of operations than the {{ }} macro syntax tokens when it should be the other way around: The macro should have higher precedence in the syntax tree and get evaluated before being used as a source for the image tag. In my opinion that would provide the most flexible and dynamic behavior for Xwiki users. Can someone on this email list share more information on the rationale behind this design decision? Thanks Regards, Francisco Peredo

2 2

[xwiki-users] Running a second xwiki instance in a single apache tomcat installation
by Sebastian Schabbach 04 May '16

04 May '16

Dear all, thanks for your help regarding to my question about ACE related javascript errors when editing xwiki articles a few days ago. As we figured out it is likely not an issue regarding tot he xwiki system and come in from a particular addon. Due to the fact, that is is not easily trackable for us which addon is working wrong, we want to setup a second xwiki instance with a new database and without extentions. This is only to ensure the errors weg et is not related to xwiki and to get a closer view to the issue. We tried simply to run a second xwiki using apache tomcat using an webapp directory called "xwiki2" with a xwiki 7.4.2 WAR-Distribution and the default (empty) HSQL Database. But this seems not to work due to the following issue. Could someone help me with fixing that issue? Kind Regards, Sebastian. Here is what the error is about: HTTP Status 500 - Failed to locate an ExtendedURL Resource Type Resolver component type Exception report message Failed to locate an ExtendedURL Resource Type Resolver component description The server encountered an internal error that prevented it from fulfilling this request. exception javax.servlet.ServletException: Failed to locate an ExtendedURL Resource Type Resolver component org.xwiki.resource.servlet.RoutingFilter.getResourceTypeResolver(RoutingFilter.java:181) org.xwiki.resource.servlet.RoutingFilter.doFilter(RoutingFilter.java:103) [...] org.xwiki.cache.CacheException: Failed to get cache factory for role hint [infinispan] org.xwiki.cache.internal.DefaultCacheManager.createNewCache(DefaultCacheManager.java:109) org.xwiki.cache.internal.DefaultCacheManager.createNewCache(DefaultCacheManager.java:85) org.xwiki.wiki.internal.manager.WikiDescriptorCache.createCache(WikiDescriptorCache.java:67) org.xwiki.wiki.internal.manager.WikiDescriptorCache.initialize(WikiDescriptorCache.java:58) org.xwiki.component.embed.InitializableLifecycleHandler.handle(InitializableLifecycleHandler.java:39) org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:322) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392) org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190) org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363) org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392) org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190) org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363) org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392) org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190) org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363) org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392) org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190) org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363) org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392) org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190) org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363) org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392) org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190) org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363) org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392) org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:190) org.xwiki.component.embed.EmbeddableComponentManager.getDependencyInstance(EmbeddableComponentManager.java:363) org.xwiki.component.embed.EmbeddableComponentManager.createInstance(EmbeddableComponentManager.java:312) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:424) org.xwiki.component.embed.EmbeddableComponentManager.getComponentInstance(EmbeddableComponentManager.java:392) org.xwiki.component.embed.EmbeddableComponentManager.getInstance(EmbeddableComponentManager.java:184) org.xwiki.resource.servlet.RoutingFilter.getResourceTypeResolver(RoutingFilter.java:177) org.xwiki.resource.servlet.RoutingFilter.doFilter(RoutingFilter.java:103)

2 2

[xwiki-users] [ANN] CKEditor Integration v1.5 Released
by Marius Dumitru Florea 04 May '16

04 May '16

Hi all, A new version of the CKEditor Integration extension is available. See http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration#H… . You can install or upgrade with the Extension Manager. Thanks, Marius

3 3

[xwiki-users] [Proposal] Plan for replacing XWiki's GWT-based WYSIWYG editor with the CKEditor-based one
by vincent＠massol.net 03 May '16

03 May '16

Hi everyone, I’d like to give everyone some heads up about the plan I discussed with Marius (who’s working on the new CKEditor integration) regarding the new CKEditor-based WYSIWYG. Goals: ====== * Replace the current GWT-based WYSIWYG editor with one based on CKEditor, see http://extensions.xwiki.org/xwiki/bin/view/Extension/CKEditor+Integration * Keep it as an extension so that it can be installed using the Extension Manager on XWiki versions 7.4.x. We need to introduce some UIXP to be able to replace the existing editor in the XWiki menus so we’ll need to commit that in 7.4.x (with x >= 2). * Make it possible to install the extension on XWiki versions 6.2.5+. However the installation will have some manual parts, to replace the GWT-based editor. Timeline: ========= * Before the 19th of Feb, a new version of the CKEditor integration will be released containing wiki page/attachment linking and image insertion features. At that point what will remain is: ** Support for editing macros ** Office importer (if needed) ** Configuration UI in the administration ** Add UIXP to integrate the CKEditor nicely into the platform (using extension points) ** Future: Add support for packaging CKEditor plugins as XWiki Extension. * The goal is to implement all these remaining features around when 8.1M1 is released (i.e. early April 2016), except maybe the Future part which could be done later on. * Starting 8.1M2, the goal would be to bundle the Extension in the distribution (default flavor) but to not make it the default yet. There would be some configuration option to select which WYSIWYG editor to use (GTW-based or CKEditor-based). * Starting 8.2, if all goes alright, we would set the CKEditor WYSIWYG to be the default (still with ability for admins to configure the editor they wish to use so they can continue to use the GWT-based one if they want that). * Starting 9.0, the idea would be to remove the GWT-editor and retire it to XWiki Contrib with instructions for advanced developers to build it and use it in XWiki should they still want to do that. However we won’t spend extra time to refactor it as an extension since that would spend too much time which we prefer to spend on improving the new WYSIWYG editor. WDYT? Thanks -Vincent PS: cc-ing the users list to let the XWiki users know about the plan ahead of time!

2 1

[xwiki-users] Sort Array of Objects
by Rochlin Oleg 03 May '16

03 May '16

Hello again. I don´t have really much knowledge in Velocity. So right now begging for help :D #set($users = $xwiki.rightsmanager.usersApi.allUsers) #foreach($user in $users) I am getting an array of objects(user in xwiki). $users-array should be sorted by familyname Here is the snippet from https://velocity.apache.org/tools/devel/javadoc/org/apache/velocity/tools/g… I am still kinda confused how to apply this on mine Single Property Sort #foreach($obj in $sorter.sort($objects, "name")) $obj.name Ordinal= $obj.ordinal #end End Thank you, guys =)

2 1

[xwiki-users] Admin Rights on myxwiki.org
by Ldm Public 03 May '16

03 May '16

Hi, I run the Wiki http://tutos.myxwiki.org on the community farm and search crashed with "Solr query require programming right" error ... does someone can save the required pages with the correct rights ? or better solution can give me "programming rights"? Regards,

3 3

Re: [xwiki-users] How to avoid nested space?
by vincent＠massol.net 03 May '16

03 May '16

Hi, On 5 Jan 2016 at 10:09:27, KirbY ZhoU (kirbyzhou@gmail.com(mailto:kirbyzhou@gmail.com)) wrote: > Sorry for reply so later, I have taken a vacation for days. Hope you had some nice holidays! :) > Actually, I modified Dashboard.WebHome after upgrade, and use {{spaces}} macro which comes from 7.3 release. > Now I replace {{spaces}} with {{documentTree}}, but I have some little problem. > 1. I want to avoid "xxx more", but limit=100 do not work. > 2. I want to limit the tree level, but I have no idea. All documentation for the tree macro can be found at http://extensions.xwiki.org/xwiki/bin/view/Extension/Document+Tree+Macro AFAIK there’s currently no way to configure how many items to display before “xxx more” appears. @Marius: is that correct? It seems it would be useful to have this in the future if that’s the case. WDYT? Do we have a jira issue about it already? I’m not sure what’s your use case for point 2. I guess you mean limit the hierarchy but it seems it would prevent users from navigating correctly so I’m not sure what’s the use case. Thanks -Vincent > 发件人: Vincent Massol 代表 "vincent@massol.net(mailto:vincent@massol.net)" > 日期: 2015年12月23日星期三下午7:35 > 至: KirbY ZhoU , XWiki Users > 主题: Re: [xwiki-users] How to avoid nested space? > > Hi, > > The default dashboard is located in Dashboard.WebHome. When you upgraded you should have had the Distribution Wizard upgrade that page. Was that the case? Could you check the history for that page? > > Now two things could have happened: > > 1) you overwrote the changes brought by the Distribution Wizard by importing old versions of pages from your previous wiki. If you’ve done that then you’ve most likely broken the upgrade process since you’ve removed all the upgrades that were required to all default wiki pages! :) See http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Upgrade for the canonical way of upgrading an XWiki instance. If you’ve done that I suggest that you redo the upgrade. > > 2) you have modified Dashboard.WebHome. If this is the case then you’ll need to update your version to use the {{documentTree}} macro instead of the spaces macro. > > As I’ve mentioned already in my reply the notion of Spaces have been removed from the UI (I’ve linked you to some page with the explanation, have you been able to read that page? was it clear? should we improve things there with more explanations?). > > Thanks > Hope it helps, > -Vincent > > > > On 23 Dec 2015 at 12:19:45, KirbY ZhoU (kirbyzhou@gmail.com(mailto:kirbyzhou@gmail.com)) wrote: > > > I belived that I have use the space widget version 7.3. > > I created a new Xwiki-7.3, and then import the old spaces one by one, excluding 'Main', 'XWiki' and all spaces coming with Xwiki default pages. > > > > I just want to get a simple space list. > > > > > > > > 发件人: Vincent Massol 代表 "vincent@massol.net(mailto:vincent@massol.net)" > > 日期: 2015年12月23日星期三上午4:41 > > 至: XWiki Users > > 抄送: KirbY ZhoU > > 主题: Re: [xwiki-users] How to avoid nested space? > > > > Hi KirbY, > > On 22 Dec 2015 at 21:27:47, KirbY ZhoU (kirbyzhou@gmail.com(mailto:kirbyzhou@gmail.com)(mailto:kirbyzhou@gmail.com)) wrote: > > > > > How to avoid nested space? > > > > > > Since the new nested space feature, a lot of nested space such as "XXX.YYY" appears in the "Space List" in my home page. > > > If I want to create a sub page, a new nested space created silently. It becomes more and more, and bothers our users. > > > > > > I want keep the original simple one level space and documents tree model instead of the new nested space model. How can I get it? > > > > The issue is that you haven’t upgraded your home page (the dashboard I presume). We have replaced the Space widget with a Documents widget. Normally, when you have upgrade you should have had the Distribution Wizard kicking in and updating the default wiki pages. Please let us know what you’ve done when the Distribution Wizard has executed. > > > > The notion of Spaces has been removed starting with XWiki 7.2+ > > > > Please see http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization > > > > The introduction of Nested Spaces is a large change and we wish to make it as seamless as possible to our users. Please let us know any issue you see and we’ll try to help you and see if we can improve things by default so that other users have less problems upgrading. > > > > Thanks for your help and patience. > > -Vincent > >

4 8