Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
theme system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Dec 2008 at 03:39 UTC
Updated:
3 Jan 2009 at 05:30 UTC
Just wondering whether someone else is seeing this problem too.
As I work with my sites, they, at some point, completely forget about their themes.
I'd like to know where that info is saved so I could write a little something to see how it is being deleted by tracking that value. Then I could let you know what is happening. It most certainly is because of one of the 100 or so modules I'm using, but that does not help much.
So if possible, please, let me know where the info saved from admin/build/themes is saved.
Thank you!
Alexis Wilke
Comments
Comment #1
dave reidWhat exactly do you lose? Theme settings? The enabled themes?
Comment #2
andypostSuppose duplicate of #305653: Themes disabled during update
Comment #3
dave reidThat's what I thought, but I just wanted to check. We should get it fixed very soon!
Comment #4
andypostI've reopen this bug because this problem not only on update.php #305653: Themes disabled during update
My env:
drupal 6.6
psql (PostgreSQL) 8.1.9
php 5.2.6
there are 3 sites (multisiting)
2 of them has different domains and sits sites/name1.domain/ and sites/name2.domain/
third site is /sub/sites/name2.domain.sub/
all of them has a different DBs but only 3rd site "randomly" (no update no cron) loose theme (row with custom theme just removes from table{system})
Once I visit mysite/sub/admin theme returns
Modules
Comment #5
AlexisWilke commentedHi guys,
I do not really know when it happens.
But yes, it looks like what is mentioned in #305653: Themes disabled during update.
I will check to see weather I lose something or not on my next update which should be very soon (As usual)!
The symptoms are as described in the other bug. There are times when I go to the Themes panel to see that no theme is enabled and none is marked as the default. Although the site continues to work even if I do not hit save, it would be tedious if I had to select 20 themes each time!
Thank you.
Alexis
Comment #6
andypostAfter some investigation I found only few occurrences of system_theme_data
One of them update_get_projects which clears its cache every hour and then reread all projects and themes
Suppose if retrieving updates take a long time this loop can be interrupted and not all data writes to DB. I think better to change DELETE-INSERT_loop to UPDATE-DELETE
Comment #7
AlexisWilke commentedAh! Yes! I have had problems when I try to select too many modules at once. That fails with a timeout.
I would instead strongly advice for a transaction mode:
That way, if it times out in the middle, you don't have half way done changes. Now that could be a problem too... But it is much safer.
Thank you.
Alexis
Comment #8
spopovits commentedI have the same problem of radomly losing custom theme. What I did notice is that if update.php is run, it appears the next time cron runs it disables the custom theme, but not the core theme.
Comment #9
andypost@spopovits This issue about update_status and cron
About update.php please review #305653: Themes disabled during update
Comment #10
spopovits commentedI have checked that post and all the forums. this issue queue is closer to what I am seeing. I understand the update function problem and compensate for it, however periodically the non-core theme gets disabled which breaks the site, until I reenable it. There is something else other than the update.php that is disabling the theme.
Comment #11
johnalbinFYI, the update.php bug is fixed as of Drupal 6.7/6.8. #305653: Themes disabled during update
And, I've run cron.php many times with update module enable and not experienced this bug. So, its not that module per se. The bug might only be present under some specific configurations.
Those of you who are still experiencing this bug on Drupal 6.8, can you do some more testing to try to narrow down what modules/configurations are causing this?
@andypost, if you think its that line in update module, can 1.) you verify you still have the problem with Drupal 6.8 and then 2.) check if the problem is fixed if you change that line to
_update_process_info_list($projects, _system_theme_data(), 'theme');?Comment #12
AlexisWilke commentedHi John,
I ran at least one update and cron executes once per hour and I had no problems lately.
I'm running 6.8.
I have seen the fixes in the code so I guess the problem was resolved for me.
Thank you.
Alexis Wilke
Comment #13
andypostAfter update to 6.8 everything fine...