Error on step 5 of setup

[kunashe]

I get the following response on step 5 of setup. However, in a separate tab, I can log into cmcm & work.

Response could not be resolved:
Strict Standards: Non-static method Login::pretty_print() should not be called statically in C:\Users...\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Login.class.php on line 287

Strict Standards: Non-static method Jdat::pretty_print() should not be called statically in C:\Users...\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Jdat.class.php on line 340

Strict Standards: Non-static method Jdat::pretty_print() should not be called statically in C:\Users...\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Jdat.class.php on line 340

[cjm771]

Ah I'll have to check with that. Your server must have error reporting as E_STRICT.I have been using E_ALL for error_reporting on my server. I'll have to debug using E_STRICT on the server.

If your self hosted, As a temp fix, change php.ini line, error_reportting to E_ALL.
If it's shared (which it doesn't look like it), then put a php.ini in your site directory with one line:
error_reporting = E_ALL

let me know if your getting this or other bugs. cheers.

-chris

On May 3, 2014, at 2:24 PM, kunashe [email protected] wrote:

I get the following response on step 5 of setup. However, in a separate tab, I can log into cmcm & work.

Response could not be resolved:
Strict Standards: Non-static method Login::pretty_print() should not be called statically in C:\Users\Kunashe\Documents\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Login.class.php on line 287

Strict Standards: Non-static method Jdat::pretty_print() should not be called statically in C:\Users\Kunashe\Documents\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Jdat.class.php on line 340

Strict Standards: Non-static method Jdat::pretty_print() should not be called statically in C:\Users\Kunashe\Documents\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Jdat.class.php on line 340

—
Reply to this email directly or view it on GitHub.

[kunashe]

Hey,

Changing the error reporting level to E_ALL & ~E_NOTICE & ~E_STRICT disabled the notification.

I am running php 5.4.7 on a local xampp 3.1 installation.

Ku

From: cjm771
Sent: ‎Sunday‎, ‎4‎ ‎May‎ ‎2014 ‎04‎:‎29
To: cjm771/cmcm
Cc: Kunashe

Ah I'll have to check with that. I have been using E_ALL for error_reporting on my server. I'll have to debug using E_STRICT on the server.

What hosting are you using? If your self hosted, As a temp fix, change php.ini line, error_reportting to E_ALL.
If it's shared, then put a php.ini in your site directory with one line:
error_reporting = E_ALL

let me know if your getting this or other bugs. cheers.

-chris

On May 3, 2014, at 2:24 PM, kunashe [email protected] wrote:

I get the following response on step 5 of setup. However, in a separate tab, I can log into cmcm & work.

Response could not be resolved:
Strict Standards: Non-static method Login::pretty_print() should not be called statically in C:\Users\Kunashe\Documents\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Login.class.php on line 287

Strict Standards: Non-static method Jdat::pretty_print() should not be called statically in C:\Users\Kunashe\Documents\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Jdat.class.php on line 340

Strict Standards: Non-static method Jdat::pretty_print() should not be called statically in C:\Users\Kunashe\Documents\work_in_progress\local\cmcm-demo\cmcm\assets\php\lib\Jdat.class.php on line 340

—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.