thecloudfactory

in my search.. i found 10.. but 6 were in the comments.. non-comment matches were 4.

they are

WPI\Product\Meta.php line 89, 237

WPI\Permalinks.php line 21, 22

Can you list the file locations and line numbers to help others? also the version of the plugin to see whether this applies to others.

Thanks in advance.

+1 for great plugin..

In connection, payment instructions needs translation. for examle, if i enabled BACS as a checkout option, there is instruction that is saved within woocommerce settings.

i notice that it’s hard to find where this is in the code to even to register it as a string translation. please make it so that instructions are translated or easily translated in the next release.

I think I have a similar issue.

Catarina,
where did u translate the attributes? I don’t see it in the string translations.

I have found out by experience that when you save the translated category or brand of a product and enter the same slug as the default language –> this creates a big problem. Any subsequent tries will only make double triple records of the translation.. and it throws off the system.

I had to delete the original category / brand and restart.

Don’t put any slug that is already being used. It did give me a warning but the problem persisted until I delete and redo.

====================

silly me, but I had trouble of finding the translated pages. I wanted to delete the translated page and recreate. You can do this by clicking on the top admin bar to change the language. I don’t know why this wasn’t intuitive for me.

=====================

I think you can find the post/tags missing language association by examining term_taxonomy table and examine the entries with taxonomy (term_translations).

if the data looks like the following. My original is “en” (English) and the transalated is “ko” (Korean). The post 25 is the original and the post 323 is the translation.

a:2:{s:2:”en”;i:25;s:2:”ko”;i:323;}

If the data looks like this, then the post 26 has been assigned the default language but no translation.

a:1:{s:2:”en”;i:26;}

I think you can use something like this to find terms that are missing a translation. “en” should be your default language code, “ko” should be the missing translation you are searching for, of course.

SELECT *
FROM wp_term_taxonomy
WHERE description LIKE ‘%”en”%’
AND description NOT LIKE ‘%”ko”%’

I has to struggle to find a solution. I think the plugin author is busy at the moment.

1. variation didn’t work. and it must be with the variation attribute which is not translated completed when the translation is made. I checked the db and most of other postmeta was present except variable attributes like ‘attribute-color’ ‘attribute-size’. I manually entered in the values according to the translated products’s post_id.

for example. original english had product id of 1 and ids of variable attribute of 2,3,4.
and the translated product is is 10 and its ids of variable attribute are 11,12,13.

I manually copied in the db the values of 2 to 11, 3 to 12, 4 to 13. Then the variable product worked in the front-end.

*warning: if i save the translated product page, then this manual work gets undone. So don’t save the translated page of the variable product.

2. i learned via reading support that you can make it editable by polylang setting of removing locker feature.

3. this issue was fixed by #1

hope this helps someone.

plugin ??? ?? https ? ???? ??? ?? ???. ?????~ ?????~

If you are using https connection, comment line 65 and uncomment line 69

//Daum postcode search for HTTP
//SSL? ???? ?? ?? ?? ?? ??? ?????.
//wp_enqueue_script( ‘postcode’, ‘https://dmaps.daum.net/map_js_init/postcode.v2.js’, array(), null, true );

//Daum postcode search for HTTPS
//SSL? ???? ?? ?? ??? ?????.
wp_enqueue_script( ‘postcode’, ‘https://spi.maps.daum.net/imap/map_js_init/postcode.v2.js’, array(), null, true );

???? ?? ?????. ^^