Re: [xwiki-users] Adding Macro as Buttons in CKEditor

2017-03-02 Thread Marius Dumitru Florea
See http://jira.xwiki.org/browse/CKEDITOR-148 .

On Wed, Mar 1, 2017 at 11:45 AM, Marius Dumitru Florea <
mariusdumitru.flo...@xwiki.com> wrote:

> On Mon, Feb 27, 2017 at 12:40 PM, Mahomed Hussein  > wrote:
>
>> Hi
>>
>> With the editor in XWiki < v9.0.0 (GWT Editor), I could add different
>> buttons and macros onto the toolbar by modifying the configuration and
>> adding “macro:macroName” as a toolbar “feature”.
>>
>>
>
>> Has anyone got a simple step by step instructions for adding the same
>> thing in CKEditor? I’ve tried looking at the documentation, but it doesn’t
>> immediately or easily relate to the macros/add-ins (e.g. the lightbox
>> macro/plugin is one we use a lot).
>>
>
> The CKEditor integration doesn't support this ATM, unfortunately. Would be
> great if you could make a feature request on http://jira.xwiki.org/browse/
> CKEDITOR . Someone else also asked for this recently so I could try to
> make some time to implement it but I can't guarantee. If you can't wait and
> you know JavaScript you could try to implement this yourself like this:
>
> * read the CKEditor documentation for writing a plugin
> http://docs.ckeditor.com/#!/guide/plugin_sdk_sample . You can write the
> plugin in a JSX similar to https://github.com/xwiki-
> contrib/application-ckeditor/blob/application-ckeditor-1.0/
> ui/src/main/resources/CKEditor/WikiSourcePlugin.xml and load it like
> https://github.com/xwiki-contrib/application-ckeditor/
> blob/application-ckeditor-1.0/ui/src/main/resources/
> CKEditor/EditSheet.xml#L154
> * the "insertTimestamp" command defined in the example plugin from the
> CKEditor documentation would open the macro editor and then insert macro
> when the dialog is closed. Something like this is done in
> https://github.com/xwiki-contrib/application-ckeditor/
> blob/master/plugins/src/main/resources/xwiki-macro/plugin.js#L160 .
>
> But it's not very easy and I would like to implement something generic.
>
> Thanks,
> Marius
>
>
>>
>> Thanks in advance for any help.
>>
>>
>> Kind regards,
>>
>>
>> Mahomed Hussein
>> Custodian Data Centre
>> Email: maho...@custodiandc.com
>> http://www.CustodianDC.com
>>
>
>


Re: [xwiki-users] [myxwiki] new wiki request

2017-03-02 Thread Thomas Mortagne
You can access your new wiki on http://secitup.myxwiki.org. Enjoy !

Note: looks like you registered 4 users with display name "Joachim
Vanthienen" so I used the one with id "JoachimVanthienen" as owner of
the wiki.

On Mon, Feb 27, 2017 at 10:26 AM, joachim  wrote:
> Description: First of all i would like to use XWiki as my personal knowledge 
> base, and using it to keep track of my projects. And if possible share some 
> blog posts and some projects with the world. Most of these topics are 
> concerning information security and forensics.
>
> Owner name: Joachim Vanthienen
>
> Wiki name: SecITup
>



-- 
Thomas Mortagne


Re: [xwiki-users] Rest API to create pages (and pages within pages)

2017-03-02 Thread Marius Dumitru Florea
On Thu, Mar 2, 2017 at 10:38 AM, Juan Huerta  wrote:

> Hi Marius,
>
> Thanks a lot for your help.
>
> Actually, after browsing the forum, I found someone had a similar problem
> (or so I thought). And I thought that my solution was along the lines of
> setting the parent and parentId of the pages (while calling the API and as
> data passed in the call) .
>

The parent field has been deprecated
http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization/NestedPagesMigration/#HParent2FChildrelationship
.


