It's generally a *really* bad idea to write code that "corrects" for a bug. That code almost always becomes a bug itself. So I encourage you to *solve* the problem instead :-)On Tue, Feb 8, 2011 at 8:42 AM, Pooya <pooya.source@gmail.com> wrote:ok then I'm going to start testing through this bug. However still feel like it might be sections problem, so I'll check section module codes see if there's a line which disables a theme in specific conditions.last solution might be writing a module that take cares if theme is disabled on each page request, if not enabled -> enable.On Tue, Feb 8, 2011 at 6:45 PM, Randy Fay <randy@randyfay.com> wrote:
Really, you can't get any help until you can recreate the problem.
Try all the things you've suggested and see if you can make it happen predictably. Use a notebook or something to list the permutations you've tried. Try to figure out all of them.
http://randyfay.com/debugging might be useful to you for strategy on this.
When you have a way to recreate it, then it can be fixed, one way or another.
-Randy--
On Tue, Feb 8, 2011 at 7:56 AM, Pooya <pooya.source@gmail.com> wrote:I've got a weird problem my theme. I've got 2 custom theme, one default for main website and another admin theme. I also use sections module to simulate a joomla-like admin page. problem here is that admin theme becomes disabled sometimes so admin users see admin page with default theme! so everytime I have to login user/1 and enable admin theme.
I have no idea why this happen but kinda feel like mostly when I visit a alias, run cron(not all the crons) or add new section.this one happens everyday or 2.any1 can help me out here? I'm done with the site which I'm working for a month on it, but can't install it for my client yet since this crit bug
--
--
Randy Fay
Drupal Module and Site Development
randy@randyfay.com
+1 970.462.7450
--
--
Randy Fay
Drupal Module and Site Development
randy@randyfay.com
+1 970.462.7450