Problems deleting PageTable pages outside of the field #815

Open
mjmurphy opened this Issue Dec 6, 2014 · 3 comments

Projects

None yet

3 participants

@mjmurphy
mjmurphy commented Dec 6, 2014

I am having problems deleting pages used by a PageTable field, when not using the actual PageTable field

Processwire version : 2.5.8 dev
Modifications : I have installed Language support for Fields and Page Names.

I am storing the PageTable pages in a hidden folder called "Videos".
If I delete one of these pages outside of where the PageTable is being used (i.e. from the "Videos" folder) the following happens :

If I am logged in as root admin, the deleted PageTable page is greyed out, I can open the page and edit, but there is a message that :

This page is in the Trash

And there is no way from this dialog to restore the page (of course you can go manually to the trash and restore it).

If I am logged in as an editor (with reduced permissions but including "page-delete") - the deleted PageTable page is greyed out, but when I try to edit the page, there is an error message.

Module ProcessPageEdit failed init - You don't have access to edit No page found

And it is not possible to edit the page.

The reason I would like to do this is because I want to allow the editors different ways of managing the content outside of the PageTable field context. For example having helper links on the front end that allows editors to easily edit the PageTable pages or viewing all the PageTable pages with Lister Pro (almost like a media manager).

@ryancramerdesign
Owner

It sounds like the issue here is that a page got trashed outside of PageTable, so PageTable still has a reference to it. I suppose this could be resolved just by having PageTable ignore its own page references if they happen to point to a page in the trash. I wanted to make sure I understood correctly, does that sound right?

@mjmurphy
mjmurphy commented Dec 7, 2014

Yes that sounds correct. Because as soon as you restore the trashed page to its original location, the problem is resolved.

@patrikengborg

Would also appreciate a fix for this, just had the same problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment