Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Drupal 7.23 on Apache 2.2, PHP 5.3
Changing a custom color scheme fails. The log shows:
MESSAGE File temporary://file0H0SXS could not be copied, because the destination directory public://color/skeletontheme-92e451ed is not configured correctly.
Comments
Comment #1
krueschi CreditAttribution: krueschi commentedHi,
looks like there is no write access to your (public) file directory or the public file directory is not set properly in
admin/config/media/file-system
.Test to make a custom color change works just fine for me.
Comment #2
jessZ CreditAttribution: jessZ commentedI could not save custom color settings. I didn't get a meaningful error message except for
"The custom favicon path is invalid." which seems to suggest some sort of path problem for the theme to find it's own settings.
EDIT: I created a favicon.ico file (just to get rid of that error) and the configuration saved.
The site is not a fresh install, but a drupal 6>7 upgrade. Alas there are so many 6>7 upgrade problems that posting an issue isn't too fruitful but I wonder if anyone on this thread is aware of ways that drupal directories/ themes/ permissions / paths might have changed between 6 and 7. I tried installing the theme directly in the /themes directory (instead of /sites/all/themes subdirectory) but the same inability to save the settings occurs. The reason I am posting here (under skeleton) is that the garland theme, also installed in that directory saves its settings (including color changes) with no problem.
All the other webforms and submission forms on the site seem to be working fine.
Is there a table change in drupal>6>7 that might be a missing ingredient for finding the path?
The error log has no interesting errors. The .htaccess warning for /files and /tmp is showing up in updates but i don't see why garland would work and skeleton fail if this has something to do with wider permissions or path problems.
Long story short. I created a favicon.ico file (just to get rid of that error) and the configuration saved.
Comment #3
krueschi CreditAttribution: krueschi commented