Return to previous page

CRITICAL ISSUE: Translated product texts visibility erratic

This topic has 19 replies, 2 voices, and was last updated 1 years, 5 months ago ago by Bas Kling

Bas Kling

Participant

September 29, 2022 at 22:22

In the staging version there are 2 identical (code wise) child themes.
name: VoyeurX2 – XStore Child
and: VoyeurX – XStore Child
from both all custom code is deleted and they only contain a screenshot image and css file with the minimum data to define a child theme.

However, VoyeurX – XStore Child has a bunch of settings configured as this is the main child-theme used in the live environment.
These theme settings are causing issues.

The following product pages should all be in English. When VoyeurX – XStore Child is active some have Dutch text parts in them. refreshing the page multiple times can change which of these pages display dutch parts. It’s very inconsistent.
Please see private area for example URLs.

When switching to VoyeurX2 – XStore Child that doesn’t have any configurational changes or settings set, the text on all previously mentioned pages are English.

– All caching is disabled.
– Problem also occurs with all plugins disabled (with the exception of xstore, woocommerce, wpbakery, translatepress)
– enabling/disabling the single product builder doesn’t seem te make a difference.

Please assist in troubleshooting. Not being able to show the English language is a business threatening issue, as the bulk of our sales market is international.

Please, contact administrator
for this information.

#335432 Copied Theme version: 4.3.4

18 Answers

Rose Tyler

Support staff

September 30, 2022 at 09:46

Hello,

We can’t log in to your Dashboard, please provide wp-admin access.
Also, we do not see any problem on mentioned pages. please describe the situation in more detail with screenshots.
What plugin do you use to create a multilingual site? Have you tried to contact their support?
How does it work when the default WC theme – Storefront is activated on your site?

Regards

#335469 Copied

Bas Kling

Participant

October 2, 2022 at 12:35

Hi Rose,

I’ll let our lead developer take care of the login request.
As for the problem, please review the video capture in Private area

We use TranslatePress as translate plugin, after tested Weglot (external, expensive after 2nd language), WPML, ridiculously slow, MultilingualPress (SEO issues, among other issues), Polylang, Loco (still using, combined with TP). TranslatePress support basically told us, the problem isn’t on their end; there’s probably an issue with either other plugins or the chosen template (xstore). Funny enough, the problem didn’t exist a month or so ago (many, many updates ago, as we’ve skipped a few xstore updates)

Staging copy with all of the plugins deactivated, except for Woocommerce, TranslatePress and Xstore, displayed same issues. Again, our lead developer can share more insights. He will contact you tomorrow.
Not sure if staging was tested with storefront…

Please contact administrator
for this information.

#335607 Copied

Bas Kling

Participant

October 3, 2022 at 10:28

The problem occurs when the VoyeurX – XStore Child (folder xstore-child) is active.
when a different xstore child theme is active or the xstore parent theme (with the default out-of-the-box settings) it works just fine.

The child theme only contains the screenshot.png file and style.css with the necessary headers to define the child-theme. So any conflicts in the php code of the child theme can be ruled out.

– When the translation editor of translatepress is active all text is in English.
– The missing translations are part of the same short product description field.

Please contact administrator
for this information.

#335664 Copied

Rose Tyler

Support staff

October 3, 2022 at 13:13

Hello,

We’ve checked your staging site, please see screenshots in the Private Content area

Regards

Please contact administrator
for this information.

#335674 Copied

Bas Kling

Participant

October 3, 2022 at 15:03

those screenshots are not from the supplied examples.
Also as previously mentioned. when testing the three provided examples at least 1 isn’t working correctly.
When just looking at 1 single page it occasionally can display correctly.

currently 2 of the 3 provided example url’s are partly in Dutch.

Please contact administrator
for this information.

#335693 Copied

Bas Kling

Participant

October 5, 2022 at 11:22

