This is a rather specific issue. I'm using views along with context and i18n. The problem occurs when I save a view block. The block table does not immediately reflect that I've added a new block, the table only updates if I go into the blocks page and click save. Now the fact that I'm using context means I don't actually ever go into the blocks page. The i18n module depends on there being an entry in the block table for every block as it uses an attribute i18n_mode belonging to each block.

Comments

dawehner’s picture

dawehner
Primary language German
commented

Well the blocks table is rebuild based on certain clear cache events, they are triggered probably on the block page but they could be also runned on context.

I'm not sure whether it's logical to rebuild the blocks when saving a view.

cdesautels’s picture

cdesautels commented

I'm having a problem with this as well and I don't see the record being cleared from the block table under any circumstances. Even if I delete the view that generates the block, clear all the caches (using admin menu) and re-save the block page. The block record remains. This is very frustrating. Views should clean up after itself.

Lightsaber’s picture

Lightsaber commented

Same problem here. I was using hook_block_list_alter and noted deleted view blocks still showing up in the $blocks array. I took a look at the block table and it shows those deleted blocks as still being defined by the views module.