Update & Activating 1.4.7 causes Fatal Error

@cpkn – Hmm that is way to generic for us to even know where to look. Any chance you can follow this guide and get a stacktrace pointing us in the right direction?

https://www.barrykooij.com/white-screen-wordpress/

This is the first report of this so please bear with me and we will get it worked out.

Hello,

Thanks for the reply.

Not a problem! ??

I will get it done ASAP!

Cheers!

@cpkn – Awesome, I am off for the night (4:30am here) so I will take a look first thing and hopefully there is enough info that I can patch tomorrow for you without any extra back and forth :).

Hello,

So had a bit of a bump getting the code to work, but then I thought I had it until I new error came up:

Fatal error: Call to undefined function nocache_headers() in …/wp-admin/admin.php on line 33

Line 33 is literally

nocache_headers()

Dunno why this affects it when adding the code but otherwise is fine?

I will try again when I can later today/tonight (currently 12:30pm), if you have any ideas on what I have done wrong, let me know.

I will keep you posted.

Note: I can remove the line of code in query.php to get my website running without WSOD, but as I am not pro with this sort of thing, I don’t know if that would be bad to keep out for the long term.

@cpkn – Probably don’t want to do that long term :).

Also thus far nothing points to any issues in popup maker other than it occurs when active, at this point without more info from somewhere its basically needle in a field of haystacks.

I have a few others reporting similar, so its not just you, hopefully we can get more details somewhere in the mix.

Hey,

I haven’t had any luck in getting the Stacktrace to work.

There is a few more things I can try but busy times are getting in the way.

I hope the other reports can help you with this issue.

I will keep you posted on getting the trace.

Sorry for the delay.

Cheers!

@cpkn – So far all reports have been resolved by the last few updates. Can you try disabling other plugins and then enabling popup maker, then turn the others back on one at a time until it breaks again. It has to be a plugin conflict of sorts.

Hello,

Yes, I see you made some updates… Awesome!. I will see if its ok with the latest.

As far as the plugin conflict, I will check what you said about activating and see and update you, if the latest update does not work of course.

Thanks!

Hello,

I am finally back!

So some good news, and bad news ??

Good News – When updating to latest update, the fatal error did not appear.

Bad News – A message popup from your plugin asked for me to update the database. It went through rebuilding data, pop up targeting conditions etc. As soon as it did it, the fatal error appeared.

Good News – It does not kill the whole site, it has fatal error when trying to access the plugin settings.

More Good News – I figured out how to get the WP Debug to work and I have more info now. It looks like it could definitely be a plugin conflict, but when I deactivate the mentioned plugin, it doesn’t fix the error:

Strict Standards: Declaration of c2c_ConfigureSMTP::options_page_description() should be compatible with C2C_Plugin_023::options_page_description($localized_heading_text = ”) in …/plugins/configure-smtp/configure-smtp.php on line 47

Fatal error: Call to a member function get() on null in …/wp-includes/query.php on line 27

Notice: is_home was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in …/wp-includes/functions.php on line 3622

Notice: is_front_page was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.) in …/wp-includes/functions.php on line 3622

Not sure what you can make of it.

I did also try the backtrace again, I think I got it to work, this is what I got:

Backtrace from warning ‘Declaration of c2c_ConfigureSMTP::options_page_description() should be compatible with C2C_Plugin_023::options_page_description($localized_heading_text = ”)’ at …/wp-content/plugins/configure-smtp/configure-smtp.php 47:
1. …/wp-settings.php 215 calling include_once()
2. …/wp-config.php 236 calling require_once()
3. …/wp-load.php 37 calling require_once()
4. …/wp-admin/admin.php 31 calling require_once()
5. …/wp-admin/edit.php 10 calling require_once()

Fatal error: Call to a member function get() on null in …/wp-includes/query.php on line 27

Backtrace from warning ‘is_home was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.)’ at …/wp-includes/functions.php 3622:
1. …/wp-includes/functions.php 3622 calling trigger_error()
2. …/wp-includes/query.php 447 calling _doing_it_wrong()
3. …/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/nxs_functions.php 1140 calling is_home()
4. calling nxs_psCron()
5. …/wp-includes/plugin.php 503 calling call_user_func_array()
6. …/wp-includes/load.php 611 calling do_action()
7. calling shutdown_action_hook()

Backtrace from warning ‘is_front_page was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.)’ at …/wp-includes/functions.php 3622:
1. …/wp-includes/functions.php 3622 calling trigger_error()
2. …/wp-includes/query.php 418 calling _doing_it_wrong()
3. …/wp-content/plugins/social-networks-auto-poster-facebook-twitter-g/nxs_functions.php 1140 calling is_front_page()
4. calling nxs_psCron()
5. …/wp-includes/plugin.php 503 calling call_user_func_array()
6. …/wp-includes/load.php 611 calling do_action()
7. calling shutdown_action_hook()

Well I hope this is what you are looking for and helps!

Chris

Hello – I was also experiencing this issue with the plugin after updating.

I was only getting the error when trying to create or view posts (of any post type).

It was originally showing as a error 500 but logs showed the same error message as @cpkn

I’ve deactivated until patch.

@cpkn – Did you disable both offending plugins? IE social-networks-auto-poster-facebook-twitter-g & configure-smtp?

@mrcarllister – The errors he listed are generated in other plugins, disabling Popup Maker should have no effect really. The problem is those plugins are doing stuff they shouldn’t for @CPKNs site on popup editor pages making it so he can’t update them. Sounds like yours is different and likely warrants a new ticket, also see previous posts about getting the error logs as they are the only way to really know what is causing the problem. You can also test by leaving Popup Maker enabled then disabling other plugins 1 by 1 until the problem goes away, if it remains then its likely in your theme. There are 0 active errors in the plugin with a fresh install and typical theme / plugins, so it is likely a conflict with a plugin that is not as popular.

Hope that helps.

Hello,

I didn’t see it show 2 different plugins. whoops!

I will disable both and try again.

If it helps, what is the next step for me? do you know the specific issues for me to get the other plugin devs to help, or do you have something that could help? Especially since the current version I have has no issues (1.3.9).

I will hopefully get an update within 24hrs on here.

@mrcarllister Sorry to hear you have issues. Please do create a new ticket with @danieliser so you can get it solved.

The error logging can be tricky if you don’t know much about changing code in WP files, FTP and if there is another underlining issue like I had the first time.

Best of luck.

@danieliser – thanks for the reply. I’ll create a new ticket soon!