Issue:
Currently, I’m unable to import a single product in English using the WPML import/export tools. When I disable the WPML import/export plugin, the product import works fine.
What we’ve done so far:
Here’s what we’ve done so far: we disabled the WPML import/export plugin, imported the products in English, and then used auto-translation for those products due to issues with custom attributes translations. After that, we were no longer able to import individual products.
CSV File Path:
This is the single English product in CSV format: hidden link
I tried again today to access the staging version, but this time it's not even rendering. I checked the latest backup you shared, and tested importing a product with all plugins activated, and also with only WPML plugins + WooCommerce activated. The importing process worked fine on both scenarios.
Can you please restore the staging version, and make sure that it is usable? Another option is for you to send a fresh copy, where the issue is happening. Please let me know how you wish to proceed.
The staging server is now stable, so you can access it.
I’ve also shared the database file in case you want to test it locally: hidden link.
We encountered an issue during the import process when the WPML Import/Export plugin is enabled. The import gets stuck specifically with variable products — simple products are working fine.
Upon debugging, we found that the function removeProductsBySkuMeta() is causing the issue.
Plugin file path:
plugins/wpml-import/classes/Integrations/WooCommerce/ImportHooks/Create.php
Line: 283
If we comment out or disable the line: "$product->delete(true);" then we're able to import variable products successfully.
Please see the screenshot for a reference to the plugin code: hidden link
I'm checking what's the best way to proceed here, along with the 2nd tier team. I'll get back to you once we have new information or questions. Thank you for your patience.
This is Christopher. I just wanted to inform you that the staging website is still giving us a hard time to test the issue.
We constantly get either 502 errors or simply no response and it limits our abilities to test the CSV file import.
Lucas will get back to you with more details, but I wanted to interject here sooner so you can double-check the staging website to move this one forward.
One more point is that we tested the same CSV file on another website and the process completed with no issues. So this is an isolated case on your website that we want to investigate.
After a couple of tries, I was finally able to download the DB package you shared. In my local copy, though, I couldn't reproduce the issue. Please check the video: hidden link
In this copy, I didn't deactivate any plugins and used the file you provided - I just changes the product name and SKU. Is the issue still happening on the website? Are you performing any different steps than the ones I showed in the video?
Apologies for the confusion. It looks like we may have sent you an outdated database, which is likely why the products were imported successfully on your end.
Here’s the latest database file we’re using:
Here’s the link:hidden link
We’ve also recorded a video to demonstrate exactly what we’re seeing on our end: hidden link
As shown in the video, we only changed the SKU and product title and tried importing the same file. However, the products didn’t import and the process got stuck in an infinite loop.
Could you please review the steps in our video and let us know if there’s anything else we should try or any differences you notice?
The steps you're following seem to be correct. I downloaded the latest DB file you shared, updated the local copy, but couldn't reproduce the issue. The import process worked flawlessly.
In this case, I'd need to check a working staging version where the issue is reproduced. You can also check for conflicts yourself, keeping WPML Export and Import activates and disabling other plugins and your theme. Let me know how you wish to proceed.
I downloaded the latest DB file you shared, updated the local copy, but couldn't reproduce the issue. The import process worked flawlessly.
Reply :
Please check on your local environment whether you're able to import all 155 tables in the database:
See reference screenshot : hidden link
Also, please remember that when the WPML Import/Export plugin is enabled, the product import process fails. So make sure this plugin is also enabled during your testing.
We tested the same database locally, and the product import works fine when the WPML Export and Import plugin is enabled. However, the import process gets stuck when using it on live environments such as staging, dev, or new servers.
We observed that the product import works as expected with the old database, but fails when using the latest database on the server.
After comparing both databases, we found a difference in the _wcml_settings entry in the options table. We copied the value from the old database and updated it in the latest one (under option_name = _wcml_settings), but that didn’t resolve the issue.
Specifically, the value of "sync_product_cat" differs between the two databases (0 in the old one and 1 in the new one).
Here’s the serialized data from the old database:
-----------------------------------s:15:"sync_variations";i:1;s:16:"sync_product_cat";i:0;s:16:"sync_product_tag";i:1;
This is serialize key for new table:
------------------------------------
s:15:"sync_variations";i:1;s:16:"sync_product_cat";i:1;s:16:"sync_product_tag";i:1;
The staging website is unusable. Let me share what I've done so far, when accessing it:
1. I was able to import the variable product, with WPML Export and Import active, with no issues, though very slowly (the process took over 10 minutes);
2. I tried a second time, recording the screen with Loom, but the process didn't finish after 20 minutes, so I canceled it;
3. I deactivated a few plugins and generated a critical error;
It's very likely that the issue is related to performance and not to WPML Export and Import (as I said, I was able to import a variable product with it active, though I couldn't record it), but we can't confirm, since the website is unusable. If possible, please provide a working staging version with only WPML, WPML String Translation, WooCommerce, WooCommerce Multilingual and Multicurrency and WPML Export and Import active (that's what I wanted to test when I encountered the fatal error).
