Issuing a command like:

drush block-configure --module=views --delta=shop_all_products-shop_toc --region=sidebar_second --weight=10

in a bash shell on the command line causes the block (previously disabled) to be moved to sidebar_second as expected. In the admin UI however (admin/structure/block) ALL the other entries in the disabled section (bottom of page) disappear. The blocks previously shown in the disabled section are still in the DB. And I can move them to other sections with the drush block-configure command.

Comparing the block table in the DB to a the DB on our Development machine shows no differences AFAICT.

This is possibly related to https://www.drupal.org/node/2266489 - drush block-configure from a script. Some kind of environment issue?

Comments

greg.1.anderson’s picture

greg.1.anderson commented

I did not write this code; it was contributed. If you find the solution, a patch to fix it would be appreciated.

Helmut Neubauer’s picture

Helmut Neubauer commented

I did a look at the source. It seems, the contributor uses the normal form (block_admin_display_form) to update the blocks. I'm not sure about the details, the submit method expects, so I can't provide a useful patch.

It's generally a problem of losing the "-1" region of the disabled blocks. As workaround you can add the following line to the block.drush.inc in the save method:

db_query("update block set region = -1 where region = ''");"

I

kat5con’s picture

kat5con commented

I'm seeing this problem as well.