Issue preventing plugin loading correctly v1.39.1

  • Resolved Chris

    (@solex)


    1 month ago

     This plugin failed to load properly and is paused during recovery mode.

    An error of type E_ERROR was caused in line 8 of the file /home/thesorti/public_html/wp-content/plugins/forminator/addons/pro/fortressdb/class-fortressdb-forminator.php. Error message: Uncaught Error: Class "Forminator_Addon_Abstract" not found in /home/thesorti/public_html/wp-content/plugins/forminator/addons/pro/fortressdb/class-fortressdb-forminator.php:8 Stack trace: #0 /home/thesorti/public_html/wp-content/plugins/forminator/addons/pro/fortressdb/fortressdb.php(28): require_once() #1 /home/thesorti/public_html/wp-content/plugins/forminator/addons/class-addon-autoload.php(81): include_once('/home/thesorti/...') #2 /home/thesorti/public_html/wp-content/plugins/forminator/forminator.php(344): Forminator_Addon_Autoload->load() #3 /home/thesorti/public_html/wp-content/plugins/forminator/forminator.php(319): Forminator->load_forminator_addons() #4 /home/thesorti/public_html/wp-content/plugins/forminator/forminator.php(112): Forminator->init_addons() #5 /home/thesorti/public_html/wp-content/plugins/forminator/forminator.php(93): Forminator->__construct() #6 /home/thesorti/public_html/wp-content/plugins/forminator/functions.php(18): Forminator::get_instance() #7 /home/thesorti/public_html/wp-includes/class-wp-hook.php(324): forminator('') #8 /home/thesorti/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #9 /home/thesorti/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #10 /home/thesorti/public_html/wp-settings.php(704): do_action('init') #11 /home/thesorti/public_html/wp-config.php(91): require_once('/home/thesorti/...') #12 /home/thesorti/public_html/wp-load.php(50): require_once('/home/thesorti/...') #13 /home/thesorti/public_html/wp-admin/admin.php(34): require_once('/home/thesorti/...') #14 /home/thesorti/public_html/wp-admin/plugins.php(10): require_once('/home/thesorti/...') #15 {main} thrown

    Seeing this error since the update to 1.39.1.
    Having to use the wordpress recovery mode to even get into wordpress admin. Any pointers are appreciated! The app was previously working fine. I’ll see if I can find any other logs. Please let me if/what info you might need.

    WordPress 6.7.1
    PHP version: 8.3.15

    • This topic was modified 1 month ago by Chris. Reason: Add versions
Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Chris

    (@solex)

    Happy to reinstall the plugin if there’s a way to keep all existing forms!

    Thread Starter Chris

    (@solex)

    Ok, I’ve resolved it. Here were my steps:

    1. Enter recovery mode for wordpress as the site was completely broken. This should happen automatically with modern versions of WordPress but this will depend on if you / your admin had set an active email address.
    2. Disable forminator in the plugins section in wordpress admin
    3. Access your server filesystem via your chosen client and navigate to /home/<your username>/public_html/wp-content/plugins/forminator/addons/pro/
    4. Rename fortressdb to fortressdb_old
    5. Test website loads
    6. Enable Forminator
    7. Test website loads
    8. Test forms – one of my several forms was broken. I fixed this by going into Forminator admin through wordpress admin and editing the broken form. I unpublished the form, and republished it.
    9. Test forms – this took a minute or so, presumably while things loaded correctly
    10. Profit

    Fingers crossed the next update doesn’t break things / hopefully this was just a strange one-off. I’ve never seen issues with Forminator before.

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    Hi @solex,

    Seems like the error was due to FortressDB add-on files still being present in your server, Fortress DB integration in Forminator was removed 2 years ago, as the company/plugin is no longer in development.
    https://profiles.www.ads-software.com/website-redirect/fortressdb

    The recent update of Forminator v 1.39.1 has changes in class name and it appears the class-fortressdb-forminator.php was throwing the error due to that.

    I’m bringing this further to our teams attention so that they are aware of the issues noticed.

    Renaming the folder as you have pointed out would be the way ahead, I’m afraid, there won’t be any fixes related to FortressDB and you’ll have to explore new integrations:
    https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#integrations

    Regards,

    Nithin

    Thread Starter Chris

    (@solex)

    Thanks Nithin – I’m not using fortress anyway so that won’t be a problem for me.

    Plugin Support Williams – WPMU DEV Support

    (@wpmudev-support8)

    Hi @solex ,

    I hope you’re doing well and I’m glad to see that Forminator is working properly for you.

    Please let us know if you face any further issues regarding this topic and we’ll go ahead and check it further for you.

    Best Regards,
    Williams Valerio

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