On West Hampton you can't drag/drop the order of the document categories and have it save the new order. Locally on my (CM) machine with the West Hampton database downloaded for testing this does work without issues.
There are no errors thrown when you release the drag/drop action in the AJAX query that is made to do the saving. Query Monitor on the local site running PHP 8.2 does say there was an AJAX error though, it just doesn't show up in the console in Firefox or Chrome when I look.
When we run PHP 8.0.22 there is no AJAX error reported in Query Monitor and still none in the browser console.
I also double checked on another site and the drag/drop function does not work their either.
Redis Caching Issue
If you turn off Redis then the drag/drop functions work as expected. If you drag/drop and then flush the Redis cache it also works as expected.
[x] run a flush cache routine when we drag/drop
but maybe that's going to be too often so the user needs to make sure they hit the save button and then we'd flush the Redis cache
we'd also need to make sure that we detect a change and then stop the user from navigating away until they've hit the button to save which would force the cache flush
Builds
Logging Code removed
Source
On West Hampton you can't drag/drop the order of the document categories and have it save the new order. Locally on my (CM) machine with the West Hampton database downloaded for testing this does work without issues.
There are no errors thrown when you release the drag/drop action in the AJAX query that is made to do the saving. Query Monitor on the local site running PHP 8.2 does say there was an AJAX error though, it just doesn't show up in the console in Firefox or Chrome when I look.
When we run PHP 8.0.22 there is no AJAX error reported in Query Monitor and still none in the browser console.
I also double checked on another site and the drag/drop function does not work their either.
Redis Caching Issue If you turn off Redis then the drag/drop functions work as expected. If you drag/drop and then flush the Redis cache it also works as expected.
save
button and then we'd flush the Redis cachesave
which would force the cache flushRedis FAQ
Describe the bug
A clear and concise description of what the bug is.
To reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
QA
Notes:
Links:
*