Missing “Layout configuration”

Events happening in the community are now at Drupal community events on www.drupal.org.
nwilds's picture

Using the Omega framework I started to create a site in a development environment. Half way through development I had it moved to a different development environment. I just noticed that the “Layout configuration” (grid settings, zone and region configuration, etc.) is missing in the new development environment (under Appearance – www.your-domain.com/home#overlay=admin/appearance/settings/your-subtheme). Rather, that page starts with “Toggle Display”. I have tried re-installing the themes, clearing caches, and running cron. The DBA has asked me to do some research on which tables are being used in the operation of this theme so a comparison can be made. Does anyone know which tables within the DB the Omega theme/subthemes live? Any advice would be appreciated. Thank you.

Comments

Are there any other

mchris82's picture

Are there any other noticeable issues with your site after moving environments? Are there any differences in the configuration of the original and new dev environment?

I'd check your settings.php file for any changes that need to be made regarding the new environment.

Thanks for the replay.

nwilds's picture

Thanks for the replay. Besides missing the layout configuration both environments seem to be identical (at least what I see on the front end). In fact, I have been working in the new dev environment for 3 weeks and just notice the missing layout configuration when I went in to turn on the grid. With the exception of environment paths, the settings.php file is the same. The DBA used a script to copy the environments. He believes there may be a reference in a table causing the issue (at least that is how I interpret it). We are just trying to figure out which haystack is the best to start looking for that needle. :)

Use Omega tools to export

JSCSJSCS's picture

Use Omega tools to export your original theme settings (which creates a new .info file based on your database settings). Then copy that .info file to your new installation. That will probably fix your issue.

James Sinkiewicz
Drupal Site Builder and Generalist
http://MyDrupalJourney.com

variables

drew reece's picture

Try the variables table.
If your migration is not taking all tables you will need to go over the entire site to be sure you have everything. Sessions, Watchdog, and Caches are usually safe to discard depending on your setup.

Most "migrations" involve

JSCSJSCS's picture

Most "migrations" involve someone running install.php again. When you do this, even thought the omega settings are in the database, they are overwritten when the .info file (containing original/default settings) is re-run during install.php, overwriting your database settings with the old .info settings. That is why you need to use omega tools to create a new .info file for migrations.

James Sinkiewicz
Drupal Site Builder and Generalist
http://MyDrupalJourney.com

This just passed onto me,

nwilds's picture

This just passed onto me, "After exporting the theme settings to the .info file, copied the .info file over to the migrated site, and initiated the revert process. Afterward, we could see that the the 'variables' record in the bootstrap cache had been recreated -- but was no larger than before. (Indicating that the omega theme related settings are still missing/not included.) So the revert process is evidently functioning and triggering a re-read & rebuild of the bootstrap cached variable blocks, but the omega related variables are still not in the bootstrap blocks..."

Update:

nwilds's picture

The problem has been solved (see comment below). Thank you to everyone who contributed!

"The publish scripts (going from one dev environment to another dev environment) had an exclusion for the settings.php file, and this exclusion was also matching the theme-settings.php file under the omega/omega/ directory, and also the one under omega/alpha/. I was able to copy the files from a working site to these locations, and the appearance/settings dialog returned for these virthosts. All should be fixed now."

Same problem here

melissjs's picture

Hi everyone, I am having this very same problem but I don't have a working site to copy the files from like Nwilds did above. Is there a place I could have messed up path variables here? When I ran update.php I got a lot of warnings to this effect (all about the omega/alpha and omega/omega directories):

Warning: array_keys() expects parameter 1 to be array, null given in alpha_get_theme() (line 227 of /home/melissjs/public_html/TVR04162015/profiles/commerce_kickstart/themes/omega/alpha/includes/alpha.inc).
Warning: Invalid argument supplied for foreach() in alpha_get_theme() (line 227 of /home/melissjs/public_html/TVR04162015/profiles/commerce_kickstart/themes/omega/alpha/includes/alpha.inc).
Notice: Undefined index: omega in alpha_get_theme() (line 238 of /home/melissjs/public_html/TVR04162015/profiles/commerce_kickstart/themes/omega/alpha/includes/alpha.inc).

Any help would be so appreciated.

Omega Framework

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: