CMS Made Simple Forums

Well, I'm stumped. I have a site I've been running since 2008 without incident. CMSMS 1.6.5. I've made no site changes recently. Yesterday, however, someone reported they were getting only a "navigation page" and couldn't access any of the site's pages. Sure enough, that's what it looks like. The code is being retrieved and parsed from the DB, but it's like the CSS is not being rendered. The system info is as follows:
----------------------------------------------
Cms Version: 1.6.5

Installed Modules:

CMSMailer: 2.0.1
FileManager: 1.1.0
MenuManager: 1.6.2
ModuleManager: 1.3.1
News: 2.11.3
nuSOAP: 1.0.1
Printing: 1.1.2
Search: 1.6.1
ThemeManager: 1.1.4
TinyMCE: 2.5.4
LightBox: 1.0.1
FormBuilder: 0.5.11
CGExtensions: 1.17.2
CGCalendar: 1.2.3
Album: 0.9.3
Album: 0.9.3
CGExtensions: 1.17.2
CGCalendar: 1.2.3
FormBuilder: 0.5.11
LightBox: 1.0.1
CGGoogleMaps: 1.4
EventsListing: 1.4
avplayer: 1.01
CGSimpleSmarty: 1.4.4
CMSMailer: 1.73.13
Gallery: 1.4.4


Config Information:

php_memory_limit: 96M
process_whole_template: false
max_upload_size: 2000000
default_upload_permission: 755
assume_mod_rewrite: true
page_extension: .html
internal_pretty_urls: false
use_hierarchy: true


Php Information:

phpversion: 5.2.17
md5_function: On (True)
gd_version: 2
tempnam_function: On (True)
magic_quotes_runtime: Off (False)
memory_limit: 96M
max_execution_time: 300
safe_mode: Off (False)
session_save_path: /home/users/web/b1753/whl.dmactkd/cgi-bin/tmp (0755)


Server Information:

Server Api: cgi
Server Db Type: MySQL (mysqli)
Server Db Version: 5.0.91
----------------------------------------------
I checked the web host, because sometimes they make upgrades without informing the customers, but PHP and MySQL are installed and seem to be running correctly.

So I edited config.php and set
$config['debug'] = false;
in order to see what's wrong. Then I reloaded the site and everything seems to run normally now. CSS is being rendered and I can navigate the site. Except now there's a couple hundred lines of debug info at the bottom of the site pages, so I can't leave it that way. The debug info shows nothing out of the ordinary, no errors appear and all the SQL is returning results as it should. Setting $config['debug']=true again causes the original problem to resurface.

What is it about setting debug ON that would cause the problem to correct itself? Anyone got any thoughts, 'cause I'm out of ideas here.

1.6.5 is no longer supported; upgrade is eminent.

Thank you, staartmees, I would not be surprised if 1.6.5 is no longer supported, and yes, I should upgrade. But it doesn't address the question. Why would the site suddenly stop rendering CSS and only render if debug=true?

Probably because modules need php 5.3 and you have 5.2, and an old cms

I'm not understanding. Modules should be updated only if I manually replace them or if I have upgraded CMSMS. If they previously ran under PHP 5.2 and I have not changed the modules, were they automagically refreshed?

I too am experiencing the same problem. All of a sudden the style sheets are not loading for my pages. This started to happen occasionally yesterday, June 10, 2013, but today is happening all the time - same day as banjoman reported this problem!

I discovered that CSS loads fine when I use Chrome, but not when I use Internet Explorer or Firefox. For either Internet Explorer or Firefox, if I clear the cache, the CSS will load fine one time. But if I click the refresh button, or try to go to the same page a second time, CSS will not load until I clear the cache again.

I have an older version of CMS (1.9.4.2) I also have an older version of PHP (5.2.17). So I tried upgrading to PHP 5.3 as was suggested to banjoman. It didn't help. The same problem remains, and it will not load the style sheets.

I tried upgrading my CMS last summer, but I could not get it to work. I went back to 1.9.4.2 just so we would have a working website for our church. I'm hoping to try again this summer during our off season.

Any tips on why loading CSS stopped working all of a sudden and what I might be able to do to fix it would be appreciated.

Thanks!

It sure seems like the hosts made changes on both cases...
There should be errors listed on the server php error log and probably some clues also on CMSMS own admin log. It's difficult to help or debug without knowing if there is an error (which most surely is) and where.

The only errors on my php error log were from when I tried switching to php 5.3 but php.ini wasn't configured correctly for CMS. So I switched back to php 5.2 and copied back in the php.ini file that had been there before. Should new errors appear on my php error log every time I reload the page and it fails to load the style sheet? If so, it isn't. There are no new errors on the php error log when I refresh my web page.

The Admin log shows only one error which appeared later this afternoon, long after the problem started with the style sheet:
FormBuilder submit error: SMTP Error: Could not connect to SMTP host. smtp.zumbrolutheran.org:587
Because of its timing, I'm guessing it is unrelated to the style sheet problem. Our website gets used heavily.

The only other things on the admin log are the usual user logins/logouts, page content changes made, and automated tasks to prune the admin log and gather notifications. These are the same activities that appear on the admin log every week.

I also checked the Error Console in the Firefox, and the Developer Console in Internet Explorer. The Firefox Error Console lists no errors when I try to load the page. The Internet Explorer Developer Console lists 3 warnings, no errors:
HTML1524: Invalid DOCTYPE. The shortest valid doctype is "<!DOCTYPE html>".
www.zumbrolutheran.org, line 1 character 1
HTML1423: Malformed start tag. Attributes should be separated by whitespace.
www.zumbrolutheran.org, line 768 character 9
HTML1512: Unmatched end tag.
www.zumbrolutheran.org, line 837 character 1

Is there possibly something wrong with the doctype statement in my template?
{process_pagedata}<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

Where else might I look for logged errors?