Broken site after the update on 11 July 2020

  • Resolved steeldrum44

    (@steeldrum44)


    4 years, 4 months ago

    Fatal error: Uncaught Error: Call to a member function replaceChild() on null in /data/web/virtuals/162588/virtual/www/domains/…/wp-content/plugins/wordpress-popular-posts/src/Front/Front.php:141 Stack trace: #0 /data/web/virtuals/162588/virtual/www/domains/…/wp-includes/class-wp-hook.php(287): WordPressPopularPosts\Front\Front->convert_inline_js_into_json(‘<script type=’t…’, ‘wpp-js’, ‘https://…&#8217;) #1 /data/web/virtuals/162588/virtual/www/domains/…/wp-includes/plugin.php(206): WP_Hook->apply_filters(‘<script type=’t…’, Array) #2 /data/web/virtuals/162588/virtual/www/domains/…/wp-includes/class.wp-scripts.php(400): apply_filters(‘script_loader_t…’, ‘<script type=’t…’, ‘wpp-js’, ‘https://…&#8217;) #3 /data/web/virtuals/162588/virtual/www/domains/…/wp-includes/class.wp-dependencies.php(116): WP_Scripts->do_item(‘wpp-js’, 0) #4 /data/web/virtuals/162588/virtual/www/domains/…/wp-includes/class.wp-scri in /data/web/virtuals/162588/virtual/www/domains/…/wp-content/plugins/wordpress-popular-posts/src/Front/Front.php on line 141

    I had to deactivate the plugin to restore website and get in working

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Hector Cabrera

    (@hcabrera)

    Yep, already reported here. Please follow steps 1, 6-10 from this comment and report back your results.

    Edit: since you already have WPP 5.2.0 installed on your site you do not need to install it again (this might sound obvious but I’d rather make it super clear to anyone reading this.)

    • This reply was modified 4 years, 4 months ago by Hector Cabrera. Reason: Added extra clarification
    Thread Starter steeldrum44

    (@steeldrum44)

    Thank you, I have downgraded to version 5.1.0 which I downloaded and installed and my site works with popular posts activated. Thanks again for your work and this plugin.

    Plugin Author Hector Cabrera

    (@hcabrera)

    WordPress Popular Posts 5.2.1 is out, it fixes this issue and a couple of minor ones as well. Please update as soon as possible.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Broken site after the update on 11 July 2020’ is closed to new replies.