WPIntell

Source evidence

Not compatible with PHP8

WooSidebars · support · 2021-01-16T10:41:00+00:00

complaintsentiment
highseverity
0.96relevance
13replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 16 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

11 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
daver unresolved
woosidebars seems isn’t compatible with PHP8 When enabling, this fatal error is generated: Uncaught ValueError: Unknown format specifier "a" in /wp-content/plugins/woosidebars/classes/class-woo-sidebars.php:170 Tested with version 1.4.5 (latest) Rolling back to PHP 7.4 run fine. D. Hello, I have the same problem – can you please create a new version of Woosidebars with update to work with PHP8? Thank you Lucka Same problem – this is the only plugin holding me back from PHP 8.0.2. An update for PHP 8 support would be awesome (or maybe someone could figure out how to update that line 170 to not throw the error). Also interested, having the same problem. You should be able to fix it yourself by changing the %a to %s on the line 170 before the plugin author publishes the fix. @tatutre Thank You for solution. Is a update coming for this plugin or is it abandoned? Yes, I have same error. THX for fix. And waiting official update! Any news please? Abandoned plugin? The error is fixed by going to the file: /wp-content/plugins/woosidebars/classes/class-woo-sidebars.php And chaning line 170 from: 'search_items' => sprintf( __( 'Search %a', 'woosidebars' ), $plural ), To: 'search_items' => sprintf( __( 'Search %s', 'woosidebars' ), $plural ), Tusind tak, @jenskirk – det var en life saver 🙏 @jenskirk Thank you very much. @jenskirk Nice job finding and describing the fix – much appreciated! For other folks with this issue, and for what it’s worth – there is an update on Github that incorporates this fix. It was listed for stable release about a week ago (Jan 20, 2022) so hopefully we’ll see the update available here soon. Since it implements the same fix as @jenskirk ‘s solution, there will be no issue for those of us who have updated the plugin manually.

Comments

13 shown
luckacv 2021-02-11T01:00:00+00:00

Hello, I have the same problem – can you please create a new version of Woosidebars with update to work with PHP8? Thank you Lucka

wooq123 2021-02-11T19:44:00+00:00

Same problem – this is the only plugin holding me back from PHP 8.0.2. An update for PHP 8 support would be awesome (or maybe someone could figure out how to update that line 170 to not throw the error).

marekp19 2021-02-12T11:49:00+00:00

Also interested, having the same problem.

tatutre 2021-02-15T23:07:00+00:00

You should be able to fix it yourself by changing the %a to %s on the line 170 before the plugin author publishes the fix.

curiousharshit 2021-03-06T12:08:00+00:00

@tatutre Thank You for solution.

prokops 2021-06-29T19:01:00+00:00

Is a update coming for this plugin or is it abandoned?

webparaplan 2021-07-12T08:59:00+00:00

Yes, I have same error. THX for fix. And waiting official update!

jenskirk 2021-07-25T14:37:00+00:00

Any news please? Abandoned plugin?

jenskirk 2021-07-31T14:40:00+00:00

The error is fixed by going to the file: /wp-content/plugins/woosidebars/classes/class-woo-sidebars.php And chaning line 170 from: 'search_items' => sprintf( __( 'Search %a', 'woosidebars' ), $plural ), To: 'search_items' => sprintf( __( 'Search %s', 'woosidebars' ), $plural ),

martinkroeger 2021-11-13T12:49:00+00:00

Tusind tak, @jenskirk – det var en life saver 🙏

Frank444 2021-11-17T20:05:00+00:00

@jenskirk Thank you very much.

thompsonpaul 2022-01-26T21:59:00+00:00

@jenskirk Nice job finding and describing the fix – much appreciated!

thompsonpaul 2022-01-26T22:14:00+00:00

For other folks with this issue, and for what it’s worth – there is an update on Github that incorporates this fix. It was listed for stable release about a week ago (Jan 20, 2022) so hopefully we’ll see the update available here soon. Since it implements the same fix as @jenskirk ‘s solution, there will be no issue for those of us who have updated the plugin manually.