quedao

For clarity I attach the code that properly prints the image in html:

<tbody> <tr class="item-5949">
 <td ><img class="thumbnail" src="https://npjul23.local/wp-content/uploads/2022/12/hack03ctr23-150x150.jpg" /></td> <td class="product"> 
<span class="item-name">(HACK CTR 03) 2023</span> 
<dl class="meta"> 
<span class="item-meta">&yen;46,990</span> 
</dl> <span class="item-meta"></span> <dl class="meta"> </dl> </td>

Thanks for the update!

Thanks for the reply, is there an ETA for the solution? can we help somehow?

Best

Hello, I reply to myslef cause a find a workoround:

One can enter the characters encoded in utf9

I used this ws to enconde the strings:

https://www.browserling.com/tools/utf8-encode

It has dissappeared, without any action on our side, please disregard

Thanks for the quick reply, I will try the solution.

I will leave the review and upload our translations to the repository

I forgot to mention that we are using Locotranslate, so far working for all strings except point label

Andre,

Thanks for reply.

After importing the products with the default field mapping, they import flawlessly, so that solves the problem. Just they import with the SKU empty (same as original file).

If I try to map the original id to the imported SKU then the variations fail to import again.

What would be a good way to import the variations and keeping the original IDs as SKUs?

Thank you in advance

• This reply was modified 2 years, 9 months ago by quedao.
• This reply was modified 2 years, 9 months ago by quedao.

Igor,

I fixed the problem.

Turns out, having the name of attibute in Japanese (double bit char) caused it.
Just change the name of the attribute in double bit language for the equivalent in English and all products and variations import flawlessly.

I didnt neeed to edit the file, nor needed to change the parents to the SKu instead of the ID.

After import the new parent products have different ids that the originals, but the variations were updated accordingly by woocommerce without any action on my side!

Igor, do you not know that woocommerce does update the ids and the parents when importing ?

Igor,

Thank you again for your help!

Your reply is exactly what I was thinking would be the solution, I did similar changes to my file, but still is not importing.

I here is the file (public this time!)

https://docs.google.com/spreadsheets/d/1uNjlXbjuSGyq4t7ExJkg1lU4EAOAmQIOKf_FQCBY4Bo/edit?usp=sharing

Thanks again!

After some trial I have figured that with the original file is not possible to match parents and variations just by changing the field mapping.

I went ahead and edited the file, I copied the original id to the sku field. then I changed the parent field of each variation from “id:30314” to “sku:30314”. It didnt work.

Then I changed the parent field of the variations to just “30314”, that would match teh new sku. It also didnt work.

This is how the file looks now:
https://docs.google.com/spreadsheets/d/1uNjlXbjuSGyq4t7ExJkg1lU4EAOAmQIOKf_FQCBY4Bo/edit#gid=642459215

Any help apreciated

Dear Igor,

Thank you very much for you reply. it is truly appreciated!

If I understand correctly the problem is that in my file the parent field is populated with the ids of the parent product, and these are lost in the import process because the newly created product come with a new id.

You stated that the solution is to use the sku to match parents and variations, and looking at your screenshot I can see you that were able to do so with my data.

Did you manually edited the file? or you were able to use the file as it is changing the set up in the column mapping screen?

Thank you very much

Thanks for the reply, I cant seem to find a way to download yoast woocommerce, is it only available as a paid plugin?

I tried reinstalling the plug in and no changes

Thank you very much for the quick reply.

Looking at the docs seems like is easily doable with the functions we already have in place. Is there any requeriment or limitation that cant be achived?

Do you have any plan on adding support for amazon in the future?

Best regards