CSS problems - Stylesheet won't load

[johnbtes]

That would seem normal.
But, you said this all started happening around the time you were altering your configure.php and changing permissions, right?
Perhaps you've accidentally changed something else related to permissions.


Now, something that's puzzling ...
You said you renamed /includes/.htaccess to htaccess_off
When you did that, and then checked the server errorlogs, do you keep getting new permissions errors about /includes/.htaccess ?
You shouldn't.

So ... what happens if you delete the /includes/.htaccess file altogether? Don't rename it. Just delete it. That gets rid of the permissions issue which would follow the file when you rename it.

Yes, that same error persisted after renaming and naming back checked many times to make sure.

I have now deleted the includes/.htaccess and no changes

[DrByte]

I have now deleted the includes/.htaccess and no changes

So, after deleting the file, are the errorlogs *still* logging *new* permission errors?

[johnbtes]

So, after deleting the file, are the errorlogs *still* logging *new* permission errors?

Yes it is still logging new errors stating:

denied: /home/8190/domains/modern-contemporaryfurniture.com/html/includes/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://modern-contemporaryfurniture.com/
[Fri Apr 04 10:47:41 2008] [crit] [client 12.41.116.10] (13)Permission denied: /home/8190/domains/modern-contemporaryfurniture.com/html/includes/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://modern-contemporaryfurniture.com/
[Fri Apr 04 10:47:41 2008] [crit] [client 12.41.116.10] (13)Permission denied: /home/8190/domains/modern-contemporaryfurniture.com/html/includes/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable,

I go and refresh the webpage http://modern-contemporaryfurniture.com and then go back to my errorlog and there are new logs stating that same error.

[DrByte]

... and you're sure that you've been working with the correct .htaccess file?
ie: /home/8190/domains/modern-contemporaryfurniture.com/html/includes/.htaccess


Sounds like you need to talk to your hosting company for specific help.

[johnbtes]

... and you're sure that you've been working with the correct .htaccess file?
ie: /home/8190/domains/modern-contemporaryfurniture.com/html/includes/.htaccess


Sounds like you need to talk to your hosting company for specific help.

Does this make sense though? For the .htaccess to be affecting the permission of the stylesheets?

When I went to change the template in the Admin to classic and I just clicked preview it threw a 403 because of the preview image.

If I just edited and changed the theme I didn't get the 403, just an error talking about my meta tags module.

I'm not sure why the .htaccess would be doing this?

[johnbtes]

Does this make sense though? For the .htaccess to be affecting the permission of the stylesheets?

When I went to change the template in the Admin to classic and I just clicked preview it threw a 403 because of the preview image.

If I just edited and changed the theme I didn't get the 403, just an error talking about my meta tags module.

I'm not sure why the .htaccess would be doing this?

Here is a screenshot.



If it would help I could send full page screenshots to you showing you any area you would like to see.

[DrByte]

.htaccess can be used to handle security, and to deny access to files that people have no business touching ... namely .php files.

Some hosting configurations don't like letting you set security at the per-folder level that way (IMO that's because they don't really understand security and just operate in "scared" mode instead of truly being functional and secure at the same time).
In those cases, deleting or renaming the .htaccess file effectively removes it from the equation.

If you're still seeing errors about reading a .htaccess file ... then ... it probably still exists. Either you're doing your changes in the wrong place or you're dealing with something beyond your control.

Again, talk to your hosting company about the problem.