pulsemedianz
New Member
Hi team,
I’m experiencing ongoing issues with order fulfilment using AliDropship Woo (latest version 1.7.0.5).
When attempting to place orders:
I enabled WordPress debug logging and found this fatal error:
Stack trace shows it occurs during:
Example:
After this:
This product works perfectly with API fulfilment.
This workflow used to work previously.
Now:
This is affecting fulfilment reliability, as products that appear valid cannot be processed.
It also makes it difficult to run a niche store (e.g. cat-only products) when suppliers include mixed variations.
Thanks in advance — any guidance or best practices would be appreciated.
I’m experiencing ongoing issues with order fulfilment using AliDropship Woo (latest version 1.7.0.5).
Issue summary
When attempting to place orders:
- Using API → spins indefinitely, then fails with 500 error
- Using non-API → shows:
- “The variation not found”
- “No variations found for this product”
Debugging completed
I enabled WordPress debug logging and found this fatal error:
Code:
PHP Fatal error: Uncaught TypeError: array_map(): Argument #2 ($array) must be of type array, string given
in /wp-content/plugins/alidswoo/includes/aliexpress_sezam/Data/ProductOrder.php
Stack trace shows it occurs during:
- searchProductSkuByNameID()
- getParams()
- action_products()
Key findings
- API works correctly for newly imported products (instant processing)
- Issue only affects specific products
- Products appear normal in WooCommerce:
- variations visible
- dropdowns working
- Resetting product (variations/stock/pricing) does NOT resolve the issue
- Re-authenticating API does not resolve it
Important observations
- In some cases, the issue occurs after modifying variation options.
Example:
- Original product has variations: Cat / Dog / Panda
- I remove Dog and Panda (only want Cat)
After this:
- product looks fine in Woo
- fulfilment fails (both API and non-API)
- However, I also tested a newly imported product where:
- I did NOT delete any variations
- all variations were already cat-related
- no structural changes were made
This product works perfectly with API fulfilment.
Behaviour difference vs previous versions
This workflow used to work previously.
Now:
- removing variation options appears to break SKU mapping
- plugin fails instead of gracefully handling mismatch
- in some cases, even reset/update does not restore functionality
Questions
- Is modifying/removing variation options no longer supported?
- What is the recommended way to:
- sell only one variation (e.g. Cat)
- without breaking AliExpress mapping?
- Should unwanted variations be hidden instead of removed?
- Is the array_map() error a known issue in version 1.7.0.5?
Impact
This is affecting fulfilment reliability, as products that appear valid cannot be processed.
It also makes it difficult to run a niche store (e.g. cat-only products) when suppliers include mixed variations.
Thanks in advance — any guidance or best practices would be appreciated.