There are certain cases where it just doesnt make sense for a variable to be exported to code or cached somewhere other than in the variables table itself.

It would be pure awesome if there were a way to specify a list of variables that should NEVER be exported or cached... and also, completely hidden when building/exporting settings using the Features UI.

Here is one such case from comment #55 on #1094598-55: Performance issues from strongarm_init().

We were having issues with cron thinking it was still running for along time, but there was no cron_semaphore variable. We finally found strongarm setting $GLOBALS['conf']['cron_semaphore'] ...

Comments

simon georges’s picture

simon georges commented

Maybe related to #708090: Classify variables by module in feature creation, it could be a task for Variable module.

bblake’s picture

bblake commented

An example of a variable that we would never want to be exported / available in the features UI:
http://drupal.org/node/1293298

bblake’s picture

bblake commented
Issue summary: View changes

Wording cleanup.