As far as I can tell, this only occurs when using the Namespace Manager's main form to update Display Orders. It also results in the Display Order update not being committed to memory until the next cache rebuild. This is fixed for the next release.
This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.