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

[xwiki-devs] [Proposal] Content menus re-organization
by Guillaume "Louis-Marie" Delhumeau 08 Oct '15

08 Oct '15

Hi. With 7.2, the content menus have changed a lot. The pain point is that we have a too much crowded "more actions" menu. Some discussions have already been done on this jira issue: http://jira.xwiki.org/browse/XWIKI-12587 Caty have created a design page to re-organize the menus: http://design.xwiki.org/xwiki/bin/view/Proposal/NestedMenuReorganization I'm in favor of the solution 1.2. So: * -0 for solution 1.1 since the viewers are not what we use the most (thanks to the extra tabs on the bottom) and it gives them too much importance * +1 for solution 1.2, even if we might encounter some difficulties saying if an item is a base action or an advanced one. * 0 for option A (too much clicks), but on the other hand I don't have an alternative to propose. * +1 for option B. The jira issue is already created ( http://jira.xwiki.org/browse/XWIKI-12636) and I think nobody would be opposed to this. * +0 for option C. The browser already have this ability, and yes, it implies the hiding of the panels (thanks to some CSS we have). However, I remember a client using this feature for a convoluted use-case: include a light wiki page in an other website via an iframe. Anyway, we could still keep the viewer but remove the link. * +1 for D. I know that security through obscurity is not the best, but it disturbs me to let an access to the source code of any wiki page, including not-well-done applications created by users. Thanks, Guillaume -- Guillaume Delhumeau (gdelhumeau(a)xwiki.com) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project

7 12

[xwiki-devs] [Contrib] XWebIDE Improvements
by Yann Flory 07 Oct '15

07 Oct '15

