Apologies in advance if this is answered already but can't find anything after searching.

Since upgrading to 6.20 I have not been able to save any changes to my blocks. When I set a block to any region it defaults back to the original setting of 'none' after saving. Also the order is not saved after dragging a block to a different order on the block page.

I have removed cache and also checked that my theme is selected correctly and there was no error when updating update.php

Has anyone else encountered this? Any help would surely be appreciated

Comments

fibie’s picture

Bump anyone had this issue?

kevinn’s picture

Yes this happend to me now when i upgraded from 6.19 to 6.22

dpearcefl’s picture

The blocks listing is partially broken in that it can display the block settings from another theme. The save works, it is just displayed incorrectly. Does the block actually show in the proper place in the region your selected?

carn1x’s picture

I'm getting this problem in 7.2 as well, don't think I had this problem before upgrading in the last week or so.

kevinn’s picture

My issue was the max post data limit in php.ini

carn1x’s picture

jdench’s picture

I had the same issue with drupal 6.26, when using PHP 5.3. The problem went away when I reverted to PHP 5.2.17.

todddd’s picture

I had this problem, but disabled modules that I wasn't using and now it works again. Suspect it was either display suite or bean as I had both of those.

janekD7’s picture

For Drupal 7 the cause of this issue was Bean All module. The only solution I came across was to disable Bean All. Now everything works fine.

lidia_ua 🇺🇦’s picture

Issue summary: View changes

Bean module was causing the problems for me too. I couldn't move blocks to any region or save them.

mkhalils’s picture

Yes! do disable the bean module.Its worked for me.

cswan’s picture

I had the similar issue in D7. After increasing php value of max_input_vars, it seems to be working now.

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.

saad.waseem’s picture

yes @janekD7 you are quite right. i faced the same issue with drupal 7.41 and it was beans module which was causing this problem
I disables the module and things get normal