On your "/store" site, you have understandably been toying with debug ideas etc. It also appears you've hard-coded a stylesheet reference, but it's not working ... because you made a typo. The "type" should be "text/css":```
<link rel="stylesheet" type=
[B]"text/cass"[/B] href="http://jerkynet.com/store/includes/templates/jerkynet/css/stylesheet.css" />
```
However, that's not the root cause of the problem. But, once you change that, you'll see that things do load properly.
Thus, since you've had to hard-code the stylesheet references manually, that means that the Zen Cart code that dynamically discovers and links stylesheets is unable to find the style*.css files in the css folder.
This is most likely a permissions issue whereby either:
a) PHP is not allowed to stat the css folder in order to "list" the files contained therein, and therefore can't create the output links
b) PHP or the webserver user (typically "nobody") doesn't have permission to read the files in the css folder
c) or some other issue.
For debugging purposes, let's turn on PHP error-reporting:
- Create a new file: /includes/local/configure.php
- In that file place only the following:```php
<?php
define('STRICT_ERROR_REPORTING', true);
?>
3. Upload the file and try accessing your site.
You'll see all kinds of warnings and errors. Hopefully one of them (where it builds the stylesheet links) will provide more hints.
You'll likely also get php halts because of "header already sent" messages -- these are a result of the php error/warning output and will go away once you delete this local/configure.php file after the rest is working again.
Also, what is your server's errorlog saying ?
.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole
Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.
