Hi @khadimyaseen,
May I ask what version of WooCommerce you are using? If version 8.5 then currently, WooCommerce in the latest version causes errors on different themes and with different plugins. I encourage you to downgrade to version 8.4 as this version resolves these issues.
There are plenty of reports on the WooCommerce support forum regarding this topic: https://projectdmc.org/support/plugin/woocommerce/
I’ve spotted the same. Rather you should fix this plugin to meet new woocommerce version than making a solution to downgrade woocommerce. Is there woocommerce an addon to this plugin or am I missing something?
Hi @dantg
Thank you for your feedback. I’m sure you know that you did not miss anything. Our developers are aware of this issue. However, this particular case is a bit different than usual bug, which we can fix right away.
Mentioned error was caused by the newest WooCommerce version. WooCommerce 8.5 caused plenty of issues (not only with FCF, but some other plugin and motives). Most likely, because of these issues WooCommerce authors downgraded it to version 8.4. This is why, rolling-back (as it is an official solution) is the best and quickest way to solve your issue.
Once 8.5 is available we will update FCF as soon as possible to make it fully compatible.
Have a wonderful day 🙂
Thanks @dominikl65 for the quick response.
Yes I am using 8.5 version of WooCommerce and I think I will stick with it for now because downgrading may make things even worse for me.
As @damianmachnik mentioned, until the woocommerce fix there new version, I have found a quick fix to this particular error.
Here’s what I did:
On /wp-content/plugins/flexible-checkout-fields/classes/plugin.php:247,
I added a check with is_array before attempting to unset the keys, which prevented the error.
if (is_array($field)) {
unset( $base[ $key ]['placeholder'] );
unset( $base[ $key ]['label'] );
if ( version_compare( WC()->version, '4.4.1', '>=' ) ) {
unset( $base[ $key ]['class'] );
}
}