[Closed] WPML causing issues while importing products with WP ALL IMPORT.

Hi there

Do you only see errors in the server logs, or do you see problems during the import process itself? (WP All Import logs the progress of the imports continuously.)

Importing multilingual content is a 2-step process, whereby you import the default language content first, and then—separately—import the translated content.

Do you know, do the problems occur only when importing the original content, the translated content, or both?

It would help if I could see your set up, examine the files you are importing, and run the imports (or a sub-set of them) to track their progress.

Could I get access to your site?

Let me mark your next reply as private so that I can get log-in credentials from you—you may want to create a temporary admin user for me to use that you can later delete. And be sure to have a current backup of your site.

Can you confirm details of the imports you are running that you experience problems with.

Actually, I'm seeing errors such as this recurring in the logs:

WordPress database error Duplicate entry '7288051-2452-7288059-pa_%ce%b4%ce%b9%ce%ac%cf%83%cf%8' for key 'PRIMARY' for query INSERT INTO wp_wc_product_attributes_lookup (
					  product_id,
					  product_or_parent_id,
					  taxonomy,
					  term_id,
					  is_variation_attribute,
					  in_stock)
					VALUES
					  ( 7288059, 7288051, 'pa_%ce%b4%ce%b9%ce%ac%cf%83%cf%84%ce%b1%cf%83%ce%b7', 2452, 1, 1 ) made by do_action('wp_ajax_as_async_request_queue_runner'), WP_Hook->do_action, WP_Hook->apply_filters, WP_Async_Request->maybe_handle, ActionScheduler_AsyncRequest_QueueRunner->handle, do_action('action_scheduler_run_queue'), WP_Hook->do_action, WP_Hook->apply_filters, ActionScheduler_QueueRunner->run, ActionScheduler_QueueRunner->do_batch, ActionScheduler_Abstract_QueueRunner->process_action, ActionScheduler_Action->execute, do_action_ref_array('woocommerce_run_product_attribute_lookup_update_callback'), WP_Hook->do_action, WP_Hook->apply_filters, Automattic\WooCommerce\Internal\ProductAttributesLookup\LookupDataStore->__call, call_user_func_array, Automattic\WooCommerce\Internal\ProductAttributesLookup\LookupDataStore->run_update_callback, Automattic\WooCommerce\Internal\ProductAttributesLookup\LookupDataStore->create_data_for, Automattic\WooCommerce\Internal\ProductAttributesLookup\LookupDataStore->create_data_for_variation, Automattic\WooCommerce\Internal\ProductAttributesLookup\LookupDataStore->insert_lookup_table_data_for_variation, Automattic\WooCommerce\Internal\ProductAttributesLookup\LookupDataStore->insert_lookup_table_data

They don't appear related to WPML, and to confirm that I've disabled the main WPML plugins and re-run the import, and it continues to generate these errors.

Perhaps you could look into that. Details are in wp-content/debug.log (I'm inspecting that with the Filester file manager plugin).

I've been testing by re-running import ID 602 ("showood - kipos/ksilines glastres").

First, I notice that you are not on the latest versions of WPML and String Translation. You'll need to update the site key for this site URL to be able to automatically update WPML to the latest 4.6.9. You should update to the current versions before any further testing with WPML active.

I'm not in a position to run imports via CLI so I'm using the normal UI via Manage Imports.

I checked again just now, disabling WPML plugins and then attempting to re-run the import with ID 602.

Once again the import fails to complete and the debug.log (at wp-content/debug.log) is full of warnings and errors.

This is with WPML plugins inactive.

It's not possible to debug warnings coming from WPML when it is active when there are warnings and errors when WPML is inactive, as the WPML errors may be a consequence of the other issues.

If there is a specific import you want me to test with let me know, but I'll need to see that it works without WPML active before I can then check it for any WPML-related problems.

From the installer support page (wp-admin/admin.php?page=otgs-installer-support) I can see in the log that the site key doesn't match.

I assume you registered WPML for the original version of the site, then made a copy at this test URL.

The site key is based on the URL, so you will need to unregister WPML (from the page in your screenshot), and then re-register it with this current URL, which will give you a distinct site key.

You should then be able to check for updates and install the latest versions.