Update bad news 🙁

Error is still present, the 22 entries in the log for 24th May corresponds with the number of individual visitors,  each visitor using light-blue overlay is creating an entry – no other overlay is creating the error (so far).

24th May – 22 entries of the error in /wp-content/sp-resources/forum-themes/reboot/styles/error.log – No errors in dashboard >forum>toolbox >error log.

[24-May-2015 21:16:04 UTC] PHP Warning:  include(): Failed opening ‘/problem-with-post-edit-buttonome/mysite/public_html/wp-content/sp-resources/forum-themes/reboot/styles/../..//styles/overlays/.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /problem-with-post-edit-buttonome/mysite/public_html/wp-content/sp-resources/forum-themes/reboot/styles/reboot.php on line 25

[25-May-2015 00:25:23 UTC] PHP Warning:  include(/problem-with-post-edit-buttonome/mysite/public_html/wp-content/sp-resources/forum-themes/reboot/styles/../..//styles/overlays/light-blue.php): failed to open stream: No such file or directory in /problem-with-post-edit-buttonome/mysite/public_html/wp-content/sp-resources/forum-themes/reboot/styles/reboot.php on line 25

sorry, can you explain what you mean by users and different overlays?  which overlay do you have selected?  how would users have a different overlay?  are you using the Language and Theme Selection plugin?  If so, what version please since a version was released a while back to fix the missing $_GET[‘theme’] variable…

Version 1.3.1 Language and Theme Selection

default theme overlay is light-blue which most users have chosen/stuck with anyway

hmmm… okay, thanks… right now, I am unable to replicate the warning…  probably need Ike to take a look…

Can we see if we can establish some more data surrounding this issue?

If this error happened on every page load for all users then (a) the error log would show higher numbers and (b) no users would ever see a properly formatted forum display. There does not seem to be any intimation on this thread that either of those conditions is really the case – thus suggesting that the condition is intermittent or, perhaps in some way, limited to a specific user. And I think we need to try and work towards pinning down the conditions under which the error occurs.

So – could we start by clearing the decks?

1. First – if the CSS caching is turned on (forum admin > options > global settings) could it be turned off.
2. Clear the error log (forum admin > toolbox > error log).
3. Deactivate the Language and Theme Selection plugin. This action might need explaining to users of course.

If you have a statistics plugin active then note the page loads. Then watch the site for a day to see if the error occurs. The error count in conjunction with page loads will give an indication of the scope of the error but that is more as something useful – not required so if no stats active then we can ignore that.

I guess finally I have to ask if any user or users have actively reported a forum display issue? If there any way they could be asked?

This is the get routine at line 25 of reboot.php from that site.

# load the selected color overlay stylesheet $overlay = dirname(__FILE__).'/../../'.$_GET['theme'].'/styles/overlays/'.$_GET['overlay'].'.php'; include($overlay);

I must add I can’t replicate the error on my dev server.

Which is as it should be.

Are you able to implement my proposals?

css caching is off, all error logs cleared within the gui and in the folders on the server.

I can’t turn off the themes & languages just yet, they’ll have a fit, I’ll spring that one on them overnight.

Stats are showing some old browsers being used, I’ll have to keep an eye on it.

Could do with a flush sessions button.

Ann said
Could do with a flush sessions button.

Would you like to expand on that?

flush all user sessions to force log out

i am not totally sure you could do that with WordPress although I guess there might be a plugin out there that could do it. A users cookie will still be on their local PC though…

There is a routine to flush the sessions table and a script to remove site cookies, I’ll see if I can make a widget/ plugin

let us know… btw, wp doesnt really do sessions in the traditional sense…  what you probably want to do is call

which essentially will force a user to log in…

Back to the ongoing error. Tests done following your requests with plug-ins disabled.

The error has manifested in 2 ways now, one is for the light-blue overlay, while the other is basically the url coding in line 25 of reboot.php. I’ve checked the site stats and several users are using outdated browsers. One guy in particular has been moaning about the fact he doesn’t like the new layout but I have a feeling this is the person that is the root of the error. I haven’t managed to catch him online today but I will endeavour to have a chat with him and send him some screen shots of what the layout actually looks like. I don’t think this error is down to your coding at all, I see this as a localised issue that I need to resolve myself.

URL error – without a specific file name

[27-May-2015 20:03:15 UTC] PHP Warning:  include(): Failed opening '/problem-with-post-edit-buttonome/mysite/public_html/wp-content/sp-resources/forum-themes/reboot/styles/../..//styles/overlays/.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /problem-with-post-edit-buttonome/mysite/public_html/wp-content/sp-resources/forum-themes/reboot/styles/reboot.php on line 25

Below is the previous error, calling light-blue overlay and not locating it. 

[27-May-2015 21:25:16 UTC] PHP Warning:  include(/problem-with-post-edit-buttonome/mysite/public_html/wp-content/sp-resources/forum-themes/reboot/styles/../..//styles/overlays/light-blue.php): failed to open stream: No such file or directory in /problem-with-post-edit-buttonome/mysite/public_html/wp-content/sp-resources/forum-themes/reboot/styles/reboot.php on line 25

Even the syntax highlighter is throwing a wobbly at the error coding lol

dont understand the syntax highlighter comment…

but both are the same thing…  the theme name is missing from the url… I am struggling with how its missing as we cannot duplicate that…

Andy was postulating it might be a blocked cookie issue on specific users…