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 said
…we do give you the option not to log them at all.

And Interestingly, I have Notices turned off yet they are still logged…

…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

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…

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!

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…

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?

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?

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…

Mr Papa said
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?

Perhaps you mean the notice I copied and pasted in post 7 above? My only other image above has a count of 380. The most recent count after clearing the log more than an hour ago is back up to 14…

27 June 2015 4:46 pm | spaErrNotice | 14 | php

file: /simple-press/sp-control.php
line: 98
function: sp_is_forum_page
Notice | Trying to get property of non-object

So the count is increasing, but nowhere near the increments expected if this was occurring upon every page load. 

And perhaps unrelated, but there is this new similar notice for a different function.

27 June 2015 3:57 pm | spaErrNotice | 7 | php

file: /simple-press/sp-startup/forum/sp-forum-constants.php
line: 26
function: include_once
Notice | Trying to get property of non-object

yes, your option should disable our logging of them… quite odd that it doesnt – will open ticket for investigation…

Thanks! And here I thought I was just starting a simple topic where users could report insignificant notices…

of course I noticed the 380 – which is why I mentioned age..  and why I asked for it to be cleared and enumerated as pages were loaded…  and if it increased for every page load…

thanks for the update…  doesnt help understand how the wp page id would not exist though 🙂

have to wonder if some other plugin or widget is loading the forum content where perhaps it doesnt exist but doesnt display the content…  still would think not a problem…

could give an easy check before the usage to make sure it doesnt exist, but since it seems it must, would just slow down the page processing (every so slowly)…  so we want to understand before just perhaps covering up something else…

after doing some research, it appears the name of that option is a bit misleading…  both the option name and the admin popup help appear to indicate all simple press notices would be hidden…

but in actuality, only notices of undefined index/variable will be suppressed…  in this case, the notice is for trying to get property of non object… so its not suppressed…

will discuss around here if we want to broaden the suppression or clean up the option name/problem-with-post-edit-buttonelp so its more clear…

Mr Papa said
could give an easy check before the usage…would just slow down the page processing…

Well we wouldn’t want that!

This doesn’t seem to have any adverse affect that I can tell, so I can live with it while looking further into any sort of conflict.

only notices of undefined index/variable will be suppressed… 

Thanks for the clarification!

Despite the fact that I have never seen this particular notice anywhere else and suspect – like Steve – that it is in all likelihood not being triggered on normal forum page loads as the count would be way, way higher and would climb quickly – I do support putting a check in place. Steve is correct that a check would be another stage in processing but – when the error does get triggered there is also the reporting and writing out of the condition that should be considered – a longer process.

Additionally – if we are correct and this is the result of, say, some sort of bot activity – and I do not mean by that something hostile – then killing the load process at that point if the data is not loaded would seem a more appropriate action.

But let’s get some input and agreement on that from Steve before progressing…