If you don't export your theme to code you get the nag drupal_set_message that says:

"The settings for this theme are currently served from a variable. You might want to export them to your .info file"

Lets have a way in the admin settings to shut this off. While someone is working on a site and doing a lot of theme work this set message drives you "nucking futs". My fingers grew tired of doing drush omega commands so I deleted the lines from the code that sets the message so I can keep my sanity.

Thanks! Keep up the good work!

CommentFileSizeAuthor
#16 nag_screen_exported_settings-2182105-16.patch3.67 KBsylus
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hturner’s picture

hturner CreditAttribution: hturner commented

Yes Please.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Let me know if you want to know where to hack/disable this. I know how annoying it is.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Agreed, I'm interested. And also slightly off topic, but what is the current method to turn off those update messages as well? Since I have a media 7.2 dev install bugging me about a 7.1 security update.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Bugging you where?

To disable the nag screen go to

omega/omega/includes/development/development.inc

Comment out line 128 (a drupal_set_message() )

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Thanks. It's bugging me on every content page.. "There are security updates available for one or more of your modules or themes. To ensure the security of your server, you should update immediately! See the available updates page for more information and to install your missing updates." - yep upgrade from .2 branch to .1 - great idea!

fubhy’s picture

fubhy CreditAttribution: fubhy commented

Disable the update manager module if those update messages annoy you during development. However, that is absolutely not on topic for this issue (please open separate issues with unrelated questions in the future).

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Second @fubhy You are mixing apples and oranges. You are talking about Drupal Update messages not Omega messages. We are talking about the Developers messages for Omega here.

Back to the topic at hand. I hacked the module to turn off those drupal_set_messages. I don't want to save the thing to code all the time. I'm working on a local machine that damn message was about to drive me f'king insane.

monching’s picture

monching CreditAttribution: monching commented

#4 - sure did worked for me. @Perignon. Thanks!

fubhy’s picture

fubhy CreditAttribution: fubhy commented
Status: Active » Fixed

Fixed in http://drupalcode.org/project/omega.git/commit/f34a828

There is now a setting for this in the development extension. Furthermore, all messages will only be printed if the development extension is enabled in the first place.

Perignon’s picture

Perignon CreditAttribution: Perignon commented

Thanks!

hturner’s picture

hturner CreditAttribution: hturner commented

Thanks fubhy.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

s_leu’s picture

s_leu CreditAttribution: s_leu commented
Status: Closed (fixed) » Needs work

Shouldn't the message also be disabled on the theme settings form?

See here (taken from the latest dev release):

function omega_form_system_theme_settings_alter(&$form, &$form_state, $form_id = NULL) {
  // General "alters" use a form id. Settings should not be set here. The only
  // thing useful about this is if you need to alter the form for the running
  // theme and *not* the the me setting. @see http://drupal.org/node/943212
  if (isset($form_id)) {
    return;
  }

  if (variable_get('theme_' . $GLOBALS['theme_key'] . '_settings')) {
    // Alert the user that the theme settings are served from a variable.
    drupal_set_message(t('The settings for this theme are currently served from a variable. You might want to export them to your .info file.'), 'warning', FALSE);
  }
fubhy’s picture

fubhy CreditAttribution: fubhy commented
Status: Needs work » Postponed (maintainer needs more info)

I thought it would be helpful to show it on the backend. It doesn't get in the way there much, does it? Unless of course you are building a backend theme but even then it only shows up on the theme settings page. Is that a problem? :)

s_leu’s picture

s_leu CreditAttribution: s_leu commented

Well at least for me it's rather confusing than helpful as i expected the message to completely disappear when disabling it using the new checkbox. Yes it doesn't get in the way actually so it could be left there. I personally would remove it though when the option is disabled.

sylus’s picture

sylus CreditAttribution: sylus commented
FileSize
nag_screen_exported_settings-2182105-16.patch3.67 KB

For drush make purposes and to not need to checkout git repo. I am just attaching a patch made to Omega 4.2. Unfortunately D.O can't package when using patch format in cgit directly.

Perignon’s picture

Perignon CreditAttribution: Perignon commented
Category: Feature request » Bug report
Priority: Normal » Major
Status: Postponed (maintainer needs more info) » Active

Ok I am still getting this on a new site I am building. I just hacked the module again to turn the nag message off as the logic creating the nag message is flawed. My settings ARE exported to the .info file but I still get this darn message.

I would say that this nag screen needs shut completely off till it is proven that it is correct. After running a fresh "drush omega-export" and confirming a change is made to the .info file via "git diff -w" still get this problem. Hence I am changing this to a bug report instead of a feature request.

steinmb’s picture

steinmb CreditAttribution: steinmb as a volunteer commented
Category: Bug report » Feature request
Priority: Major » Normal