Fabrick Support

Hello and sorry for the late reply.

your message is not enough clear for us to understand what kind of issue you are facing.

please write to [email protected], with a detailed description of the issue, with screenshot of the error message and the configuration set on the plugin

thanks

Fabrick Plugin Support Team

• This reply was modified 4 months, 3 weeks ago by Fabrick Support.

Good evening,
we have done some analysis. The error starts here:
array_map(): Argument #2 ($array) must be of type array, int given
in abstract-wc-shipping-method.php:539

thus inside WC_Shipping_Method->get_instance_form_fields() / get_option() of the WooCommerce Flat Rate shipping method.
in the backtrace there is no presence of any functions of the plugin Axerve/GestPay: plugin starts directly after the core part of WooCommerce
advanced-dynamic-pricing-for-woocommerce-pro
(ADP\BaseVersion\Includes\CartProcessor\CartProcessor->process())

So:

• The crash happens during the shipping calculation, WooCommerce core codes;
• Our plugin doesn’t trigger during this phase and it is not present in the stack.

This could be the reasonfor the crash:

1. Bad configuration or corruption of a method Flat Rate
   WooCommerce waits for an  array of options for the shipping method, but it gets an integer.
2. Interactions with the Advanced Dynamic Pricing for WooCommerce Pro
   the plugin ADP, which intercepts the cart and shipping calculation, could override or modify the shipping method options and give back a not valid input (int instead of an array), causing the crash of array_map().

I can suggest these points:

1. Quick test on plugins
   • Temporaly deactivate Advanced Dynamic Pricing for WooCommerce (Pro)
   • Clear the cache
   • Refresh the page that gave the error (cart/checkout/backend)
     If all is fine, issue is relate to interactions between WooCommerce Shipping ↔ Advanced Dynamic Pricing.
2. Check and re-save the shipping methods
   • WooCommerce → Settings → Shipping → Shipping Zones
   • Go into the needed zone
   • Open the methods “Flat rate” actually active
   • Check that the fields (cost, rules) are good and then save again.
   • If there are doubts, it could be useful to create a new Flat Rate method, to test if with the new method all works fine.
3. Verify the versioni
   Please send to us:
   • WordPress version
   • WooCommerce version
   • PHP version
   • List of the main plugins installed and related to the cart (discount, advanced shipping, multi-currency, and so on…)
4. Debug log
   If problem still persist:
   • Enable WP_DEBUG_LOG and WooCommerce log
   • Generate the error
   • Send to us all the logs generated during the error simulation, and every ADP or shipping log message.

we are available for further assistance

Team Fabrick

Hello everyone,
thank you all for your reports.
We have investigated and identified the issue, the new release 20250912 includes the fix for the reported bug.
Please let us know if you meet any further issues.

We remain available for any questions or clarifications.

Thank you,
Team Fabrick

good day, with release 20250603 this issue on generation of logs has been solved

thanks & regards

Good day!
thank you for your report, we are investigating in this anomaly in log generation.

may I ask you if the issue is still present with the newest release, the 20250530?

and, for future reports, to have quicker and full support, please write to [email protected]

thanks & regards

Buongiorno,
abbiamo preso in carico la sua segnalazione e le risponderemo quanto prima.

per future segnalazioni, per ricevere un supporto più completo e veloce, può scrivere a [email protected]

grazie e cordiali saluti

ciao @wizy80 ,

Stiamo lavorando per risolvere l’incompatibilità presente su alcuni ecommerce per la versione 20240823.

Nei prossimi giorni verrà rilasciata una nuova versione che risolve questa problematica.

Ci scusiamo per il disagio creato.

Grazie,

Dear All,

Thank you for reporting the issue.
After the release of the latest version we detected an anomaly, which we are managing and a fix will be released in the next hours.

We apologize for the inconvenience; we will update you promptly when the issue is resolved.

Thank you,