garland theme / color picker broken

By kginger on 23 Feb 2007 at 01:31 UTC

I followed some other threads about the garland theme and private files (File System) but I can't seem to solve this issue. The color picker DOES show up but I get this error everytime I change the color or the logo image - immediately after saving changes:

* warning: chdir() [function.chdir]: No such file or directory (errno 2) in ./modules/color/color.module on line 289.
* warning: fopen(files/color/garland-ed07b5f5/style.css) [function.fopen]: failed to open stream: No such file or directory in ./modules/color/color.module on line 338.
* warning: fwrite(): supplied argument is not a valid stream resource in ./modules/color/color.module on line 339.
* warning: fclose(): supplied argument is not a valid stream resource in ./modules/color/color.module on line 340.

this all happened after I went from public to private files (and the color picker disappeared) and then back to public

any ideas?

files directory is writable.

Comments

Maybe out of memory?

bobseekone commented 26 February 2007 at 20:57

I couldn't save the changes from the Garland theme color picker either - I always got a blank page. Looking in /var/log/httpd/error_log showed that I was running out of memory for PHP.

Increasing the memory_limit = 16M in /etc/php.ini fixed the problem.

Files do not exist

tboudreaux commented 18 July 2008 at 14:55

Wow, this is a fairly old post, but I have a very similar issue to both of you, and I've tried the solutions in the following threads, but nothing has worked thus far.

http://drupal.org/node/134275

http://drupal.org/node/110916

Basically, when I try to save changes to Garland it takes me to a blank page. Reloading the page (or site) shows no theme changes. However, a "garland-fd99b..." folder is created in the files/color directory, and all permissions look good. It's almost as if the site can't load the files within the newly created folder, but I've checked all of the settings in drupal, php and on the server. Everything is good.

After opening up the error_log in /var/log/httpd I see that every time the site is opened there is a "File does not exist" error for style.css and logo.png files that apparently should be in the files/color/garland-***** folder. Sure enough, they're not there. And I also see "Allowed memory size exhausted" errors in the server log after so many failed attempts. (16MB)

It seems like my issue is that style.css and logo.png are not being created, but I can't tell if this is a permission issue or a code issue (maybe a module that's screwing things up?).

Problem Solved!

tboudreaux commented 18 July 2008 at 15:14

After trying everything else I upped (not sure if that's a word) my PHP memory limit to 26MB. Not sure why I needed more, but now when I save changes to Garland all files are created. There are now 17 files in the garland-##md5hash## folder, as opposed to the 4 that were being created before.