-
-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reordering Static pages does not save config #870
Comments
Hello, Check the site and seems the subpage already in order (see the menu).
You can use the |
Sorry, I should have been clearer. |
By the way, I should say how impressed I am by this extremely useful and compact CMS. |
No problems.
Let me try to create similar sub-pages structure to test it |
Bug confirmed. Thanks. To fix this while waiting for a newer version, you can replace |
Many thanks for the quick turnaround! |
Describe the bug
I have a Static page with approximately 150 subpages - each basically a date in a year e.g. 'Friday, 19th April 1942'
Obviously I wish to order them by date ascending.
When I attempt to do so by dragging sub pages into the correct order and using [save config] I see an alert telling me 'Page order saved successfully!' and I dismiss the alert.
I then discover that the page order is not saved at all.
I have logged out and back in, cleared cache and tried numerous times to no avail.
To Reproduce
Using a large list of sub pages ≥ 150,
Reorder one or more by manual drag and drop
Save reo-order
Expected behavior
Re-ordered list is saved
Screenshots/Errors
If applicable, add screenshots and/or error messages to help explain your problem. You may need to check your webserver's error logs.
HTMLy Version
HTMLy v3.0.3
Server Info (please complete the following information):
Operating System | linux
Apache Version | 2.4.62
Kernel Version | 5.14.0-503.14.1.el9_5.x86_64
PHP Version | 7.4
Link to installation (optional, but usually helpful)
https://sheriffof0.com/fred&doreen/
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: