White screen on activation version 4.0.1

Can you look what the PHP error shows? A white screen would suggest some problem on a basic level. Ig you have got PHP opcache running, has it been refreshed since the update?

Thank you for replying. The site is actually on AWS, running ubuntu/ngnix. I was able to dig into the error logs and found out that there’s a conflict with your plugin and another one I am using on the client’s site called “WP RSS Aggregator”. That plugin has an add-on called “WP RSS Aggregator – Feed to Post” which takes content from an RSS feed and creates Posts.

According to the error log snippet below, it doesn’t like the fact that I am running that, plus the “Media Credit” plugin, as well as the “Classic Editor” plugin.

The client requires the other two plugins (Classic Editor and WP RSS Aggregator – Feed to Post). All three worked fine together before the Media Credit version 4.x update so not sure what changed.

Anyway, this is FYI for you and others that may run into this, as it’s clearly an edge case. Not sure what I can do in the meantime.

Error log snippet:

2019/03/14 12:28:17 [error] 12178#12178: *34022108 FastCGI sent in stderr: “PHP message: PHP Fatal error: Uncaught Error: Call to undefined function get_current_screen() in /var/www/site/wp-content/plugins/wp-rss-feed-to-post/includes/wprss-ftp-meta.php:70
Stack trace:
#0 /var/www/site/wp-includes/class-wp-hook.php(286): WPRSS_FTP_Meta->disable_visual_editor(true)
#1 /var/www/site/wp-includes/plugin.php(208): WP_Hook->apply_filters(true, Array)
#2 /var/www/site/wp-includes/general-template.php(3123): apply_filters(‘user_can_riched…’, true)
#3 /var/www/site/wp-content/plugins/media-credit/includes/media-credit/components/class-classic-editor.php(93): user_can_richedit()
#4 /var/www/site/wp-includes/class-wp-hook.php(286): Media_Credit\Components\Classic_Editor->initialize_editor_integration(”)
#5 /var/www/site/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
#6 /var/www/site/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
#7 /var/www/site/wp-settings.php(505): do_action(‘init’)
#8 /var/www/site/wp-config.php(91): require_once(‘/var/www/site/w…’)” while reading response header from upstream, client: 66.249.66.211, server: 13.58.18.0, request: “POST /wp-admin/admin-ajax.php?action=acc_get_banners HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9000”, host: “thejewishnews.com”, referrer: “https://13.58.18.0/2012/07/05/greener-than-green/”

• This reply was modified 5 years, 11 months ago by Jeff Mackey.

Hi @jsmackey, it looks like the error occurs in WPRSS_FTP_Meta::disable_visual_editor. That seems to be part of the commercial WP RSS Aggregator – Feed to Post plugin. As I don’t have the source code available, I can’t say for sure, but it looks like it incorrectly assumes that can_user_richedit will only ever be called on the full backend and not on the frontend or in an AJAX call and so does not include the proper source file for making get_current_screen available.

The issue might be triggered by a change in Media Credit’s initialization sequence, but I don’t think it is a bug in Media Credit.

Again, thanks for replying. I will continue to dig to see if I can find a solution somehow.

I’ve had a look at the code in question: calling user_can_richedit (which is located in wp-includes/general-template.php) on the init hook is, as far as I can see, a perfectly valid way to fence in some additional hook linkups.

WP RSS Aggregator – Feed to Post hooks into the eponymous user_can_richedit hook in an attempt to disable the visual editor. Unfortunately, it assumes this filter won’t be called from anywhere but the admin backend. For what reason etc., I can’t say. But since this is a commercial plugin, there should be some support venue.

Please post here to let us know if you get an answer from them! (Though in the meantime I’ll mark this thread as resolved since this really is an issue in another plugin.)

Peter — thanks! Yes, I plan on reaching out to the RSS Aggregator folks.

Yep, I forgot to toggle the support request ‘closed’ on my last reply.