>
> http://xwiki.475771.n2.nabble.com/when-creating-a-page-via-
> REST-it-doesn-t-
> appear-in-children-via-REST-td7601706.html
> 
>
> Thanks again for your help and I'll check on it.
>
> Cheers,
>
> Juan
>
> 2017-03-02 9:34 GMT+01:00 Marius Dumitru Florea <
> mariusdumitru.flo...@xwiki.com>:
>
> > Hi Juan,
> >
> > You got it almost right, but you need to read
> > http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization/ ,
> > especially the part that explains the difference between terminal and
> > non-terminal pages.
> >
> > On Wed, Mar 1, 2017 at 11:13 PM, Juan Huerta 
> > wrote:
> >
> > > Hi,
> > >
> > > I'm quite new in XWiki and trying to use the RestAPI to create pages,
> and
> > > pages inside pages (which I think is called spaces).  I have the
> feeling
> > > that 'spaces' is a legacy term, and that in the current XWiki
> (Enterprise
> > > 9.1), an space is just a page that contains other pages. Kindly correct
> > me
> > > if I'm wrong, but I have not find anywhere how to create an space.
> > >
> > > Below the 2 URLs I'm using to create the pages. In both cases, when I
> use
> > > PUT to call the 2 urls, I pass as data a content and a title. I have no
> > > problem with the title and the content, both are being created
> correctly.
> > > My end goal is to create pages, and pages withing pages.
> > >
> > >
> >
> > > "http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> > > 2020/pages/madrid
> > >
> >
> > This creates a terminal page "madrid".
> >
> >
> > > "
> > > "
> > >
> > >  > 2020/spaces/madrid/pages/cibeles>
> >
> >
> >
> > > http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> > > 2020/spaces/madrid/pages/cibeles
> > >
> >
> > This creates a terminal page "cibeles" inside a non-terminal page
> "madrid".
> >
> >
> > > "
> > >
> > >
> > > In both cases, I'm using PUT and I'm able to create pages successfully,
> > > however, not as I want:
> > >
> > > - "
> > > http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> > 2020/pages/madrid
> > > "
> > > This one creates a page called "madrid" (with the content I pass)
> > >
> > > - "
> > > http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> > > 2020/spaces/madrid/pages/cibeles
> > > "
> > > I would expect this one to create a page named "cibeles" inside the
> > > previous "madrid" page.
> > > Instead, it creates a new "madrid" page (without any text in the
> content,
> > > which is fine as I dont pass anything), and inside this page, the
> > "cibeles"
> > > page (with the content I expect)
> > >
> > >
> >
> > > So, I end up having TWO pages named "madrid"
> > >
> >
> > Exactly. One is terminal and the other one is non-terminal. The actual
> > references (identifiers) are:
> >
> > xwiki:2017-2020.madrid <--- this is the terminal page (can't have child
> > pages)
> > xwiki:2017-2020.madrid.WebHome <--- this is the non-terminal page (can
> have
> > child page)
> >
> > Hope this helps,
> > Marius
> >
> >
> > >
> > >  One points to "http://localhost:8080/xwiki/bin/view/2017-2020/madrid/
> "
> > > (and have inside a page named cibeles) . This "madrid" page displays
> this
> > > text: "The requested page could not be found.", although inthe
> hierarchy
> > > tree I see it has a page inside.
> > >
> > >  The other (without a nested page), points to: "
> > > http://localhost:8080/xwiki/bin/view/2017-2020/madrid; and has a
> proper
> > > content (which I passed in the PUT request)
> > >
> > >  (notice the / at the end of the URL, "madrid" vs "madrid/" )
> > >
> > >  How to indicate that the page should be created in an existing page
> > > without the need to create this new parent page? Or even if I have to
> > > create first the parent page, how to tell that the child page should be
> > > inside that existing parent page?
> > >
> > >  Thanks for your help,
> > >
> > >  Juan
> > >
> >
>


Re: [xwiki-users] Rollback Failure

