Drupal Themes Getting "Unselected"

Sometimes at least 1 time per month + - when I am on my site, the topic is not selected and I get a lot of error code.

Notice: Undefined index: highlighted em include() (linha 120 de /var/www/novoportal.faccat.br/htdocs/portal/modules/system/page.tpl.php). Notice: Undefined index: sidebar_first em include() (linha 132 de /var/www/novoportal.faccat.br/htdocs/portal/modules/system/page.tpl.php). Notice: Undefined index: sidebar_second em include() (linha 138 de /var/www/novoportal.faccat.br/htdocs/portal/modules/system/page.tpl.php). Notice: Undefined index: genesis em drupal_theme_initialize() (linha 100 de /var/www/novoportal.faccat.br/htdocs/portal/includes/theme.inc). Notice: Trying to get property of non-object em _drupal_theme_initialize() (linha 145 de /var/www/novoportal.faccat.br/htdocs/portal/includes/theme.inc). Notice: Trying to get property of non-object em _theme_load_registry() (linha 321 de /var/www/novoportal.faccat.br/htdocs/portal/includes/theme.inc). Notice: Undefined index: genesis em theme_get_setting() (linha 1316 de /var/www/novoportal.faccat.br/htdocs/portal/includes/theme.inc). 

I always need to select a theme again and clear the cache.

I also used the Devel theme rebuild tool, but I keep getting these errors.

Any ideas?

+6
source share
5 answers

Here is what I suggest:

1) First check the .info file and make sure that it contains regions at page.tpl.php. This error is based on this.

2) If the above value is true, then the next thing I would like to do is make a new new installation and only move the sites / all / themes / folder, and then I will go through it to make sure that the error does not occur.

Hope this helps.

+3
source

From your description, I think it might be a weird mistake in opening a Drupals theme - try calling:

 _system_rebuild_theme_data() 

One call for this should be sufficient, so do not leave it constant - as this harms the loading of your site.

I registered an error and description .

Edit

The above probably won't solve your problem forever, I just thought it would be at the time of writing.

+1
source

I believe that this may be caused in some cases by a failed start of cron.

I observed this problem on a dev site where I was basically the only person interacting with it. A problem may occur after several hours of inactivity. The only events in the log will be related to cron runs.

I was able to determine that a normal, user initiated cron start would not cause a problem.

One type of cron entry was an "invalid key" error. I researched and decided that a cron job was given to run without a key. After eliminating this cron job, I could no longer observe the error.

+1
source

i also encountered a similar problem after installing the https://www.drupal.org/project/nucleus theme kernel (which is required to install any custom theme on drupal7), and secondly, I deleted the cache entry for my custom theme ( drupal_cache table), and then the problem was fixed. Now I could see the modules, then I went to the "Appearance" tab and set my theme as the "Default" theme. Hope this helps

+1
source

Although I have no answer to this problem, I thought it might come in handy to add some cross-references:

If you find more links, add them here!

EDIT (2014-10-22): In a multi-node environment, we did not set a default site first. Because of this, Drush sometimes generated warnings or errors, so we added the settings.php file to the default site directory with the credentials of the test site database database. Since we installed the default site with its own database, the problem, fortunately, no longer occurred. :-)

Perhaps this had something to do with the simultaneous execution of several clones in the same database ...?

0
source

Source: https://habr.com/ru/post/914725/


All Articles