WP All Import
Forum Replies Created
-
Hi @gurug,
when I export products from woocommerce, preview does show me right language of descriptions, etc, but in generated export file – all is always is other (everytime same) language. Any ideas how to fix that?
We’d need access to an environment where this is happening (I couldn’t replicate it) in order to figure out what’s going on. Please contact our support team at http://www.wpallimport.com/support/ about this and we’ll help out there.
Hi @noupe,
You would have to use this workaround to allow HTML in term descriptions: https://woocommerce.com/document/allow-html-in-term-category-tag-descriptions/.
Hi @komarovski,
Since this is related to our Pro plugin, can you please send us this message via http://www.wpallimport.com/support/? We can only help with the free versions of our plugins on this forum.
Hi @gecatabg,
Can you please try deactivating WP All Export and reactivating it? Hopefully that will fix the missing column mentioned in the error.
If it does not fix it, please contact us here: http://www.wpallimport.com/support/. Since it’s related to our Pro plugin, we can’t help with it on this forum.
Hi @brian5e597bf8e0,
It sounds like you’re using a third-party plugin to modify the order IDs, so we’d need to check how that tool is storing the data to advise on exporting it. Please replicate this issue on a sandbox site at http://www.wpallimport.com/debug/, then send us the sandbox site URL and a brief description of the issue at http://www.wpallimport.com/support/.
Hi @mcdeth,
Two things:
- The “processing” script has to run at least once in order for the “pmxe_after_iteration” hook to fire and run the rest of the export.
- You should put the full (including protocol and domain) processing URL in the $cron_processing_url variable.
Hi @andreanyc,
Unfortunately, the free version of WP All Export doesn’t support filters like that, but you can use a custom WP_Query to do it: https://www.wpallimport.com/documentation/wp-query-export-to-csv/. ChatGPT or Claude AI should be able to help you write a WP_Query with a date_query that fetches all posts from 2017 or before.
Hi @shereewalker,
As long as the customers and products are assigned to the purchases, the IDs of the products in the purchase shouldn’t matter.
Hi @grahamhopsack,
That looks right, but we can only help with our free features on this forum. If you need help setting up a pro feature, please contact us here: http://www.wpallimport.com/support/.
Hi @shereewalker,
Newly imported posts are considered new posts in WordPress, so a new, unique, ID will be generated for them. It works the same way as manually creating a post.
That said, you can attempt to keep the old IDs using a custom workaround like this: https://www.wpallimport.com/documentation/code-snippets/#keep-old-ids-when-migrating-products, though it is not guaranteed to work. The only way to be sure to keep old IDs is to do a complete database migration.
Hi @maelstrom06,
If you’re re-importing a modified version of the same file you imported the first time, you should just update the first import with the new file and re-run it: https://www.wpallimport.com/documentation/update-import/.
If you must use separate imports, then you can use an “Existing Items” import to avoid duplicates: https://www.wpallimport.com/documentation/update-existing-posts/.
You can learn more about the import types here: https://www.wpallimport.com/documentation/import-types/.
Hey @grahamhopsack,
The “Remove or modify products created or updated by this import and then later removed from this import file” option can only remove products that were previously created by the import you’re running. It can’t remove items created manually or by other imports.
Unfortunately, this requires the “Remove or modify all products on this site that are not present in this import file” option, which I’m afraid isn’t available in the free version of our plugin. You’ll have to manually remove the products that aren’t a part of the import.
Let me know if you have any other questions.
Hi @earthnutvt,
This error typically means the import is trying to continue after the server has terminated the session. If you restart the import from the beginning, does it fix it?
If it still happens when you restart it fresh, try running a conflict test ( https://www.wpallimport.com/documentation/plugin-theme-conflicts/ ) on a staging copy of the site.
Hi @shortik,
For support with our Pro versions, you will have to contact us here: http://www.wpallimport.com/support/. We can only advise on our free plugins in this forum (one of which is the one I linked you to).