Support Forum

Bug – Dashboard crash on fresh install

CU cubehouse
cubehouse
Member
Member since Jul 2011
34 posts
Jul 4, 2011 · 12:09 pm · Edited

Found this on two of my WordPress installations (one running current stable and one running bleeding-edge WordPress).

After activating, Dashboard would return error 500. Turned on debugging in PHP and found this error repeated around 82 times before running out of memory and dying:

Notice: Trying to get property of non-object in /var/www/vhosts/blahblah/problem-with-post-edit-buttonttpdocs/blog/wp-content/plugins/simple-press/sp-api/sp-api-primitives.php on line 761

 

I “fixed” this by checking for “if ((isset($spThisUser))&&(isset($spThisUser->tracki)))”, but I’m not entirely sure where $spThisUser comes from, so haven’t looked into working out why it isn’t initialised.

This was a clean installation on these blogs, can’t 100% confirm that was the reason for the crash tho.

13 Answers

New Answer
MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Jul 4, 2011 · 1:32 pm

not sure why that would cause anything to die or crash…

we have not done a thorough sweep yet with debug on to fix all the notices but certainly will before release…

will get a ticket open on this one…

$spThisUser is an object containing wp current user info plus sp specific info…  possible this is pre setup of it as you indicate…

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Jul 4, 2011 · 2:39 pm

Andy committed a fix for this too…  would be interested to know if it helped you too…

CU cubehouse
cubehouse
Member
Member since Jul 2011
34 posts
Jul 4, 2011 · 2:54 pm

Unfortunately not.

Still get:

Notice: Trying to get property of non-object in /var/www/vhosts/blahblah/problem-with-post-edit-buttonttpdocs/wp-content/plugins/simple-press/sp-api/sp-api-primitives.php on line 761

many many many times until it runs our of PHP memory

CU cubehouse
cubehouse
Member
Member since Jul 2011
34 posts
Jul 4, 2011 · 2:59 pm

Should add, it all works fine on my other website once the forum is installed (that other installation had this error before I haxed it). Seems to happen after activating the plugin but before running the actual forum installation.

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Jul 4, 2011 · 3:26 pm

okay thanks for update. will pass to andy.

CU cubehouse
cubehouse
Member
Member since Jul 2011
34 posts
Jul 5, 2011 · 8:44 am

Spotted a few SVN commits today, just ran a fresh install on the blog that was previously throwing a wobbly – now appears to be functioning correctly on all the test cases I have running 🙂

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Jul 5, 2011 · 9:40 am

cool. we actually had forgotten to run through install and upgrade with debug on… had done pass through front end and fixed maybe 90% before opened alpha… andy has been going through install and upgrade to fix up those notices too…

thanks for update…

DE devjah
devjah
Member
Member since Jul 2011
3 posts
Jul 5, 2011 · 7:09 pm

died 2 times on fresh installation, successfully installed on third try.

DE devjah
devjah
Member
Member since Jul 2011
3 posts
Jul 7, 2011 · 12:15 pm

Mr Papa said:

any clue on the first two? error log?

readdir() expects parameter 1 to be resource, boolean given in rootwp-contentpluginssimple-presssp-startupinstallsp-upgrade-support.php on line 96, referer: root/wp-admin/admin.php?page=simple-press/sp-startup/sp-load-install.php

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Jul 7, 2011 · 12:19 pm

what did you do differently on third install?  did you create the dir?  was that a critical error?

DE devjah
devjah
Member
Member since Jul 2011
3 posts
Jul 8, 2011 · 4:24 pm

Mr Papa said:

what did you do differently on third install?  did you create the dir?  was that a critical error?

I did nothing different, it just installed on third try. that is a warning, not an error. I don’t get what was the problem.. Hope it was only me.

MP Mr Papa
Mr Papa
Member
Member since Dec 2006
19,448 posts
Jul 8, 2011 · 6:06 pm

so far… but pretty small sample size…  thats the worrying part…