2017-03-02 Thread Marius Dumitru Florea
The rollback operation fails inside the FileSystem Attachment Store, at
this line
https://github.com/xwiki/xwiki-platform/blob/master/xwiki-platform-core/xwiki-platform-store/xwiki-platform-store-filesystem-oldcore/src/main/java/org/xwiki/store/legacy/store/internal/FilesystemAttachmentRecycleBinStore.java#L472
. The problem is that

absolutePath.indexOf("/~this/")

return -1, which suggests that some paths within the FileSystem Attachment
Store folder are not right (as expected). I would check the paths related
to your target document.

Hope this helps,
Marius

On Wed, Mar 1, 2017 at 7:08 PM, Keith Davis 
wrote:

> We have a page that fails when we attempt to rollback, other pages seem to
> work fine:
>
> Detailed information:
>
> Error number 0 in 11: Uncaught exception
> com.xpn.xwiki.XWikiException: Error number 0 in 11: Uncaught exception
> at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:474)
> at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:210)
> at org.apache.struts.action.RequestProcessor.processActionPerform(
> RequestProcessor.java:425)
> at org.apache.struts.action.RequestProcessor.process(
> RequestProcessor.java:228)
> at org.apache.struts.action.ActionServlet.process(
> ActionServlet.java:1913)
> at org.apache.struts.action.ActionServlet.doGet(
> ActionServlet.java:449)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:622)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:230)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:112)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:192)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.xwiki.wysiwyg.server.filter.ConversionFilter.
> doFilter(ConversionFilter.java:127)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:192)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.apache.tomcat.websocket.server.WsFilter.doFilter(
> WsFilter.java:52)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:192)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.xwiki.container.servlet.filters.internal.
> SetHTTPHeaderFilter.doFilter(SetHTTPHeaderFilter.java:63)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:192)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.xwiki.container.servlet.filters.internal.
> SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:192)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.xwiki.container.servlet.filters.internal.
> SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:111)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:192)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.xwiki.resource.servlet.RoutingFilter.doFilter(
> RoutingFilter.java:134)
> at org.apache.catalina.core.ApplicationFilterChain.
> internalDoFilter(ApplicationFilterChain.java:192)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:165)
> at org.apache.catalina.core.StandardWrapperValve.invoke(
> StandardWrapperValve.java:198)
> at org.apache.catalina.core.StandardContextValve.invoke(
> StandardContextValve.java:96)
> at org.apache.catalina.authenticator.AuthenticatorBase.invoke(
> AuthenticatorBase.java:474)
> at org.apache.catalina.core.StandardHostValve.invoke(
> StandardHostValve.java:140)
> at org.apache.catalina.valves.ErrorReportValve.invoke(
> ErrorReportValve.java:79)
> at org.apache.catalina.valves.AbstractAccessLogValve.invoke(
> AbstractAccessLogValve.java:624)
> at org.apache.catalina.core.StandardEngineValve.invoke(
> StandardEngineValve.java:87)
> at org.apache.catalina.connector.CoyoteAdapter.service(
> CoyoteAdapter.java:349)
> at org.apache.coyote.http11.Http11Processor.service(
> Http11Processor.java:783)
> at org.apache.coyote.AbstractProcessorLight.process(
> 

Re: [xwiki-users] Nice display title

2017-03-02 Thread Vincent Massol
Hi Gerritjan,

> On 2 Mar 2017, at 09:35, Thomas Mortagne  wrote:
> 
> See xwiki.title.compatibility property in xwiki.cfg.
> 
> Extracting the title from the content was disabled by default in 7.0.

Note that you need to read the release notes before upgrading (all the release 
notes from the version you have till the version you’re upgrading to. Yes that 
could be a lot! :)) since they contain useful information such as this one.

For example for 7.0, we had:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki70#HBackwardCompatibilityandMigrationNotes

Thanks
-Vincent

