[Résolu] Front end content for product single translation not showing

[Auteur]

Publications

[bjhdesign]

Hi there,

after updating, the front end for single product doesn't show any content any more.

Example:

DE: lien caché
EN: lien caché

The page for the German version is working, but the English pendant isn't showing any content. But in the back end, all data is available for both languages. Where's the problem?

Regards
Björn

[Minesh]

Hello. Thank you for contacting the Toolset support.

I see you created duplicate ticket for the same issue.

You are welcome to close this ticket and we will continue with the following ticket:
=> https://toolset.com/forums/topic/front-end-content-for-product-single-translation-not-showing/

[Minesh]

Hello. Thank you for contacting the Toolset support.

Can you please share admin access details so I can check whats going wrong with your setup.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually 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 and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

[Minesh]

When I load the page: lien caché
=> It looks like nothing was found at this location.

It looks like you have added the geo-location filter? Can you please tell me where you added that and also tell me for what field exactly the translation is not working. Maybe you can send me few screenshots that should help me to understand your issue.

[bjhdesign]

Yes, when you load the page, it looks like nothing was found at this location. But if you have a look at the corresponding entry in the back end, the data is all there (see screenshot). Also the German and English version are connected in WPML.
I don't know what you mean with geo-location filter.

[bjhdesign]

Any news?

[Minesh]

Can you please check now.

I've copy the original language content template content to your secondary language content template (En) and I can see its working as expected.

Can you please confirm it works as expected now.

[bjhdesign]

Now, the english pages work, but the german ones don't anymore!
Examples:
lien caché (ERR_TOO_MANY_REDIRECTS)
lien caché (page not found)

[Minesh]

Please check the following:
- lien caché
- lien caché

Please check your custom post type slug. I see for post type Product the slug for both language is products:
=> lien caché
[Under section "Post Types Translation"]

[bjhdesign]

I checked the settings for Post Types Translation as you said, but it looks correct to me (see screenshot).

DE (original) = produkte
EN = products

[Minesh]

I'm not sure whats going on as with the same section I see the original language slug is set to products.

Please check the following screenshot: lien caché

I even see with products slug, both original language post and secondary language post is working as expected.
- lien caché
- lien caché

[bjhdesign]

I can see that the slugs in the front end is /products/ for both languages.
But why. According to my settings it should be correct.
What's going on? Do you have any approach to fix this problem?

[Minesh]

According to the screenshot I shared before: lien caché

The slug for post type product is set to products for both the languages. I do not see produkte.

On the following WPML settings for post types section:
=> lien caché

I see the slug products are assigned to both languages. I'm not sure why you see prokukte slug

[bjhdesign]

In the Toolset settings for the Produkte post type
lien caché
the slug is set to "produkte" as you can see in the screenshot. Why is WPML using "products". And: I still see "produkte" in the WPML settings.

[Minesh]

It looks like there is something to do with the redirection plugin where you added the redirection rules.

For now, I just disabled the redirection plugin and I can see now results with the following URLs:
- lien caché
- lien caché

Please clear your browser cache and history before you run test.