1.16.0 update breaks ClassicPress and WP4.9 sites

  • Resolved Ray Gulick

    (@raygulick)


    3 years, 11 months ago

    I rolled back to an earlier version, so the 17 sites I’m using popup maker on are back online, so can’t point to a website that demonstrates the issue. However, when going to a ClassicPress or WP4.9 site with 1.16.0 update, the screen is white. No error message, but error messages were probably turned off on each of the sites (did not check that).

    I do not know for sure this is only a problem on ClassicPress/WP4.9, but I don’t have the plugin installed on sites with more recent versions of WP.

    • This topic was modified 3 years, 11 months ago by Ray Gulick.
    • This topic was modified 3 years, 11 months ago by Ray Gulick.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)

  • Hello everyone!

    We are very sorry to hear that you are experiencing this issue.

    I will escalate this to our lead developer and we will let you know as soon as we get any new piece of information.

    Thank you!

    Plugin Author Daniel Iser

    (@danieliser)

    Thanks for the reports, will get a patch out that should prevent that error for WP_Block_Type_Registry. The ones related to ActionScheduler_Lock must be related to some type of caching, object caching or PHP opcache etc. Those files were included with the previous version of PM but never used so we removed them. Only an opcache could hypothetically still run code from those files that didn’t exist, so clearing it should be the fix.

    Strange that it doesn’t clear automatically though when a plugin updates.

    That said we are moving towards the block editor as the default. We will try our best to keep that code segmented with a version check, but I cannot guarantee that we will be able to maintain full backward compatibility with < 4.9 for much longer as we keep up with the current releases as well.

    Honestly at this point, I see no reason not to update to the latest WP build. Gutenberg can easily be disabled if you really hate it that much. Nothing else should be so different that I can think of to hold you back other than that. Just my 2 cents as someone who was against merging the block editor initially, but has grown to really like where its going.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘1.16.0 update breaks ClassicPress and WP4.9 sites’ is closed to new replies.

Tags