Support Forum
Mr Papa said
No, this would be an advanced topic... sorry, thought I mentioned it, easiest way would be to inquire with your host... if you have access to a phpinfo() display, that could give it to you as well...still researching this as well since not convinced that is the issue... but the error is actually occurring in a wp function (their db connection code)... and its not obvious how its triggered.. only these two reports and I cannot duplicate it... and wp support forum have fair number of similar reports but no common thread...
would it be possible to temp disable all other plugins and see if it still occurs?
Already tried that and it still happens.
well, tomorrow is weekend and plan to research further... but bit stymied what would be causing this on two sites... and in a wp function no less...
Visit Cruise Talk Central and Mr Papa's World
can you guys give me a link to where this is happening so I can see where the error is occurring in relation to the rest of the page display? @howtonetwork yours is behind paywall...
It appears the only way this can happen is when the WP global $wpdb does not exist - or correctly is not yet set up... wouldnt have expected that in the footer, but perhaps something else is doing some sort of ajax response...
can you both verify on forum - integration - page and permalink that you have 'limit forum display to within wp loop' set true and 'allow multiple loading of forum content' set false?
If so, then try checking 'force strict use of the WP API' and see if any difference...
Visit Cruise Talk Central and Mr Papa's World
The error for me only appears in my error logs, I guess he has debug set to true in wp-config.php so that might be when he actually sees the error.
Limit forum to display to within WP loop was not checked (is now)
Force the strict use of WP API was not checked (is now)
Allow multiple loading of forum was not checked and is still not checked
and I assume, no change? didnt really expect so, but was hoping... is one case where the $wpdb object would not be valid...
you might also have display errors turned off in your php ini like one really should for production sites...
still looking, but a bit stymied how the $wpdb object wouldnt exist..
Visit Cruise Talk Central and Mr Papa's World
I am still at a loss as to what is going on here... and why just the two of you are having this issue...
upon further research, this check connection is only used when we are trying to generate an error and log it.. so we are definitely in a some odd state here...
For now, to remove the error, I would suggest going to forum - options - global settings and disable logging... that should at least remove the error...
also, any errors displayed on forum - toolbox - error log?
Visit Cruise Talk Central and Mr Papa's World
I haven't had the connection error today, but I have had the following:
[04-Oct-2015 16:08:35 UTC] PHP Warning - Creating default object from empty value - file: /simple-press/sp-startup/site/sp-site-support-functions.php - line: 686 - function: sp_check_for_updates
[04-Oct-2015 16:08:35 UTC] PHP Warning: Creating default object from empty value in /home/HOSTACCOUNT/public_html/wp-content/plugins/simple-press/sp-startup/site/sp-site-support-functions.php on line 686
[04-Oct-2015 16:08:35 UTC] PHP Warning - Creating default object from empty value - file: /simple-press/sp-startup/site/sp-site-support-functions.php - line: 686 - function: spHandleShutdown
nah, those are harmless notices (not errors) and unrelated... in fact, those three have already been dealt with in the next version...
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)