Moving content blocks within area doesn't work

Permalink 1 user found helpful
I have seen similar reports on this forum, but none pointed me in the right direction. In a pretty standard concrete5 setup (5.4.2, was the same problem in 5.4.1), moving blocks within the page seems to work right after clicking "Save positioning", which alerts and displays the blocks in the correct order. When saving, the version dialog shows the current, not the next version number, and after saving the old order is restored. Changing a block's content and then saving works correctly.

Any pointers?

Thank you,
Bernd

 
likesalmon replied on at Permalink Reply
I can confirm this, but my version number is incremented correctly when I approve the version. I've been working on this site for a while but just noticed it today. It's locally hosted.

Move consistently works in some areas but consistently doesn't work in others. I had the problem in 5.4.2.1 and experienced no change upon upgrade to 5.4.2.2. Adding, editing and deleting blocks works fine. I show no php or javascript errors. I tried removing my custom javascript to no avail. I'm running the core_commerce add-on but otherwise I'm just using core packages.

Thanks and heartfelt appreciation to the C5 community,

Likesalmon
beeman89045 replied on at Permalink Reply
Having this exact problem (and thought I was going crazy). One other minor piece of information is that one my block is a "global block" (hosted in the Scrapbook) and the other is a block specific to the page. I have attempted to move the Global Block "under" the page-level block. Behavior is same as described. Works perfect until publish after which it reverts back to pre-edit positioning.
bmatzner replied on at Permalink Reply
I finally found out what was the problem:
in this site, I added a redirect using header() to the index.php file to a specific page if the home page is loaded. Obviously, some ajax call in the editing interface was loading the index.php file, which was not executed due to the redirect.
After removing the redirect, the problem disappeared.

Hope this helps someone.
Bernd