CSS problems - Stylesheet won't load

[johnbtes]

.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.

Sounds good. I'll look into this and post updates here.

[johnbtes]

So i'm trying to look at this as logically as possible.

Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /mnt/gs01/herd04/8190/domains/modern-contemporaryfurniture.com/html/includes/configure.php:135) in /mnt/gs01/herd04/8190/domains/modern-contemporaryfurniture.com/html/includes/functions/sessions.php on line 108

Warning: Cannot modify header information - headers already sent by (output started at /mnt/gs01/herd04/8190/domains/modern-contemporaryfurniture.com/html/includes/configure.php:135) in /mnt/gs01/herd04/8190/domains/modern-contemporaryfurniture.com/html/includes/init_includes/init_templates.php on line 78
™ ™
Warning: I am able to write to the configuration file: /home/8190/domains/modern-contemporaryfurniture.com/html/includes/configure.php. This is a potential security risk - please set the right user permissions on this file (read-only, CHMOD 644 or 444 are typical). You may need to use your webhost control panel/file-manager to change the permissions effectively. Contact your webhost for assistance.

The warning is talking about headers being sent out. Well, the problem with every call to a css file is 403 forbidden and they are all located in the head of the document. So is the logo and it is not accessible. But the favicon.ico is located in the head and it still shows up.

Let us all ponder.

[DrByte]

Cannot modify header information - headers already sent by (output started at /mnt/gs01/herd04/8190/domains/modern-contemporaryfurniture.com/html/includes/configure.php:135) in ...

Warning: I am able to write to the configuration file: /home/8190/domains/modern-contemporaryfurniture.com/html/includes/configure.php ...

What's with the different paths being specified?

[johnbtes]

What's with the different paths being specified?

I know, I have no clue what that path is at the top. I'm assuming something with my server. I host through MediaTemple.net by the way.
So I found this, by setting the permission to 644 on my includes/functions/sessions.php is makes my entire site forbidden, but when it is set to 755 it remains as is with the broken stylesheet. <-- does this spark any ideas?

[DrByte]

Have you talked to your hosting company about this situation?

[johnbtes]

Have you talked to your hosting company about this situation?

Yeah, I was on the phone with them for about 45 minutes. So they are working on it now and trying to find the source of no permissions.

[johnbtes]

Yeah, I was on the phone with them for about 45 minutes. So they are working on it now and trying to find the source of no permissions.

I'm just installing a fresh copy and redoing everything. I Love It!