Almost 2 full days since the last feedback.
I hope you’re mid-troubleshooting (assisting)…?
Sorry to drive this a bit more aggressively than usual, but this is our production environment, and we are currently attending an international B2B fair. Our English-speaking prospects are being referred to our website.
We need this resolved!

#335847 Copied

Rose Tyler

Support staff

October 6, 2022 at 07:33

Hello,

Sorry for the delay in answering.
I’ve passed this topic to one of our developers, and I will let you know once get an answer.

Regards

#335897 Copied

Rose Tyler

Support staff

October 6, 2022 at 17:41

Hello,

Please check the reply in the Private Content area

Regards

Please contact administrator
for this information.

#335947 Copied

Bas Kling

Participant

October 6, 2022 at 20:03

migrations where done by wp migrate db pro (plugin by delicious brains – https://deliciousbrains.com/wp-migrate-db-pro/)

Spend another couple of hours today just testing different theme settings to figuring out what could be the cause and I found the following things.

when importing the settings from the live production site in to the settings of the xstore parent theme, the error also shows itself in the Xstore parent theme.

On removal of all elements from the header builder the issue seems resolved (manually removing each individual element, not using the header reset option).
when rebuilding the header it keeps working with the main menu and logo element present, when also adding the secondary menu (as third item) the issue seems to reoccur but less often.

When leaving the secondary menu element out of the header all the other header elements (desktop view, removed additional headers) can be used without issues.
with the exception of the secondary menu, checked all single products in the /en/leren-lingerie/ categorie, all without issue.

the moment I put the secondary menu element back in the header, the issue presents itself again.
(main menu, logo and secondary menu elements are placed in the bottom header)

When trying to work around the secondary menu usage and adding a couple of items to the main (mega) menu, while the secondary menu was still in the header the issue also seems to disappear suggesting it could also be caused by something inside the (mega)menu that is conflicting with translatepress.

#335950 Copied

Bas Kling

Participant

October 7, 2022 at 09:59

commenting on #335947
the video isn’t a long-term solution.
We’ve tried. do that for 10 products and before you’re done with the last product the first shows in Dutch again.

Also the not working product from screenshot KKangxHRd6nr
works perfectly fine when removing the secondary menu from the header builder.

—EDIT—
Previous communication between you and us is being managed by our web developer.
As the owner of the brand/website, I would like to emphasize that we are rapidly expanding into Europe, the US, and Canada region, ramping up from 20 to approx. 35/40 stores within the next 2 months.
If we cannot resolve the translation issue within the next few days/week (which,
as I understood from our developer, is XStore’s purview to help resolve), I’m afraid we need to explore other template providers, ending our collaboration with XStore.
This is definitely not our preference as we’ve been more than content with the template, support, and expertise. I’m sincerely hoping for XStore’s support in this.

#335989 Copied

Rose Tyler

Support staff

October 10, 2022 at 15:51

Hello,

The translation problem is related to the plugin you are using, because it stores translations in theme mods, which are unique for each theme and when switching to another, they are not saved, or are loaded with errors, the same will happen if you use different child themes even for the default theme (not XStore at all). When switching child themes, it will all fly off
so
it is better for you to switch to some other plugin for translation, we recommend WPML (but it is paid) https://xstore.helpscoutdocs.com/article/31-translation-with-wpml , and for this you will have to redo the translations, or you can use a child theme with which there are no problems

Regards

#336155 Copied

Rose Tyler

Support staff

October 10, 2022 at 16:00

We can see only 1 purchase from you. 1 purchase code can be used for 1 project, but you used it for a few sites.
If you want to use our theme for a few different projects you need to buy a few licenses.
Read more – https://themeforest.net/licenses/terms/regular

Regards

#336156 Copied

Bas Kling

Participant

October 10, 2022 at 16:40

Hello Rose,

We have only one production site in use, hence the one license.

Besides this, to troubleshoot current issues, we have two development sites running, clearly indicated by the .dev in the slugs.

There seems to be a lot of incompatibility in xtore’s code, working with TranslatePress. We rely on our developer as well as Xstore to troubleshoot and resolve these issues. In order to compare code we need both development sites.

If we need to decommission 1 of the development sites, we will do so, but then we would have to rely even more on your supper team to help us resolve the open tickets.
Indicating that we are expanding into the global market and the dire need for the translation /xstore incompatibility to be resolved ASAP, the reply that we get a license warning, really isn’t the response we were hoping for.
We hope you can appreciate our current position and help us out.

Thank you

#336160 Copied

Rose Tyler

Support staff

October 11, 2022 at 12:15

Hello @Bas Kling,

Thanks for the answer. It seems you have missed my reply – https://prnt.sc/Qmhus5TQmCrg
TranslatePress plugin does not come bundled with our theme, it is a 3rd party plugin. Please note that we do not give a guaranty for full theme compatibility with all existing 3rd party plugins, and additional customization is outside the scope of our basic support.
We tried to help you every time you contact us, but in the current situation, I can only repeat the reply from our dev team here: “The translation problem is related to the plugin you are using, because it stores translations in theme mods, which are unique for each theme and when switching to another, they are not saved, or are loaded with errors, the same will happen if you use different child themes even for the default theme ( the situation is independent of XStore). When switching child themes, it will all fly off
so
it is better for you to switch to some other plugin for translation, we recommend WPML (but it is paid) https://xstore.helpscoutdocs.com/article/31-translation-with-wpml , and for this you will have to redo the translations, or you can use a child theme with which there are no problems”

Regards

#336219 Copied

Bas Kling

Participant

October 12, 2022 at 15:29

Hello Rose,

we didn’t miss the reply, its just that we couldn’t do anything with it. The feedback felt like a standard answer since all the points you mentioned had already been tested and refuted. The point about changing the secondary menu was also ignored, beside the fact that you only tested 1 page at a time instead of the 3 / 10+ that we recommended.

TranslatePress stores the translations in a separate database table at string level, not in the theme mods as you claim. After all, translations simply work perfectly when the theme is changed.

Our developer screen-capped the entire topic and sent it to TranslatePress. Hopefully, they will know what to do with it.
For now, unfortunately, we are left with cutting out all elements that might pile on the incompatibility issues, hoping for the best.

#336312 Copied

Rose Tyler

Support staff

October 17, 2022 at 14:47

Hello,

We hope you will be able to solve this problem with the help of TranslatePress.
We can’t give another answer/solution in this case, unfortunately.
Sorry, but we also can’t give a guarantee for full theme compatibility with 3rd party plugins.

Regards

#336668 Copied

Rose Tyler

Support staff

October 17, 2022 at 16:57

Hello,

Back to your words, the problem may be caused by content inside the secondary menu or imported “multiple headers”.
If It is in “multiple headers” you need to resave each of them. And add secondary menu one more time. If the problem persists even after that, let us know what exactly menu is selected to display at the header > secondary menu element – https://prnt.sc/tsuRWjI6nxnF Another our specialist will try to solve the problem, but it will not be fast, unfortunately.

Regards

#336680 Copied

Bas Kling

Participant

November 3, 2022 at 13:25

Hi Rose,

we’ve rebuilt the multiple headers per your suggestion, and the problem seems to have gone for now. We’ll keep monitoring closely as we develop the other languages.
Thank you

#337807 Copied
Tagged: critical issue, erratic, translated product texts, visibility, woocommerce, wordpress
Viewing 19 results - 1 through 19 (of 19 total)

The issue related to '‘CRITICAL ISSUE: Translated product texts visibility erratic’' has been successfully resolved, and the topic is now closed for further responses

CRITICAL ISSUE: Translated product texts visibility erratic

Recent Topics

Helpful Topics

Useful links WooCommerce & WordPress

Browse by popular tags:

Explore our best WordPress WooCommerce Themes collection