Support Forum

XAMPP 1.8.0 and db problems

DH Dietmar Herian
Dietmar Herian
Member

Hi Sp team,

since a couple of days, the XAMPP for Linux version 1.8.0 came out. It contains Apache 2.4.2 and PHP5.4.4 and MySQL 5.5.25a. And this is where my trouble starts, I guess.

After upgrading to XAMPP 1.8.0 – which btw ran seemless without any errors –  there still was an MySQL database upgrade to run . Doing so, immediately threw a number of errors to the display of my forum, PM side and SP admin side. Here they are :

Admin page

Warning: Creating default object from empty value in /opt/lampp/problem-with-post-edit-buttontdocs/wp-content/plugins/simple-press/forum/content/sp-common-view-functions.php on line 413

Forum page

Warning: Creating default object from empty value in /opt/lampp/problem-with-post-edit-buttontdocs/wp-content/plugins/simple-press/forum/content/sp-common-view-functions.php on line 413

Warning: Creating default object from empty value in /opt/lampp/problem-with-post-edit-buttontdocs/wp-content/plugins/simple-press/forum/content/classes/sp-group-view-class.php on line 268

Warning: Creating default object from empty value in /opt/lampp/problem-with-post-edit-buttontdocs/wp-content/plugins/simple-press/forum/content/classes/sp-group-view-class.php on line 314

Warning: Creating default object from empty value in /opt/lampp/problem-with-post-edit-buttontdocs/wp-content/plugins/simple-press/forum/content/classes/sp-list-topic-class.php on line 193

PM page

Warning: Creating default object from empty value in /opt/lampp/problem-with-post-edit-buttontdocs/wp-content/plugins/simple-press/forum/content/sp-common-view-functions.php on line 413

Warning: Creating default object from empty value in /opt/lampp/problem-with-post-edit-buttontdocs/wp-content/sp-resources/forum-plugins/private-messaging/library/sp-pm-database.php on line 166

It all seems to be related to group-ID or forum-ID. If you look into the database tables, they do not look corrupted or so. Maybe, a format issue?

Are there any known issues with MySQL 5.5.25a or PHP5.4.4 ?

Any help available for this?

3 Answers

New Answer

MP Mr Papa
Mr Papa
Member

turn off strict error checking in php…  its not any kind of issue… strict error checking does not make sense for production environment anyways…  strict error checking is an annoyance of the php that they added…

we have opened a ticket to put in some checks for this junk, but its going to take some time to put in place – significant effort for no gain… :(

DH Dietmar Herian
Dietmar Herian
Member

Thanks! This helped.

The upgrade seems to revert the error_reporting variable back to ‘E_ALL | E_STRICT’ and display_errors to ‘on’.

There is always some surprise hidden in these upgrades.

YS Yellow Swordfish
Yellow Swordfish
Member

we have come across this. It seems very heavy handed to set up strict error checking.