Hello devs, Recently, a new version of the XWebIDE ( http://extensions.xwiki.org/xwiki/bin/view/Extension/XWebIDE+Application) has been published which added the ability to work with Nested spaces in the application. In order to progress with the development of the extension, we've made a list of future relevant features to add to the application. We'd now like to have your opinion about the importance of each one of them (order the features based on their priority) and your ideas for new ones. You can find the list and add your vote in the table in the design wiki : http://design.xwiki.org/xwiki/bin/view/Proposal/XWebIDE+Application+Improve… We'd also like to know what are the required features which make you believe you'll use the application in the future. And feel free to provide any other feedback you may have about the current version of the XWebIDE application. Thanks, Yann

6 8

[xwiki-devs] [Proposal] New testing framework to write unit test of wiki pages
by vincent＠massol.net 05 Oct '15

05 Oct '15

Hi devs, In the past few days I’ve written the first version of a test framework to allow unit testing wiki pages in our build (see http://jira.xwiki.org/browse/XWIKI-12643) The advantages are: * No running XWiki required * Relatively fast to execute (<2s) and much faster than functional tests Some remarks: * It’s not meant to replace functional tests * What pushed me to work on this was that I wanted to provide a test for XWIKI-11524 (Do not display hidden documents in feeds) which I fixed a week ago or so but at the time I couldn’t do that easily. I would have had to write a functional tests and 1) there was no test at all existing and setting up the scaffolding is a bit heavy for this small use case 2) I didn’t want to penalize our build by a minute more or so just to validate that a “hidden/document” query filter is executed... Now it’s still an experiment at this stage as I don’t know how easy or hard it’ll be when writing unit tests for other pages and we’ll need to add more component declarations and setup for sure. On this topic we will need to start developing ComponentList annotation packs probably in order to not slow down execution of all wiki page tests. Let me know what you think and in case nobody likes it we can always remove it and move it to contrib. Thanks -Vincent

2 2

[xwiki-devs] [Proposal] Improve the management of inexistent WebHome with children
by Denis Gervalle 05 Oct '15

05 Oct '15

Hi devs, I am opening this discussion to move the discussion started in an issue (XWIKI-12628) to its proper place, the ML. (Discussing into JIRA is very bad since it lower the audience, we tend to have done it too much recently). So the issue is that, in the Nested Document concept, we can create children to inexistent (WebHome) page. This introduce some abnormalities: - Administering inexistent page (including page rights, see http://jira.xwiki.org/browse/XWIKI-12629) - Children of inexistent page (see http://jira.xwiki.org/browse/XWIKI-12628 ) Since we agree that having nodes in the tree of pages is fine without having the intermediate document created, we definitely need to better show this concept to the final user. It would be a pain to explain to a user that access rights for page children of an inexistent page is administrable from that inexistent page. It is also very poor when you navigate from the breadcrumb to a inexistent page as a normal user to reach "The requested page could not be found." with no way to navigate further. These inexistent page are not necessarily invisible, there is links to them, and showing that as "error" page looks inappropriate IMO. So there is probably a couple of things we could do to improve this: A) display the list of children in addition to the actual message B) display a "default" and nice (not an error) dashboard on them that allow navigation (with a button for those that can edit, to create the page) C) create them all the time, with the dashboard above by default D) do not propose links to those page in the breadcrumb to users without edit right on them ? E) ... (please add more idea) I am in favor of B) currently, since I do not think we are in an "error" case like A) seems to expose. I am wondering if D) could be useful as well to limit navigation to those page or not for user that will not find them so useful... but it may exists opposite UC. WDYT ? -- Denis Gervalle SOFTEC sa - CEO

3 4

[xwiki-devs] Error installing Social Login Application
by wout.vanduffel 05 Oct '15

05 Oct '15

All, I am trying to install the social login application, but I receive the following error on install Any ideas? Kr W Failed to get fields for class [org.xwiki.social.authentication.internal.DefaultSocialAuthManager] because the class [Lorg/xwiki/crypto/passwd/PasswordCryptoService;] couldn't be found in the ClassLoader. class java.lang.NoClassDefFoundError: Failed to get fields for class [org.xwiki.social.authentication.internal.DefaultSocialAuthManager] because the class [Lorg/xwiki/crypto/passwd/PasswordCryptoService;] couldn't be found in the ClassLoader. at org.xwiki.component.util.ReflectionUtils.getAllFields(ReflectionUtils.java:71) at org.xwiki.component.annotation.ComponentDescriptorFactory.createComponentDescriptor(ComponentDescriptorFactory.java:132) at org.xwiki.component.annotation.ComponentDescriptorFactory.createComponentDescriptors(ComponentDescriptorFactory.java:105) at org.xwiki.component.annotation.ComponentAnnotationLoader.register(ComponentAnnotationLoader.java:168) at org.xwiki.component.annotation.ComponentAnnotationLoader.initialize(ComponentAnnotationLoader.java:136) at org.xwiki.extension.jar.internal.handler.JarExtensionHandler.loadComponents(JarExtensionHandler.java:149) at org.xwiki.extension.jar.internal.handler.JarExtensionHandler.install(JarExtensionHandler.java:103) at org.xwiki.extension.handler.internal.DefaultExtensionHandlerManager.install(DefaultExtensionHandlerManager.java:85) at org.xwiki.extension.job.internal.AbstractExtensionJob.installExtension(AbstractExtensionJob.java:256) at org.xwiki.extension.job.internal.AbstractExtensionJob.applyAction(AbstractExtensionJob.java:204) at org.xwiki.extension.job.internal.AbstractExtensionJob.applyActions(AbstractExtensionJob.java:151) at org.xwiki.extension.job.internal.InstallJob.runInternal(InstallJob.java:150) at org.xwiki.job.internal.AbstractJob.runInContext(AbstractJob.java:209) at org.xwiki.job.internal.AbstractJob.run(AbstractJob.java:192) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722) Finished job of type [install] with identifier [extension/action/org.xwiki.contrib:xwiki-social-login-ui/wiki:xwiki] -- View this message in context: http://xwiki.475771.n2.nabble.com/Error-installing-Social-Login-Application… Sent from the XWiki- Dev mailing list archive at Nabble.com.

3 11

[xwiki-devs] [XWiki Day] BFD#88
by Eduard Moraru 02 Oct '15

02 Oct '15

Hi devs, Today is BFD#88: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingdays We've postponed BFDs during the summer because of the large amounts of work we had on our hands with Nested Spaces / Nested Documents, but since 7.2 was released, it is now a good time to resume. Our current status for the 1 year period is 52 bugs behind. See: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10000#Created-vs-R… Here's the BFD#88 dashboard to follow the progress during the day: http://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=13501 Thanks and enjoy your bug fixing day! -Eduard

2 2

[xwiki-devs] XML file format to import multiple revisions of an existing page via XAR upload
by Ghosh, Amrita 01 Oct '15

01 Oct '15

Hi, I am trying to update an existing page (ad new revisions) by uploading XAR using REST API: curl -k -u Admin:admin -v -X POST -T "Main.testpage.xar" -H "Content-Type: application/stream" https://SERVER/xwiki/rest/wikis/xwiki?history=ADD I could successfully upload a single new revision to an existing page and that new revision is correctly showing up on the page history. But I wanted to upload multiple revisions at a time. For that in the document xml I specified the new revisions inside <versions> </versions> tag (similar to what we see in the XML of exported page with history), but that does not work. Is it possible to add multiple revisions to an existing page with a single XAR upload? Following are my document xml and package.xml inside the XAR file that I was using: Main/testpage.xml: <?xml version='1.0' encoding='UTF-8'?> <xwikidoc version="1.1"> <web>Main</web> <name>testpage</name> <language/> <defaultLanguage>en</defaultLanguage> <translation>0</translation> <creator>XWiki.amritg</creator> <creationDate>1443041962000</creationDate> <versions>head 6.1; access; symbols; locks; strict; 6.1 date 2015.09.23.21.11.51; author XWiki.amritg; state full; branches; next 5.1; 5.1 date 2015.09.23.21.01.49; author XWiki.amritg; state full; branches; next ; desc @@ 6.1 log @@ text @<?xml version="1.0" encoding="UTF-8"?> <xwikidoc> <web>Main</web> <name>testpage</name> <language></language> <defaultLanguage>en</defaultLanguage> <translation>0</translation> <parent></parent> <creator>XWiki.amritg</creator> <author>XWiki.amritg</author> <customClass></customClass> <contentAuthor>XWiki.amritg</contentAuthor> <creationDate>1443041962000</creationDate> <date>1443042713000</date> <contentUpdateDate>1443042713000</contentUpdateDate> <version>6.1</version> <title>Test Page</title> <defaultTemplate></defaultTemplate> <validationScript></validationScript> <comment></comment> <minorEdit>false</minorEdit> <syntaxId>xwiki/2.1</syntaxId> <hidden>false</hidden> <content>Update content for 6th revision</content></xwikidoc> @ 5.1 log @@ text @<?xml version="1.0" encoding="UTF-8"?> <xwikidoc> <web>Main</web> <name>testpage</name> <language></language> <defaultLanguage>en</defaultLanguage> <translation>0</translation> <parent></parent> <creator>XWiki.amritg</creator> <author>XWiki.amritg</author> <customClass></customClass> <contentAuthor>XWiki.amritg</contentAuthor> <creationDate>1443041962000</creationDate> <date>1443042713000</date> <contentUpdateDate>1443042713000</contentUpdateDate> <version>5.1</version> <title>Test Page</title> <defaultTemplate></defaultTemplate> <validationScript></validationScript> <comment></comment> <minorEdit>false</minorEdit> <syntaxId>xwiki/2.1</syntaxId> <hidden>false</hidden> <content>Update content for 5th revision</content></xwikidoc> @ </versions> <author>XWiki.amritg</author> <contentAuthor>XWiki.amritg</contentAuthor> <date>1443042712000</date> <contentUpdateDate>1443042712000</contentUpdateDate> <version>6.1</version> <title>Test Page</title> <comment/> <minorEdit>false</minorEdit> <syntaxId>xwiki/2.1</syntaxId> <hidden>false</hidden> <content>Update content for 6th revision</content> </xwikidoc> Package.xml: <?xml version='1.0' encoding='UTF-8'?> <package> <infos> <name>Main.testpage</name> <description/> <licence/> <author/> <version/> <backupPack>false</backupPack> <preserveVersion>true</preserveVersion> <extensionId/> </infos> <files> <file defaultAction="0" language="">Main.testpage</file> </files> </package> Thanks, Amrita

2 4

[xwiki-devs] [Proposal] Roadmap for XWiki 7.3
by vincent＠massol.net 01 Oct '15

01 Oct '15

Hi devs, Since 7.3 is a stabilization release I propose that we don’t introduce any new features in it and that we focus on stabilizing the Nested Spaces feature which has had its first release in XWiki 7.2. The idea would be to work on Nested Spaces issues as priority and reduce this list to zero: http://jira.xwiki.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=%… Of course we should also fix any important bugs from other features too. In addition a user has asked us to look at * http://jira.xwiki.org/browse/XWIKI-12294: Unable to build on Windows because of failing META-INF/components.txt check Last, in 7.3 and 7.4 we should also work on fixing/polishing features that have been introduced in this cycle (7.x), such as DW/EM work to improve upgrades. Proposed Dates: =============== 7.3M1: 12 October 2015 7.2M2: 26 October 2015 7.3RC1: 2 November 2015 7.3final: 9 Novembre 2015 Note that I’ve put only 1 week between M2 and RC1 and one week between RC1 and final because we need to have a 7.4 that ends before the end of the year. I’ve left one week of buffer between the end of 7.3 final and the start of 7.4M1 in case we have delays. Tentative dates for 7.4: 7.4M1: 30 November 2015 7.4M2: 14 December 2015 7.4RC1: 21 December 2015 7.4final: 28 December 2015 Note that we don’t have much margin with the Christmas holidays. WDYT? Thanks -Vincent

7 11

[xwiki-devs] [Contrib] Request for an xwiki contrib project
by Alexandru Cotiuga 25 Sep '15

25 Sep '15

Hello, I would like to add some improvements to Attachment Selector Macro [1]. Can someone please create a project under xwiki-contrib for this extension ? I think that the name should be “attachment-selector-macro”. Can someone please create the project on Jira ? The key could be “ATTACHSELECTOR”. [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/Attachment+Selector+Ma… Have a good day, Alex.

3 4

[xwiki-devs] [ANN] XWiki 7.2 released
by Guillaume "Louis-Marie" Delhumeau 24 Sep '15

24 Sep '15

The XWiki development team is proud to announce the availability of XWiki 7.2. This release is probably one of the biggest releases we have done in XWiki for years (more than 900 commits)! We have worked hard during all the summer to finally achieve the introduction of a new concept: Nested Pages. This big change affects both the platform and the user interface, and you will discover many differences while using XWiki. For developers, this release also introduces a new Script right and some changes in the REST, Job and Refactoring modules, just to list a few... Finally, it also brings a lot of bugs fixes! You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki72 The following people have contributed code to this release: * Caleb James DeLisle * Clemens Robbenhaar * Denis Gervalle * Ecaterina Moraru (Valica) * Eduard Moraru * Gabriela Smeria * Guillaume Delhumeau * Jean Simard * Marius Dumitru Florea * Sergiu Dumitriu * Thomas Mortagne * Veronika Koltunova * Vincent Massol Thanks for your support -The XWiki dev team

1 0