Version 1.3.0 causes fatal error

  • Resolved danbeach

    (@danbeach)


    2 months, 2 weeks ago

    After updating to the latest version (1.3.0), my site crashes with a fatal error. After deactivating the plugin and then trying to activate it again, WordPress won’t activate it because of the same error. My logs record the following error in each case:

    PHP Parse error: syntax error, unexpected 'Trait' (T_TRAIT), expecting identifier (T_STRI
    NG) or '{' in /wp-content/plugins/easy-accordion-block/inc/Admin/Admin.php on line 4
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Binsaifullah

    (@binsaifullah)

    Thanks for sharing it. please allow me a moment to check and update it. Thanks

    Hello, I just saw this thread after creating my own about the exact same issue.

    Sorry for unintentionally creating 2 support threads about the same problem.

    Plugin Author Binsaifullah

    (@binsaifullah)

    Hi,

    I have checked the plugin several times; unfortunately, I didn’t find any error. Can you please delete the plugin, delete cache, and again reinstall and activate? and please let me know the update.

    Note: Don’t remove the accordion from your posts/pages; when you delete the plugin, it will say no blocks found. Don’t worry, it will be back when you reinstall it.

    Looking forward to hearing the update from you.

    Thanks

    Hi,

    I just tried again on a brand new WordPress (v6.7.1) install (with PHP v7.4.30) and I still get the same error. I have no plugins installed and nothing custom, as I just created the website, it is completely blank.

    Here’s a screen recording of it: https://cln.sh/SPJb15Y4

    Thread Starter danbeach

    (@danbeach)

    Even after deleting the plugin and cache and reinstalling it, I get the same error.

    Plugin Author Binsaifullah

    (@binsaifullah)

    Hi,

    Thanks for your try, I got the matter, it is due to autoloading. However, the issue is fixed in 1.3.1 version, Please update the plugin and check. Now it should run without any error.

    Thannks

    Hi,

    Thanks a lot, the new version fixed it for me!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.