I have been in contact with Barn2 support who have referred me to your support if the guide they provided could not help me. The guide did not solve my problem so now I am trying to get help from you.
I have a WPML setup with two languages enabled, DK (miho.dk) and SE (miho.se). I am using the product tabs plugin from Barn2, and have created two global tabs in the DK version with default content. Each product will override the global tabs with product specific tab content. The global tabs label and the global content have been translated in the SE version, but I cannot see the product specific translated content in the SE version. Please guide me on how to set up WPML in order for getting the SE translation to work. If needed I can grant you access to the backend.
I have received the attached guide from Barn2, and my global tabs and content is translated just fine. But it is the product specific content I dont see on the frontend.
The product specific content seems to be translated in the WMPL Advanced Translation Editor, however it is not displayed on the frontend.
On the products I can see that the override checkmark on the products are not set. Hence the global content is display as expected.
So I guees the override checkmark needs to be set somehow - hopefully done automatically?Next, the translation of the product specific tab content from the original language needs to be inserted on the tab. Hopefully this is done automatically as part of the product translation when set up correctly?
I have attached some screenschots to help explain my situation.
Thank you for the explanation and the screenshots.
From what I understand, the global tab content is not being overwritten in the translated product, even though it is set correctly on the product in the default language.
This usually indicates that the information is stored in a custom field that is not being copied to the translation.
Could you please try the following steps?
1. Go to WPML → Settings → Custom Fields Translation and enable the option
“Show ‘Multilingual Content Setup’ meta box on post edit screen.”
2. Open the product in the original language for editing.
3. Scroll to the bottom of the page and expand the Custom Fields section.
4. Look for a custom field that may be related to the global tab content and set its translation preference to Copy, then save the changes.
5. Make a small change to the product description in the original language, update the product, and then complete the translation so the changes are synchronized.
Try two of them where it says "override". I also pointed out in the screenshot. And then, an important part :
5. Make a small change to the product description in the original language, update the product, and then complete the translation so the changes are synchronized.
I have followed your procedure, but I still don't see the product specific content on the frontend tabs. After doing the changes I tried translating a new product but I experienced the same issue - no product specific content in the tab.
I have looked at the translated products and the override checkmark are still not set with the change from "Don't translate" to "Copy"
I can see that the global tabs in the translated version have their own custom fields (_wpt_override_wpt-35344, _wpt_override_wpt-35346 and _wpt_field_wpt-35344 - _wpt_field_wpt-35346 is missing!!) It seems like there is no connection between the custom fields in the original version and the translated version.
Please see attached screenshots for further description.
I need to request temporary access (wp-admin and FTP) to your site—preferably to a test site where the problem has been replicated if possible—in order to be of better help. When you log in to leave your next reply, you will find the needed fields below the comment area. The information you will enter is private, meaning only you and I can see and access it.
I’ve reviewed your website, and you’re absolutely right — there is no connection between the custom fields in the original product and its translated version. This leads me to believe that the fields may have been added separately rather than inherited during translation.
Could you please clarify the steps you followed? For example, were the tabs added or modified after the products had already been translated?
Also, would it be possible for me to create a test product on your live site to further check the issue? This would help me better understand the workflow.
Honestly, I cannot remember if I created the tabs myself and then translated them with WPML OR if WPML created the tabs as part of a translation. I can remember I had a tab too much created by mistake which I then deleted. So the process has not been so clean. Would it be possible to delete the translated tabs completely (only in the SE version) and then let WPML translate them again and inherit setup/content from the original language (DK)?
You can go ahead and create a test product, no problem.
I have experienced that my stock is reduced 2-3 times when an order is processed. I can see I receive several woo messages on the order that stock has been reduced - in both the original language and the translated language (have a look at order #35591). I have tried to sync stock status using your 'Troubleshooting' tools and flushed WP Rocket and Redis cache afterwards but I am still seeing the problem. We have to adjust stock manually after processing every order, so a rather critical issue.
I know it is probably not related to the issue regarding the tabs, but would it be possible for you to have a look at this also when you are logged into the system? Maybe it is because all the published products on the original language have not been translated yet? Can this cause some out of sync issues that can trigger several stock reductions?
Thank you very much for your help 🙂
/Peter
New threads created by Andrey and linked to this one are listed below:
I’ve investigated this further and have created a ticket for our compatibility team to review, as I was also able to reproduce the issue on my end.
The Product Tabs are using different custom fields in the original product and in its translation. This is why the content appears in the Translation Editor, but does not display on the front end — the custom field IDs are different between the original and translated products.
I’ll keep you updated here as soon as I have more information from the compatibility team.
If this issue is blocking your work and you need to proceed in the meantime, you’ll need to make the adjustments directly in the WordPress editor for the translated product, rather than using the Translation Editor.
Thank you for the update. Looking forward for the feedback from your compatability team.
I decided to buy the Barn2 plugin, because I thought it was fully WPML compatible. So if it turns out there is a compatability issue I have to use another plugin. Can you recommend other plugins providing extra tabs that are fully compatible with WMPL? Then I can have a look while we wait for your compatability team to provide feedback.
I am planning launch of the second language shop mid Febuary, so I hope we can find a solution together soon 🙂
The plugin is compatible. As far as I can see, in earlier versions (or in other versions), it was possible to adjust the slug of the Product Tabs custom fields so that the same fields were used in both the original product and its translations. However, somehow this is no longer possible in the version you’re currently using.
Let’s wait for feedback from the compatibility team. I will keep the support ticket open 🙂
In the meantime, if you’d like to explore alternative options, you can check the list of WPML-compatible plugins here: https://wpml.org/plugin/
You can also try searching on Google for the plugin name + WPML to see whether it’s confirmed as compatible.
I have some good news for you. You might remember that earlier I mentioned it was no longer possible to adjust the slug of the Product Tabs custom fields. Our compatibility team has now identified the cause: the option was simply hidden by CSS.
Here’s what I did to confirm this:
1. I went to WPML → Languages → Language switcher options → Additional CSS and added the following rule:
2. This made the “Screen Options” panel visible when editing a product tab.
3. After that, the “Slug” option became available. I’ve attached a screenshot showing this.
You can safely remove this CSS rule afterward if you don’t need it anymore.
What you need to do next
To ensure everything works correctly, make sure that the Tab ID (slug) is identical in all languages:
• Each tab has a KEY, and this ID is used in the custom field names
_wpt_override_ID and _wpt_field_ID.
This ID is essentially the slug of the Product Tab post.
• You have two options:
• Create new tabs and use the same title in Danish and Swedish (so the slug is generated identically), or
• Edit the existing tabs (Danish and Swedish) in the WordPress editor and manually set the same slug.
• Important: If you change the slug, you will need to re-edit the product and re-add the custom tab content, since the custom field name depends on the slug.
Finally, as originally suggested:
• Set _wpt_override_ to Copy
• Set _wpt_field_ to Translate
This way, the product and its translation will correctly share the same custom field setup.
I’ve attached a screenshot where the slug is visible for reference.
Some questions to your procedure, where you write "• Create new tabs and use the same title in Danish and Swedish (so the slug is generated identically)"
- Does this mean I have to make new Tabs for the Danish products or only the Swedish?
- When I manually create new Swedish Tabs and give them the same title as in the Danish products, wil they then automaticaly get same IDs/Slugs as the Danish ones? I thought new tabs would always get new IDs/Slugs?
- When the ID/Slugs are identical, can I then rename the Tabs, for the Swedish products after the ID/Slugs have been set?
So maybe if you can detail this step a bit more for me, I would be really happy 🙂 It sounds like the most safe way is to create new tabs, so I will go for that solution.
