Forums

Strict standards and C5 support errors

Permalink 1 user found helpful
Hi everybody! I'm trying to install concrete5 using xampp but when I try to go tohttp://localhost/concrete I have a red circle beside the "Support for C5 request URLs" voice: what should I do to repair this? Moreover above the "install concrete5" screen I have a huge amount of errors:

Strict Standards: Non-static method Loader::database() should not be called statically in /opt/lampp/htdocs/concrete/concrete/dispatcher.php on line 23
Strict Standards: Non-static method Loader::library() should not be called statically in /opt/lampp/htdocs/concrete/concrete/libraries/loader.php on line 177
Strict Standards: Non-static method Loader::library() should not be called statically in /opt/lampp/htdocs/concrete/concrete/libraries/loader.php on line 178
Strict Standards: Non-static method Loader::library() should not be called statically in /opt/lampp/htdocs/concrete/concrete/libraries/loader.php on line 179
Strict Standards: Non-static method Loader::library() should not be called statically in /opt/lampp/htdocs/concrete/concrete/libraries/loader.php on line 180
Strict Standards: Declaration of dbTable::create() should be compatible with that of dbObject::create() in /opt/lampp/htdocs/concrete/concrete/libraries/3rdparty/adodb/adodb-xmlschema03.inc.php on line 642
Strict Standards: Declaration of dbIndex::create() should be compatible with that of dbObject::create() in /opt/lampp/htdocs/concrete/concrete/libraries/3rdparty/adodb/adodb-xmlschema03.inc.php on line 806
Strict Standards: Declaration of dbData::create() should be compatible with that of dbObject::create() in /opt/lampp/htdocs/concrete/concrete/libraries/3rdparty/adodb/adodb-xmlschema03.inc.php on line 1051
Strict Standards: Declaration of dbQuerySet::create() should be compatible with that of dbObject::create() in /opt/lampp/htdocs/concrete/concrete/libraries/3rdparty/adodb/adodb-xmlschema03.inc.php on line 1302
Strict Standards: Non-static method Loader::library() should not be called statically in /opt/lampp/htdocs/concrete/concrete/libraries/loader.php on line 181
Strict Standards: Non-static method Loader::library() should not be called statically in /opt/lampp/htdocs/concrete/concrete/dispatcher.php on line 26
Strict Standards: Non-static method Cache::startup() should not be called statically in /opt/lampp/htdocs/concrete/concrete/dispatcher.php on line 27
Strict Standards: Non-static method Cache::getLibrary() should not be called statically in /opt/lampp/htdocs/concrete/concrete/libraries/cache.php on line 64
Strict Standards: Non-static method Loader::library() should not be called statically in /opt/lampp/htdocs/concrete/concrete/libraries/cache.php on line 28
Strict Standards: Non-static method Loader::library() should not be called statically in /opt/lampp/htdocs/concrete/concrete/dispatcher.php on line 30
Viewing 15 lines of 75 lines. View entire code block.

what can I do?
 
mkly replied on at Permalink Best Answer Reply
mkly
This was discussed in this post
http://www.concrete5.org/community/forums/installation/concrete5-in...

The tl;dr version
====================
You need to replace a line in your file C:\xampp\php\php.ini
error_reporting = E_ALL | E_STRICT

to
error_reporting = E_ALL & ~(E_NOTICE | E_STRICT | E_DEPRECATED)
illukino90 replied on at Permalink Reply
Thank you so much, it works!!
siteadvice replied on at Permalink Reply
siteadvice
I've just had to move a couple of Concrete5 sites running v5.4.X and I had a lot of trouble with this.

The supposed fix reported by several people on the forums (adding the error_reporting setting to a php.ini file in the site root) does not solve the problem because error_reporting is reset numerous times in the core Concrete5 code itself.

The solution for me was to search through the \concrete\ folder and find instances of

error_reporting(E_ALL ^ E_NOTICE ^ E_DEPRECATED)

or

error_reporting(E_ALL ^ E_NOTICE)

(for example in concrete\startup\debug_logging.php and concrete\controllers\upgrade.php)

and change them to the following:

error_reporting(E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE)

This got my sites running again.
Tromholt replied on at Permalink Reply
Tromholt
Hey Jon Ewing
I got the same problem / challenge with this "Strict standards . . . " and reporting errors.

You wrote that you searched through the folder Concrete folder for instancex of "error_reporting(E_ALL ^ E_NOTICE ^ E_DEPRECATED)" or "error_reporting(E_ALL ^ E_NOTICE)" and replaced them with "error_reporting(E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE)".
How did you do that search ?
I have dreamweaver 6 (the newest before CC) and I can't figure out how I can search all the files automatic, - like in Windows 7 explorer.
I want to use a function like "search and replace".
Otherwise I have to go through every single file, as far as I understand - or is it only a couple of files?
Should I open them step by step and use "search and replace ?
I hope you can help me - I got "only" two sites running with that problem.

Hey Jon
Once again.
I have to tell you how I use Concrete5:
I don't use Xampp - as I said - I use Dreamweaver 6, but use the web for changing design and text, does normaly NOT use Dreamweaver for editing the site.
So PHP is installed on the server, - and my problem started when they updated PHP to version 5.6. - It works with version 5.3
The concrete5 version i 5.5.1
In my directory i don't have a php.ini - i think its only on the webhotels server because it belongs to PHP system.

So - is your solution still to change these instances ?

Thanks for your writing in the Concrete Forum
Ib Tromholt
WebcentricLtd replied on at Permalink Reply
I wouldn't normally suggest this but won't changing the error reporting in just dispatcher.php work?