WPIntell

Source evidence

Plugin Broken

Microsoft Azure Storage for WordPress · support · 2023-02-21T12:04:00+00:00

mixedsentiment
highseverity
0.94relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

7 / 37 rows with source links

18.9% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
wellconnit resolved
Hi Team, The plugin has stopped loading past the containers and the container dropdown in blank. We recently started seeing the following issue in the error_log of the wp-admin folder. [21-Feb-2023 11:52:36 UTC] PHP Fatal error: Uncaught TypeError: Return value of Windows_Azure_Generic_List_Response::current() must be an instance of mixed, array returned in /home/xyz/public_html/wp-content/plugins/windows-azure-storage/includes/class-windows-azure-generic-list-response.php:145 Stack trace: #0 /home/xyz/public_html/wp-content/plugins/windows-azure-storage/windows-azure-storage-settings.php(294): Windows_Azure_Generic_List_Response->current() #1 /home/xyz/public_html/wp-admin/includes/template.php(1785): windows_azure_storage_setting_storage_container(Array) #2 /home/xyz/public_html/wp-admin/includes/template.php(1739): do_settings_fields(‘windows-azure-s…’, ‘windows-azure-s…’) #3 /home/xyz/public_html/wp-content/plugins/windows-azure-storage/windows-azure-storage-settings.php(87): do_settings_sections(‘windows-azure-s…’) #4 /home/xyz/public_html/wp-includes/class-wp-hook.php(308): windows_azure_storage_plugin_options_page(”) #5 /home/xyz/public_html/wp-includes/class-wp-hook.php(332): WP_Hook- in /home/xyz/public_html/wp-content/plugins/windows-azure-storage/includes/class-windows-azure-generic-list-response.php on line 145 We believe the error started a few months ago, but haven’t been able to work out exactly when. WordPress is 6.11 PHP is 7.4 Plugin is 4.3.4 If anyone has seen it and know’s how to rectify please let me know. Thanks! Thanks for the report. In looking into this, I found the issue. We solved a problem with PHP 8.1 but in doing so, we broke compatibility with PHP 7.4. We are currently deciding whether we make PHP 8.0 our minimum (which solves things here) or if we try and keep support for PHP 7.4. In the meantime though, there’s two options that will fix this: Rollback the plugin to v4.3.3 Upgrade the PHP version on your server to PHP 8.0+ @dkotter , Thanks for looking into that, we’ve upgraded to 8.0 and it’s fixed the issue.

Comments

2 shown
Darin Kotter 2023-03-02T22:22:00+00:00

Thanks for the report. In looking into this, I found the issue. We solved a problem with PHP 8.1 but in doing so, we broke compatibility with PHP 7.4. We are currently deciding whether we make PHP 8.0 our minimum (which solves things here) or if we try and keep support for PHP 7.4. In the meantime though, there’s two options that will fix this: Rollback the plugin to v4.3.3 Upgrade the PHP version on your server to PHP 8.0+

wellconnit 2023-03-03T06:54:00+00:00

@dkotter , Thanks for looking into that, we’ve upgraded to 8.0 and it’s fixed the issue.