Robin S Posted December 15, 2018 Posted December 15, 2018 Pages At Bottom Keeps selected pages at the bottom of their siblings. A "bottom page" will stay at the bottom even if it is drag-sorted to a different location or another page is drag-sorted below it (after Page List is refreshed the bottom page will still be at the bottom). Newly added sibling pages will not appear below a bottom page. The module also prevents the API methods $pages->sort() and $pages->insertAfter() from affecting the position of bottom pages. Note: the module only works when the sort setting for children on the parent page/template is "Manual drag-n-drop". Why? Because you want some pages to always be at the bottom of their siblings for one reason or another. And someone requested it. ? Usage Install the Pages At Bottom module. Select one or more pages to keep at the bottom of their siblings. If you select more than one bottom page per parent then their sort order in the page list will be the same as the sort order in the module config. https://github.com/Toutouwai/PagesAtBottomhttps://modules.processwire.com/modules/pages-at-bottom/ 14 1
Robin S Posted December 15, 2018 Author Posted December 15, 2018 v0.1.1 released: if you select more than one bottom page per parent then their sort order in the page list will be the same as the sort order in the module config. 1
cb2004 Posted January 14, 2020 Posted January 14, 2020 Never commented on how this makes every default install I have, love it. 1
bernhard Posted February 4, 2020 Posted February 4, 2020 Just installed it. Really simple. Really useful. Thx a lot! ? 1
cb2004 Posted November 28, 2022 Posted November 28, 2022 @Robin S this still makes an appearance on every install I have. Is there any way to extend the module so that it adds options for pages at top? 1
Robin S Posted November 30, 2022 Author Posted November 30, 2022 On 11/29/2022 at 3:20 AM, cb2004 said: Is there any way to extend the module so that it adds options for pages at top? The settings are made on the module config page and that means they are only accessible to superusers. When putting pages at the bottom this is usually for "admin helper" purposes that a superuser would set up, but I would think that forcing pages to the top is more a content management function that needs to be manageable by non-superusers. It might be something that is better handled with a hook or just a Page Reference field. Can you describe the use case where you want pages kept at the top? Then I can consider it or suggest alternative ways of achieving it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now