User renamed space - now inaccessible

classic Classic list List threaded Threaded
3 messages Options
D R
Reply | Threaded
Open this post in threaded view
|

User renamed space - now inaccessible

D R
Hi everybody,

I have a huge issue here with our XWiki 7.4.4 instance running on CentOS 7
/ Tomcat 8.0.33.

We had a document space "Customer Docs" in a sub wiki "Customers" with
several nested docs (customers with more nested docs).

A user managed to break the whole document space by renaming it to "@Spain
Wiki". When accessing the page now the browser throws a "This page does not
work, <SERVERNAME> has redirected too often" (translated from German).

I see the pages with the old names in Page Index under deleted documents
but when I click the actions icon (which says it can't be restored because
it already has been recreated?!) I get the same browser error.

Is there any way I can restore the old document space?

(Restoring a database backup will not work because too many other things
have been changed in other parts of the wiki, the renaming was done on
April 20th but discovered today)

Regs,
Dennis
D R
Reply | Threaded
Open this post in threaded view
|

Re: User renamed space - now inaccessible

D R
Hi again,

does nobody have an idea?

The other guys in the wiki team lose faith because a simple rename can have
such a huge impact on the contents and the restore feature does not work.

Regs, Dennis

2017-04-28 11:31 GMT+02:00 D R <[hidden email]>:

> Hi everybody,
>
> I have a huge issue here with our XWiki 7.4.4 instance running on CentOS 7
> / Tomcat 8.0.33.
>
> We had a document space "Customer Docs" in a sub wiki "Customers" with
> several nested docs (customers with more nested docs).
>
> A user managed to break the whole document space by renaming it to "@Spain
> Wiki". When accessing the page now the browser throws a "This page does not
> work, <SERVERNAME> has redirected too often" (translated from German).
>
> I see the pages with the old names in Page Index under deleted documents
> but when I click the actions icon (which says it can't be restored because
> it already has been recreated?!) I get the same browser error.
>
> Is there any way I can restore the old document space?
>
> (Restoring a database backup will not work because too many other things
> have been changed in other parts of the wiki, the renaming was done on
> April 20th but discovered today)
>
> Regs,
> Dennis
>
D R
Reply | Threaded
Open this post in threaded view
|

Re: User renamed space - now inaccessible

D R
Hi again,

meanwhile I found out that the restore process doesn't ignore the redirect
object on the renamed pages.

So am I right that I need to do the following:
1. Delete all pages that have the redirect object
2. Use recycle bin to restore the complete document space

If I'm wrong please let me know, otherwise please tell me how to achieve
the above without going throuth each document. Via database?

Thanks and regards,
Dennis

2017-05-03 9:53 GMT+02:00 D R <[hidden email]>:

> Hi again,
>
> does nobody have an idea?
>
> The other guys in the wiki team lose faith because a simple rename can
> have such a huge impact on the contents and the restore feature does not
> work.
>
> Regs, Dennis
>
> 2017-04-28 11:31 GMT+02:00 D R <[hidden email]>:
>
>> Hi everybody,
>>
>> I have a huge issue here with our XWiki 7.4.4 instance running on CentOS
>> 7 / Tomcat 8.0.33.
>>
>> We had a document space "Customer Docs" in a sub wiki "Customers" with
>> several nested docs (customers with more nested docs).
>>
>> A user managed to break the whole document space by renaming it to
>> "@Spain Wiki". When accessing the page now the browser throws a "This page
>> does not work, <SERVERNAME> has redirected too often" (translated from
>> German).
>>
>> I see the pages with the old names in Page Index under deleted documents
>> but when I click the actions icon (which says it can't be restored because
>> it already has been recreated?!) I get the same browser error.
>>
>> Is there any way I can restore the old document space?
>>
>> (Restoring a database backup will not work because too many other things
>> have been changed in other parts of the wiki, the renaming was done on
>> April 20th but discovered today)
>>
>> Regs,
>> Dennis
>>
>
>