By irishwinereview on

I keep getting weird formatting errors in firefox when I try to change any theme from the bog standard. Selecting "ash" as a theme from Garland results in these formatting errors. The only solution I've been able to come up with is to hardcode garlands style.css but this is proving daunting and an annoyance as I would like to change the colors quickly.

Any help?

⋅ Categories: Drupal 6.x

Comments

irishwinereview’s picture

irishwinereview commented

I had a look through the fourms here, and followed some advice (turning caching on), yet still no luck. When trying to turn on CSS cashing the exact same misplacement and distortion of the theme show up - both under FF and IE on two different computers.

LiquidWeb’s picture

LiquidWeb commented

Can we see site?

irishwinereview’s picture

irishwinereview commented

http://nickgeoghegan.net/

LiquidWeb’s picture

LiquidWeb commented

Your problem is a missing CSS file
When I looked at CSS files all files apart from "/sites/default/files/color/garland-b6d9947b/style.css" seemed working only that file gives "500 Internal Server Error" This may be because of many reasons try to change chmod of "files" and all subfolders to 755 and clear all chace and if this does not work try uninstalling and installing color module.

irishwinereview’s picture

irishwinereview commented

Hey,

Tried all that but still no luck. I reinstalled drupal too, but still no luck. Very confused!

I don't mind hard coding the colors into styles.css, but it just makes it so darn complicated to change!

LiquidWeb’s picture

LiquidWeb commented

Your site seems ok now. Check your browser cache :) especially if you are using opera

It is broken again and it is again 500 error. check if there is such files in
/sites/default/files/ad_blueprint/custom.css
/sites/default/files/color/ad_blueprint-9c085c9e/style.css

irishwinereview’s picture

irishwinereview commented

Yeah, sorry. Should have said I moved back to a default theme, all that unformatted text was annoying me!

irishwinereview’s picture

irishwinereview commented

Ok, I found a workaround to this issue. by moving the custom style.css from sites/default/files/color/ad_blueprint-6ba1c5ab to /themes/ad_blueprint/

It's not ideal, but it works!

LiquidWeb’s picture

LiquidWeb commented

This may be php safe mode issue. Once my hosting provider activated safe mode then I got 500 error from all files and directories with chmod 777. I don't remember exacly but changing 777 to 775 or 755 worked for me. But you may try adding "php_value safe_mode off" to .htaccess and turn off safe mode.

keeline’s picture

keeline commented

I recently installed xampp 0.7.4 on MacOS X 10.4.11 which included PHP 5.2.6, Apache 2.2.9, and MySQL 5.0.67. Once this was working I added Drupal 6.8 and experienced some of the same problems indicated here.

  • Clean URLs was not available to be activated
  • Themes would not allow an uploaded custom logo to appear
  • Attempts to change color via color.module in the Garland theme to another predefined color palate or a custom one generated pages which stripped the CSS from the navigation menu and overall layout
  • Trying to access the custom style.css page or the uploaded custom logo image generated an Error 500, Internal Server Error, from Apache.

I tried a number of suggestions connected with permissions and the contents of the .htaccess files. Nothing really worked the way it was supposed to.

This morning I had a breakthrough that got things working. I went into Apache's configuration file (httpd.conf) and was able to add the directives to ensure that .htaccess files could include any allowed directive (AllowOverride all). Next, because I had two directories with trial Drupal installations, I defined Directory containers in httpd.conf for each path that included the directives mentioned on the Clean URL page. Specifically I added:

   RewriteEngine on
   RewriteBase /
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]

As with any change to a server configuration file, I restarted Apache. I found that this allowed me to use the Clean URL option. This is linked to the problems with the color.module and Garland theme as well as the custom logo upload. They both work properly for me after Clean URLs are working. It would appear that the code for these features do not work well with the GET variables (?q=...) in the URL and require Clean URLs.

Perhaps a check should be made in these programs to see that Clean URLs are enabled if it is not possible to get them to work with and without Clean URLs.

I spent a few hours on this and hopefully this post will save others this amount of time or even longer.

James Keeline