> On Tue, Feb 28, 2017 at 10:50 AM, Gerritjan Koekkoek
>  wrote:
>> It has always been normal that if a page did not have the attribute 'title' 
>> (it was left empty)
>> 
>> it would use a smart way to see if in the text there was a header of level 
>> 1,2 or 3 at the top. And then display that as the title...
>> 
>> 
>> Now I've migrated pages to a XWiki 8.4.4 and this does not work any more?
>> 
>> 
>> What can cause this change in behavior ? Is it a known issue when migrating 
>> pages from 6.4 to ???
>> 
>> Is the nested pages a possible cause?
>> 
>> 
>> I tried to put the h2 title in the title attribute as well, but still the 
>> pagename is shown as title?
>> 
>> 
>> Gerritjan Koekkoek
>> Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
>> Visit our website
>> Facebook
>> email
>> 
>> 
>> 
> 
> 
> 
> -- 
> Thomas Mortagne



Re: [xwiki-users] Rest API to create pages (and pages within pages)

2017-03-02 Thread Juan Huerta
Hi Marius,

Thanks a lot for your help.

Actually, after browsing the forum, I found someone had a similar problem
(or so I thought). And I thought that my solution was along the lines of
setting the parent and parentId of the pages (while calling the API and as
data passed in the call) .

http://xwiki.475771.n2.nabble.com/when-creating-a-page-via-REST-it-doesn-t-
appear-in-children-via-REST-td7601706.html

Thanks again for your help and I'll check on it.

Cheers,

Juan

2017-03-02 9:34 GMT+01:00 Marius Dumitru Florea <
mariusdumitru.flo...@xwiki.com>:

> Hi Juan,
>
> You got it almost right, but you need to read
> http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization/ ,
> especially the part that explains the difference between terminal and
> non-terminal pages.
>
> On Wed, Mar 1, 2017 at 11:13 PM, Juan Huerta 
> wrote:
>
> > Hi,
> >
> > I'm quite new in XWiki and trying to use the RestAPI to create pages, and
> > pages inside pages (which I think is called spaces).  I have the feeling
> > that 'spaces' is a legacy term, and that in the current XWiki (Enterprise
> > 9.1), an space is just a page that contains other pages. Kindly correct
> me
> > if I'm wrong, but I have not find anywhere how to create an space.
> >
> > Below the 2 URLs I'm using to create the pages. In both cases, when I use
> > PUT to call the 2 urls, I pass as data a content and a title. I have no
> > problem with the title and the content, both are being created correctly.
> > My end goal is to create pages, and pages withing pages.
> >
> >
>
> > "http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> > 2020/pages/madrid
> >
>
> This creates a terminal page "madrid".
>
>
> > "
> > "
> >
> >  2020/spaces/madrid/pages/cibeles>
>
>
>
> > http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> > 2020/spaces/madrid/pages/cibeles
> >
>
> This creates a terminal page "cibeles" inside a non-terminal page "madrid".
>
>
> > "
> >
> >
> > In both cases, I'm using PUT and I'm able to create pages successfully,
> > however, not as I want:
> >
> > - "
> > http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> 2020/pages/madrid
> > "
> > This one creates a page called "madrid" (with the content I pass)
> >
> > - "
> > http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> > 2020/spaces/madrid/pages/cibeles
> > "
> > I would expect this one to create a page named "cibeles" inside the
> > previous "madrid" page.
> > Instead, it creates a new "madrid" page (without any text in the content,
> > which is fine as I dont pass anything), and inside this page, the
> "cibeles"
> > page (with the content I expect)
> >
> >
>
> > So, I end up having TWO pages named "madrid"
> >
>
> Exactly. One is terminal and the other one is non-terminal. The actual
> references (identifiers) are:
>
> xwiki:2017-2020.madrid <--- this is the terminal page (can't have child
> pages)
> xwiki:2017-2020.madrid.WebHome <--- this is the non-terminal page (can have
> child page)
>
> Hope this helps,
> Marius
>
>
> >
> >  One points to "http://localhost:8080/xwiki/bin/view/2017-2020/madrid/;
> > (and have inside a page named cibeles) . This "madrid" page displays this
> > text: "The requested page could not be found.", although inthe hierarchy
> > tree I see it has a page inside.
> >
> >  The other (without a nested page), points to: "
> > http://localhost:8080/xwiki/bin/view/2017-2020/madrid; and has a proper
> > content (which I passed in the PUT request)
> >
> >  (notice the / at the end of the URL, "madrid" vs "madrid/" )
> >
> >  How to indicate that the page should be created in an existing page
> > without the need to create this new parent page? Or even if I have to
> > create first the parent page, how to tell that the child page should be
> > inside that existing parent page?
> >
> >  Thanks for your help,
> >
> >  Juan
> >
>


