• Resolved Timothy

    (@seahawknationblog)


    I don’t need help just need you folks to fix the update with your plugin and we should be good to go?

Viewing 6 replies - 1 through 6 (of 6 total)
  • i got the same issue. Fatal errors

    Error Line:?46

    Message:?Uncaught Error: Failed opening required ‘/Jorcus/wp-content/plugins/disable-dashboard-for-woocommerces/vendor/freemius/wordpress-sdk/start.php’ (include_path=’.:’) in /Jorcus/wp-content/plugins/disable-dashboard-for-woocommerces/disable-dashboard-for-woocommerce.php:46<br />
    Stack trace:<br />

    Same issue, had to revert to the previous version 3.2.6 but man if I wasn’t staying late our site would been down for several hours…

    Plugin Contributor ospiotr

    (@ospiotr)

    Dear @seahawknationblog @novelasligeras @jorcus

    Please update the plugin to version 3.2.8 which has just been released.

    I performed tests on the production environment, and unfortunately, everything turned out very bad.

    Please follow these steps if your site is not reachable:

    1. Deactivate the plugin manually: https://wpdesk.net/docs/how-to-disable-your-plugin-manually/
    2. Update the plugin to 3.2.8 (don’t activate yet)
    3. Activate the plugin

    I think I’m going to get rid of this plugin (just like those who use Freemius, still having problems with this system).

    Plugin Contributor ospiotr

    (@ospiotr)

    In the near future, I plan to implement automated end-to-end testing to continuously verify the application’s state, preventing similar issues in the future. I’m currently building a CI/CD system to meet today’s quality standards. The critical error discussed was due to a human mistake. The external provider is not at fault.

    I acknowledge the limitations of Freemius as a solution and have explored other licensing systems like Lemon Squeezy and Appsero. However, Freemius remains the preferred choice for WordPress tool developers. I hope the market will offer more convenient solutions soon.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘New Update Killed My Woo Site White Screen’ is closed to new replies.