Skip to main content

I am trying to re-order my solution articles manually but currently this doesn’t seem to be working.

I can select to order them as “created by” or “A-Z’ etc. But when I select Manually it reverts back to default ordering and I can move the articles but they “snap” back to where they originally were.

For context I have Admin and Agent permissions.

Any help or known issues would be appreciated. I haven’t found any answers searching so far.

I have the same problem. I noticed it yesterday (1 July 2025) for the first time.

This happens on MS Edge and Chrome since the Chromium 138 update. Firefox also has the same problem.


Thanks for the reply.

I have just tried to reorder some articles on Safari and that seems to be working. It would be interesting to know what is causing it to not work in Chrome. I’ll use Safari as a workaround for now.


I noticed the same problem today, and (as you say) it occurs on Edge, Chrome and FireFox.

 

Luckily there is a workaround - use Opera :-)


Same issue here. Working with Chrome
Version 138.0.7204.102 (Official Build) (arm64)


If you're unable to manually reorder your solution articles and they keep snapping back to their original positions, it's likely a glitch with the platform or a browser-related issue. Try clearing your browser cache, switching to another browser, or ensuring you're in the published (not draft) view of your help center. Even with Admin permissions, this can happen due to small syncing bugs. If the problem persists, it’s best to contact support, as it could be a known issue needing backend resolution.


 

That's frustrating! It definitely sounds like a bug in the manual ordering functionality. I've run into similar issues with other platforms where drag-and-drop just doesn't behave. Have you tried clearing your browser cache and cookies, or maybe even testing it in a different browser? Sometimes that can resolve unexpected glitches. It's a long shot, but quicker than driving around in circles like someone in an Eggy Car! Hopefully, someone else has encountered this and has a more concrete solution.


Reply