Recently Browsing 0 members
No registered users viewing this page.
I have a feeling I'm missing an easy thing here (again...). If I trash a page from API with :
Is there a simple way to restore it if needed ? I can do it in back-end, but I'd like to do it through API with something like
but this doesn't exit
So if you can give me a little help on that, I'd appreciate. Thanks in advance !
By Robin S
Allows non-superusers to trash pages directly from Page List (if they have page-delete permission for that page).
Not much to say really - the module adds a "Trash" option to the extra actions for pages in Page List. It looks and works just like the Trash action available to superusers.
Up to you whether you think non-superusers should be trusted with simpler trashing. For most cases I like the default behaviour where editors have to jump through some more hoops - I want them to think carefully about what they are doing. But if an editor needs to trash several pages then this module might reduce frustration.
@tpr, by now you can probably predict what I'm going to say...
...something to merge into AdminOnSteroids?
I've noticed when I trash pages from a PageTable field, then restore them, they are restored to their original location, however the connection is broken with the PageTable field.
Is this expected behaviour? Is there a way for it to maintain this relationship? Otherwise restoring it doesn't actually restore it to it's previous state.
Note that in this case the parent pages for the PageTable field is not set as the direct parent.
When I delete a page name, e.g, /cart/, using the admin interface it goes into trash and gets the name /trash/2573.1.11_cart/ .
I see that, with the Pages::trashed hook that the previous page name (previousPage) can be accessed.
Where can I more information about what happens when a page is put into trash and what the name means?