Re: [xwiki-users] Nice display title

2017-03-02 Thread Thomas Mortagne
See xwiki.title.compatibility property in xwiki.cfg.

Extracting the title from the content was disabled by default in 7.0.

On Tue, Feb 28, 2017 at 10:50 AM, Gerritjan Koekkoek
 wrote:
> It has always been normal that if a page did not have the attribute 'title' 
> (it was left empty)
>
> it would use a smart way to see if in the text there was a header of level 
> 1,2 or 3 at the top. And then display that as the title...
>
>
> Now I've migrated pages to a XWiki 8.4.4 and this does not work any more?
>
>
> What can cause this change in behavior ? Is it a known issue when migrating 
> pages from 6.4 to ???
>
> Is the nested pages a possible cause?
>
>
> I tried to put the h2 title in the title attribute as well, but still the 
> pagename is shown as title?
>
>
> Gerritjan Koekkoek
> Vader van Rai Koekkoek (cdls) en voorzitter vereniging CdLS
> Visit our website
> Facebook
> email
>
>
>



-- 
Thomas Mortagne


Re: [xwiki-users] Rest API to create pages (and pages within pages)

2017-03-02 Thread Marius Dumitru Florea
Hi Juan,

You got it almost right, but you need to read
http://platform.xwiki.org/xwiki/bin/view/Features/ContentOrganization/ ,
especially the part that explains the difference between terminal and
non-terminal pages.

On Wed, Mar 1, 2017 at 11:13 PM, Juan Huerta  wrote:

> Hi,
>
> I'm quite new in XWiki and trying to use the RestAPI to create pages, and
> pages inside pages (which I think is called spaces).  I have the feeling
> that 'spaces' is a legacy term, and that in the current XWiki (Enterprise
> 9.1), an space is just a page that contains other pages. Kindly correct me
> if I'm wrong, but I have not find anywhere how to create an space.
>
> Below the 2 URLs I'm using to create the pages. In both cases, when I use
> PUT to call the 2 urls, I pass as data a content and a title. I have no
> problem with the title and the content, both are being created correctly.
> My end goal is to create pages, and pages withing pages.
>
>

> "http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> 2020/pages/madrid
>

This creates a terminal page "madrid".


> "
> "
>
> 



> http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> 2020/spaces/madrid/pages/cibeles
>

This creates a terminal page "cibeles" inside a non-terminal page "madrid".


> "
>
>
> In both cases, I'm using PUT and I'm able to create pages successfully,
> however, not as I want:
>
> - "
> http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-2020/pages/madrid
> "
> This one creates a page called "madrid" (with the content I pass)
>
> - "
> http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/2017-
> 2020/spaces/madrid/pages/cibeles
> "
> I would expect this one to create a page named "cibeles" inside the
> previous "madrid" page.
> Instead, it creates a new "madrid" page (without any text in the content,
> which is fine as I dont pass anything), and inside this page, the "cibeles"
> page (with the content I expect)
>
>

> So, I end up having TWO pages named "madrid"
>

Exactly. One is terminal and the other one is non-terminal. The actual
references (identifiers) are:

xwiki:2017-2020.madrid <--- this is the terminal page (can't have child
pages)
xwiki:2017-2020.madrid.WebHome <--- this is the non-terminal page (can have
child page)

Hope this helps,
Marius


>
>  One points to "http://localhost:8080/xwiki/bin/view/2017-2020/madrid/;
> (and have inside a page named cibeles) . This "madrid" page displays this
> text: "The requested page could not be found.", although inthe hierarchy
> tree I see it has a page inside.
>
>  The other (without a nested page), points to: "
> http://localhost:8080/xwiki/bin/view/2017-2020/madrid; and has a proper
> content (which I passed in the PUT request)
>
>  (notice the / at the end of the URL, "madrid" vs "madrid/" )
>
>  How to indicate that the page should be created in an existing page
> without the need to create this new parent page? Or even if I have to
> create first the parent page, how to tell that the child page should be
> inside that existing parent page?
>
>  Thanks for your help,
>
>  Juan
>


Re: [xwiki-users] Batch move of pages

2017-03-02 Thread Marius Dumitru Florea
On Wed, Mar 1, 2017 at 6:20 PM, Sebastian Luna Valero <
sebastian.luna.val...@gmail.com> wrote:

> Many thanks, Marius.
>
> Apart from that option, would it be possible to drag and drop wiki pages
> when using the "tree view" in the "Page index"?
> (xwiki/bin/view/Main/AllDocs?view=tree)
>

Unfortunately this is not yet implemented, see http://jira.xwiki.org/browse/
XWIKI-11046 . The tree supports drag & drop (see the "readOnly" parameter
http://extensions.xwiki.org/xwiki/bin/view/Extension/Document+Tree+Macro#HParameters
) and the backend API to move pages is available (the refactoring module I
linked in the previous mail). What's missing is the binding between them.
See https://github.com/xwiki/xwiki-platform/blob/master/
xwiki-platform-core/xwiki-platform-index/xwiki-platform-
index-tree/xwiki-platform-index-tree-macro/src/main/resources/XWiki/
DocumentTreeMacros.xml#L113 . ATM all actions return "The specified action
is not supported.". You can try to modify the XWiki.DocumentTreeMacros page
at the indicated line to test for the move action and call the refactoring
script service.

Hope this helps,
Marius


>
> Best regards,
> Sebastian
>
>
> 2017-03-01 14:50 GMT+00:00 Marius Dumitru Florea <
> mariusdumitru.flo...@xwiki.com>:
>
> > Hi Sebastian,
> >
> > Take a look at the Refactoring Module
> > http://extensions.xwiki.org/xwiki/bin/view/Extension/Refactoring+Module
> .
> > It provides some scripting APIs to move/rename pages. The full list of
> > methods is available at
> > https://github.com/xwiki/xwiki-platform/blob/master/
> > xwiki-platform-core/xwiki-platform-refactoring/xwiki-
> > platform-refactoring-api/src/main/java/org/xwiki/refactoring/script/
> > RefactoringScriptService.java
> > . Move request accepts a list as input (i.e. you can move multiple pages
> to
> > the same target location).
> >
> > Hope this helps,
> > Marius
> >
> > On Wed, Mar 1, 2017 at 4:22 PM, Sebastian Luna Valero <
> > sebastian.luna.val...@gmail.com> wrote:
> >
> > > Hi All,
> > >
> > > We are rearranging our xwiki and we have many pages to move to
> different
> > > locations. So far, the only solution seems to be doing so one page at a
> > > time, which is tedious having into account that more than 200 pages
> need
> > to
> > > be moved.
> > >
> > > I was wondering whether this could be streamlined somehow. I could not
> > find
> > > help in the mailing list archives and I think the only extension
> > available
> > > is:
> > >
> > > http://extensions.xwiki.org/xwiki/bin/view/Extension/File+
> > > Manager+Application
> > >
> > > but this seems to work with non-wiki files.
> > >
> > > Any feedback is appreciated.
> > >
> > > Best regards,
> > > Sebastian
> > >
> >
>