Domain Variable Settings

Synopsis

This project fills the gap between domain_conf / domain_settings and domain_variable. domain_variable and domain_conf are using different approaches of changing the values in the drupal variable system and are thus incompatible #1993588: Compability with Domain Conf. It does so by hooking into form submission and mimic the way domain_settings handles data saving with the big difference of actually saving data into the variable_store table.

So why are those modules incompatible anyway?

domain_conf loads the specific variables values during domain bootstrap phase using hook_domain_bootstrap_full (domain_conf.module:50).

domain_variable depends on the variable module to load the variables. Varialbe does so (domain_realm) by using hook_boot (variable_realm_boot calls variable_realm_rebuild, which assigns _variable_realm_build return value to $GLOBALS['conf']).

But as the domain module is called prior to any other module (it needs to, in order to prepare all domain specific stuff) it goes first. Later on the variable module simply rebuilds the complete varaible registry. By that all changes done by domain_conf are simply lost.

Basic use case

• Using domain_settings and domain_varaible
• Give the varaible module the ability to fill the varaible registry properly

Requirements

This module requires:
domain_settings
variable_store (2+)
variable_realm (2+)

Roadmap

As this module is in fact only 55 lines of code, it would make sense to be included in either domain, or domain_variable

Known problems

none yet.

Similar projects and how they are different

This module is in fact very close to what domain_variable does. The difference is: this module will not be able to give you the option to save a variable domain specifically if you could not do so with domain_settings. It merely makes domain_settings compatible to varaible.

Did I save you some time?