Support Forum
Toolbox - Error Log
Strict: ...please inform Simple:Press support so we can deal with them.
Notice: ...We make every effort to clear these when we are informed of them.
Warning: ...suggest a code conflict of some type that should be investigated.
Error: ...should be reported to Simple:Press support
I expect most users would start a new topic to discuss any errors affecting forum behavior, but I couldn't find a specific place to report general Notices and Warnings. Perhaps we could use this topic.
So I'll start—just noticed the entries below.
No need to reply, unless there is any cause for concern or action required on my part.
Thanks, for the continued great work and support!
25 June 2015 10:05 am | spaErrWarning | 8 | php
file: ipawds/public_html/wp-content/sp-resources/forum-plugins/admin-bar/library/sp-admin-bar-components.php
line: 542
function: sp_AdminBarDashboardPosts
Warning | Invalid argument supplied for foreach()
25 June 2015 4:28 am | spaErrNotice | 4 | php
file: /simple-press/sp-startup/site/sp-site-support-functions.php
line: 242
function: sp_feed
Notice | Trying to get property of non-object
25 June 2015 4:23 pm | spaErrNotice | 141 | php
file: /simple-press/sp-control.php
line: 98
function: sp_is_forum_page
Notice | Trying to get property of non-object
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
As we have said many times - these tend to be harmless nuisances but we do appreciate that they ARE a nuisance. Which is why we do give you the option not to log them at all.
Having said that - we DO take note of them and try and clean up the causes when we can and if we can find the cause. More often than not they are caused by a feature that was added in an update of SP but where the admin panel has never been visited by the user and the initial data set up. We do try and remember to set up default data but sometimes we do just miss it.
A lot can often be caused by bots and nuisance users trying to spam post your website. I am actually quite proud of the work I put in a couple of updates back to reduce the overhead of this and also the notices that these attempts sometimes spawn.
The main thing to watch for if you DO log the notices - are repeated occurrences. That number on the same line as the date and time shows how many times that notice has been issued and of that starts to climb dramatically then it is worth sorting out. We clear ours and then just keep watch. Needless to say we donlt see any of the above but then this is the problem - everyones notices are different!
YELLOW
SWORDFISH
|
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
...watch for...repeated occurrences. That number on the same line as the date and time shows how many times that notice has been issued and of that starts to climb dramatically then it is worth sorting out.
And thanks for pointing this out!
So, perhaps 380 occurrences of this one needs some looking into. How might I start to sort that out?
27 June 2015 1:03 pm | spaErrNotice | 380 | php
file: /simple-press/sp-control.php
line: 98
function: sp_is_forum_page
Notice | Trying to get property of non-object
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
interesting... not sure I understand why that would be... generally, its not occurring... it seem to indicate you are on a wp page, but the page has no ID... which does not compute at the moment for me...
can you narrow down when its occurring? every forum page? specific ones? other wp pages/posts?
and how old are the 380? perhaps clear the log and see how fast they build up and answer the first question...
Visit Cruise Talk Central and Mr Papa's World
Mr Papa said
interesting... how old are the 380?
As recent as today, according to the date.
Cleared the log and haven't replicated it yet but will keep an eye on things.
Welcome back!
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
So as soon as I posted Here, I checked my log and got this again...after I had viewed the main Forums page, a forum, a topic, and then posting in the topic. (checking log in between each action with no result)
27 June 2015 1:46 pm | spaErrNotice | 1 | php
file: /simple-press/sp-control.php
line: 98
function: sp_is_forum_page
Notice | Trying to get property of non-object
Clearly anything anyone else might have been doing could have caused it to I presume...
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
As y'all have said many time before though, this may merely be a nuisance. Any idea why my notices would still get logged if I have the option checked not to do so? Or am I misunderstanding that option in my screen shot above?
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Let's do the notice first which is just about the most bizarre notice I have seen and really suggests that every load of the forum page should result in a 404. Actually - it is saying that WordPress is not finding the forum page which is clearly bunk.
Would you agree with that @mr-papa? Any idea anyone why the $wp_query object would be empty?
YELLOW
SWORDFISH
|
not convinced its the $wp_query empty, but perhaps the post object of that object... but effect is the same as I mentioned - on a wp page but it has no page id...
but to be clear, your image has a count of 1... if it was every page, should have been more... can you verify the count increments for every page and the image was not matching your words?
yes, your option should disable our logging of them... quite odd that it doesnt - will open ticket for investigation...
Visit Cruise Talk Central and Mr Papa's World
1 Guest(s)