Module: AdminSaveActions

[Martijn Geerts]

Makes sense to me Nik.

When a parent is filled with imported unpublished pages, it's likely that you save/publish/delete it and go to the next unpublished/hidden. 

[kongondo]

Nik,

Thanks for the update. Works nicely but there is one issue..A cookie is not being set/or is being ignored for "remember this setting" when it comes to "Edit next sibling page". Is this the intended behaviour? (maybe to deal with cases where there is no next sibling?). At the moment, it is rather tedious to keep on selecting after save -> edit next sibling on each page edit

[nik]

Good catch Kongondo, thanks! I didn't test that quite enough obviously.

I fixed this and also added a little bit intelligence to the option:

• If currently edited page is hidden but published all published pages are acknowledged (visible or hidden)
• If currently edited page is unpublished all pages are acknowledged
• Otherwise (visible, published page) only visible and published pages are acknowledged

That may lead to some confusion I'm sure, but it felt quite natural to me. Feel free to disagree .

[kongondo]

Nik, thanks for the update!

I'll test and see if I disagree (e.g. make the choices configurable? or maybe that's overcomplicating things...)

[valan]

How to make "After save" fieldset visible only for superusers? Being a superuser I like to work with "After save", but other roles have destructive access to system through it... Thanks!

[dotnetic]

This module still works with PW 2.7.1 and it´s a great one. I think it should be in core.