2.0 causes a fatal error

  • Resolved slewisma

    (@slewisma)


    1 year, 4 months ago

    Updated to 2.0 and got a fatal error. Had to rename the plugin folder to be able to login. Cannot reactivate without causing the fatal error.
    It looks like you are requiring a bunch of php files that don’t exist.

    • This topic was modified 1 year, 4 months ago by slewisma.

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Alex Sirota

    (@asirota)

    1 year, 4 months ago

    Yes I’m seeing this too. Auto update to v2.0 crashes the site. I manually updated the folders of the plugin with the contents of 2.0.1 zip file by manually downloading it and updating the existing plugin folder with all files. All is well again.

    Plugin Author Nick Halsey

    (@celloexpressions)

    10 months, 3 weeks ago

    Noting for future reference that yes, there was an issue with the 2.0 package that I didn’t notice until after my site also auto-updated to a fatal error. Version 2.0.1 repackaged to include the missing files, but there was a window in between when sites could auto-update to the broken version. WordPress core is working on a feature that will prevent auto-updates from silently breaking in this way in the future; it is on track to land with WordPress 6.4:

    https://core.trac.wordpress.org/ticket/58281

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘2.0 causes a fatal error’ is closed to new replies.