Fatal error after upgrade

Resolved

(@dmiyares)

Getting this on my sites where I’m running this plugin. Running PHP 8

—

error	X.X.X.X:0	PHP Fatal error:  Uncaught Error: Failed opening required '/mySitesRootDirectory/wp-content/plugins/widget-options/includes/widgets/option-tabs/days-dates.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /mySitesRootDirectory/wp-content/plugins/widget-options/plugin.php:202
Stack trace:
#0 /mySitesRootDirectory/wp-content/plugins/widget-options/plugin.php(53): WP_Widget_Options->includes()
#1 /mySitesRootDirectory/wp-content/plugins/widget-options/plugin.php(264): WP_Widget_Options::instance()
#2 /mySitesRootDirectory/wp-content/plugins/widget-options/plugin.php(271): WIDGETOPTS()
#3 /myWebSitesURL/wp-settings.php(418): include_once('/nas/content/li...')
#4 /mySitesRootDirectory/wp-config.php(133): require_once('/nas/content/li...')
#5 /myWebSitesURL/wp-load.php(50): require_once('/nas/content/li...')
#6 /myWebSitesURL/wp-admin/admin.php(34): require_once('/nas/content/li...')
#7 /myWebSitesURL/wp-admin/index.php(10): require_once('/nas/content/li...')
#8 {main}
  thrown in /mySitesRootDirectory/wp-content/plugins/widget-options/plugin.php on line 202, referer: https://www.myWebSitesURL.com/wp-login.php?redirect_to=https%3A%2F%2Fwww.myWebSitesURL.com%2Fwp-admin%2F&reauth=1	Fri May 20 2022 10:20:56 GMT-0400 (Eastern Daylight Time)

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

megaphonejon
(@megaphonejon)

2 years, 4 months ago

I can confirm this bug. I can also confirm that days-dates.php isn’t present in the zip file, and that the issue isn’t specific to any PHP version.

cpsdarren
(@cpsdarren)

2 years, 4 months ago

Same issue. Updated plugin to 3.8, WSOD on dashboard. WordPress email notification indicated Widget Options was causing an error. Had to use recovery mode to disable the addon.

Plugin could not be activated because it triggered a fatal error.

`Warning: require_once(/public_html/wp-content/plugins/widget-options/includes/widgets/option-tabs/days-dates.php): failed to open stream: No such file or directory in /public_html/wp-content/plugins/widget-options/plugin.php on line 202

Plugin Author Marketing Fire
(@marketingfire)

2 years, 4 months ago

@cpsdarren @megaphonejon @dmiyares very sorry for the errors! It looks like our latest update caused an issue. Our support team has been flagged and we will be rolling back that change shortly. Thank you for flagging the errors for us to review.

In the meantime, you can also download a previous version of the plugin at the bottom of this page:

https://wordpress.org/plugins/widget-options/advanced/

Plugin Author Marketing Fire
(@marketingfire)

2 years, 4 months ago

You can also comment out the lines 202 and 203 in /var/www/wp-content/plugins/widget-options/plugin.php and the plugin can be reactivated.

//add days and dates tab DEMO
//require_once WIDGETOPTS_PLUGIN_DIR . ‘includes/widgets/option-tabs/days-dates.php’;
//require_once WIDGETOPTS_PLUGIN_DIR . ‘includes/widgets/option-tabs/styling.php’

jonathanc1
(@jonathanc1)

2 years, 4 months ago

Hello^^,

Is the above option a permanent solution or does something else have to be changed/added later?
bhammondCVL
(@bhammondcvl)

2 years, 4 months ago
I think they should issue an update soon that will fix the issue. In the meantime, commenting out those lines will keep the plugin running. Or you can roll back to the previous version.
- This reply was modified 2 years, 4 months ago by bhammondCVL. Reason: typo
Plugin Author Marketing Fire
(@marketingfire)

2 years, 4 months ago

@jonathanc1 this is just a temp fix. @bhammondcvl exactly right. We are rolling back to the previous version shortly and then the regular update will work going forward

Plugin Author Marketing Fire
(@marketingfire)

2 years, 4 months ago

@bhammondcvl @dmiyares and everyone, we pushed an update a few hours ago (now v3.8.2) to fix these fatal errors. Hopefully that helps resolve everything quickly! Please let us know if you continue to experience any issues though of course too.

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

The topic ‘Fatal error after upgrade’ is closed to new replies.