Hi,

In addition to this post http://drupal.org/node/430886 I want to add one thought about centralised block settings storage.

The idea is to make block settings easy extendable. Now to add a few custom settings to a block we need to invent something: either create a new table or store them in variables.

Here is a little overview of how different modules solve this issue:

  1. Superfish - stores block settings in variables
  2. Menu Block

    3. - adds a table

  3. Block Class

    4. - adds a table

As a result there are two big issues:

  1. Lots of tables and SELECTs. RIght now we have several sites which uses Superfish, Menu Block and Block class which means 3 SELECTs + 4 SELECTs (from core) and +1 SELECT from our custom table... which is in total 8 separate SELECTs to read all block configuration
  2. Modules need to waste time to implement storage for their block settings

If you already have an idea how to solve this issue please share it... but reviewing D8 I found that this issue is still not solved and in addition we have a new table block_languages...

Thanks.

Comments

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
commented
Issue summary: View changes
Status: Active » Closed (duplicate)

Block settings are now in config and are defined by their plugins.