Hi, we looked into it. There are two things I will point out.
1. This is probably a case of plugin conflict.
2. Unfortunately, over the last few days, I did some deep research and found out that the format we have for Etsy is deprecated and we were not able to collect their feed configurations since their latest API changes.
If you have the latest copy of their feed configurations, then you can give it to us and we can try to update it, or we will simply remove it from our supported merchant list.
Hope you understand.
Thanks.
Thread Starter
a
(@cfreek)
1) The only plugins activated are yours, Jetpack, Akismet, and a few WooCommerce plugins – their plugins, like payments, etc.
2) I may be misunderstanding here. Do you not have access to any developer information for Etsy, so you’re going to just abandon the plugin?
Hi, plugin conflict is just a possibility, however, there could be many reasons such as a server timeout, or a server restriction. But I can be more sure if I can take a look at the console errors.
And no, we are not abandoning the plugin. At the time when we added Etsy, they still had public instructions on uploading products using feed file. Now, they changed their instructions with API instructions. But we are not doing any API integration for marketplaces through our plugin.
And looking at their instructions, I believe our current feed format is no longer supported. And even if you use the API, it only allows limited data. Then you still have to manually edit the products there and update certain information for all the products. (This is what I understood from their current instructions but not 100% sure.)
Now as I said, we do not have access to their current feed format, if any.
If you have access to a sample, then you can provide it to us and we will implement it. If not, the worst-case scenario, we simply have to stop supporting Etsy. The plugin will still be there for all other merchants and marketplaces.
Sorry for the inconvenience. Hope you understand.
