CMS Made Simple Forums

Sorted, for now at least. On my host (Siteground) the solution was to turn off front end error reporting via .htaccess in both the main root directory and the admin directory.

Thanks for your help on this,

Hi, thanks for the update, I'm more than happy with the explanation, and am a massive fan of CMS Made Simple. The problem I have is that I can't upgrade to 2.20 on sites where my clients access the CMS as the error messages make it look like there's something wrong. php.ini doesn't stop these errors...

Various templates in the OneEleven admin still use "Count" and that is causing PHP Deprecated warnings. Templates I've found that have this issue: changeusergroup.tpl changegroupperm.tpl systeminfo.txt.tpl I've tried using php.ini to suppress these - that works on the front end but not in ...

Editing ErrorPage.inc.php as suggested by creopard

[edited by admin as core code changes should not be posted on the forum - use the bug tracker instead]
http://dev.cmsmadesimple.org/bug/view/12712

Resolves the issue of sites not loading where Content Type Error page is used.

Having installed V2.2.20 on a site originally built in 2.2.0 or thereabouts, it does not seem to be compatible with earlier template types or page types I have found the following: 1) Site will not load if the previous site had a default Error Page (Content Type = Error Page). Error seen: Parse erro...