Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Theme works well for some hours, then it crashes (website looks like there is no theme) and I get errors:
warning: array_map() [function.array-map]: Argument #2 should be an array in /home/user/domains/example.com/public_html/modules/system/system.module on line 966.
warning: array_keys() [function.array-keys]: The first argument should be an array in /home/user/domains/example.com/public_html/includes/theme.inc on line 1762.
warning: Invalid argument supplied for foreach() in /home/user/domains/example.com/public_html/includes/theme.inc on line 1762.
After I clear the cache, theme works well for some hours again.
And there is another problem (not sure, if it's connected): I usually can't run cron. Then, for example, after some days, I can run it. Then I again can't.
I'am using Zen subtheme. I don't think there is a problem in theme, because I checked it -- it's made like my other subthemes, that are working well.
It's multisite. exampe.com/public_html/ hold all files. And the site that doesn't work is one of subsites. Althought other subsites with the same Zen subthemes work fine.
Comments
Comment #1
gábor hojtsyIf you have problems with Zen subthemes, then let's submit this under the Zen project then.
Comment #2
houen commentedI have the same error, but also with Zen base theme. Drupal 6.12 install, however, on mine the error happens right after enbling zen theme. I can run cron just fine (before crash)
UPDATE: This is VERY weird. When running Zen theme, my apache crashes. This is the apache error log:
[Wed May 27 02:20:32 2009] [notice] Child 3364: Child process is running
[Wed May 27 02:20:32 2009] [notice] Child 3364: Acquired the start mutex.
[Wed May 27 02:20:32 2009] [notice] Child 3364: Starting 64 worker threads.
[Wed May 27 02:20:32 2009] [notice] Child 3364: Starting thread to listen on port 80.
[Wed May 27 02:20:38 2009] [notice] Parent: child process exited with status 3221225477 -- Restarting.
[Wed May 27 02:20:39 2009] [notice] Apache/2.2.11 (Win32) PHP/5.2.9-2 configured -- resuming normal operations
It seems like this is somehow related to http://drupal.org/node/438714
UPDATE: I have tried disabling all non-core modules, delete all content and still no luck. Zen can, however install on a "clean" subsite
FINAL UPDATE: Wow... from this thread http://drupal.org/node/128882 I got around to thinking about my CSS caching. Turns out it was turned on. Disabling it fixed the whole thing... Weird error to get from that, still...
This leads me to think if the original poster's problem isn't due to a lack of cron running, and thus having outdated css/js files? Anyway - have you tried poormanscron to fix it?
Comment #3
drupal3008 commentedSame problem here and it's related to Zen. But man it's so sporadic I don't know what's going on. I believe it has to do with cron running automatically because if I disable cron it doesn't screw up.
I can only remedy it by going and clearing the cache.
Comment #4
Schoonzie commentedI have been getting a similar problem with one of my sites using Zen 6.x-1.
It seems to only happen when I'm doing something in the admin section, and flushing the cache always fixes it. I didn't have CSS or JS file optimization turned on so that isn't it for me.
At around the time it happens I get the same error messages as the Mavros Gatos.
I've tried all the fixes that I've found for those errors but none have worked to date. If anyone can shed some light it would be appreciated.
Comment #5
drupal3008 commentedI'm going to try to work on this some more but I've simply been manually doing cron jobs, which sucks =)
Comment #6
digitalfrontiersmediaI'm seeing same problem. No css/js optimization. exact same error messages and sporadic crashes that are fixed by flushing caches.
Zen 6.x-2.0 on a multisite. Zen base in sites/all. custom sub-themes in separate site theme folders. They're named the same but are slightly different. Not sure if that matters or not.
Comment #7
barrapontorenaming to make it clearer.
Comment #8
barrapontoreports stopped coming, I guess it fixed itself.