• Resolved varactu

    (@varactu)


    <span style=”font-size: inherit;”>Hi,</span>

    I’d like to report a bug with WP Rollback version 3.1.1.

    After updating to this version, it completely breaks the admin interface and parts of the frontend:

    • The admin site display is impacted
    • It becomes impossible to properly access and use the theme (in my case, Avada) to edit or create articles
    • The editor is partially broken
    • Yoast SEO is no longer working correctly inside articles

    Overall, the backend becomes very unstable and imposile to use.

    I rolled back manually to version 3.1.0, and everything works perfectly again:

    • Theme (Avada) works fine
    • Article editor is back to normal
    • Yoast SEO works without any issue
    • No display problems on the site

    So the issue seems clearly related to version 3.1.1.

    Environment:

    • WordPress: latest version
    • Theme: Avada
    • Yoast SEO plugin active

    Hope this helps identify the problem.

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • sarahtopfstaedt

    (@sarahtopfstaedt)

    Hi,

    I can confirm that the same issue appears on my site after updating to version 3.1.1. – We are also using Avada theme.

    Also in my site, after updating my site to version 3.1.1, the theme’s admin panel broke.
    The following fatal error was reported by WordPress:

    Occurred on line 54 of the file /MyURL/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Admin/AdminFooter.php. Error message: Uncaught TypeError: WpRollback\SharedCore\Rollbacks\Admin\AdminFooter::footerText(): Argument #1 ($text) must be of type string, null given, called in /MyURL/wp-includes/class-wp-hook.php on line 341 and defined in /MyURL***/wp-content/plugins/wp-rollback/vendor/wp-rollback/shared-core/src/Rollbacks/Admin/AdminFooter.php:54

    Plugin Author Devin Walker

    (@dlocc)

    Hey @sarahtopfstaedt + @varactu + @senribb

    I just released version 3.1.2 with the fix. Appreciate the quick posts and confirmations of the bug.

    Thread Starter varactu

    (@varactu)

    ok for me it seems to by good in 3.1.2. i test always.
    and for all people it is good ?

    Plugin Author Devin Walker

    (@dlocc)

    @varactu I’ve received multiple reports it’s fixed now. Should be good to go for everyone now 🙂

    The new version now works correctly on my site. Thank you for your prompt response.

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

You must be logged in to reply to this topic.