• Resolved nonopnt

    (@nonopnt)


    Hey there, im stuck with some SEO issues due to some missing translations. Let me explain, im using Oxygen builder to build all the pages, and TP to translate the content. Through the backend all strings, links are properly translated from FR to EN.

    In major cases translations seems to be okay. But on the homepage there are links that is not being translated.

    For example, through the mega menu here that show the wrong URL : https://ibb.co/C0RcFzj (wordpress generated native menu) the Press page has ? …/presse ? for FR original url. The translated version of the page are ? …/press ?. By switching FR to EN from the language switcher, the page are in the correct URL, but through the menu the displayed URL stills ends with the FR version as follow ? /en/presse ?.

    French version : /presse
    English translated version : /press
    Displayed URL in the menu : /en/presse (doesn’t exist URL)
    This critical translation issue generates 301 redirection to /en/press

    I’ve tried to use the TP functions to check if the page link are properly translated using the following with it’s page ID :

    $url_converter->get_url_for_language(‘en_GB’, ‘THE_ID_TO_TEST’)
    but the URL returned is still the wrong one. It doesn’t return the ? /en/press ? URL.

    Another example here
    The FR original link is : https://danenberg.fr/collection/bijoux/bagues-bandeau/
    The translated EN version set properly in the backend are : https://danenberg.fr/en/collection/jewelry/bandeau-rings/
    The displayed EN version of the URL in the homepage are : https://danenberg.fr/en/collection/bijoux/bagues-bandeau/
    This should be the translated version (https://danenberg.fr/en/collection/jewelry/bandeau-rings/) instead…

    Activating the debug mode only shows those https://ibb.co/wwhcc6r but without any indication on the serveur problems or anything. I’m literally stuck with those URL problems.

    Let me add that I already send paid support ticket with my pro licence through https://translatepress.com/support/open-ticket/ and still unresponded.

    Thanks a lot for your help!

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Anghel Emanuel

    (@anghelemanuel99)

    Hello there,

    Thank you for reaching us!

    From what I checked,you received a response from me and it seems that you saw the reply.Here is what I mentioned:

    “Hello there,

    Thank you for reaching us!

    Since this looks a lot like a conflict with some other code, the first/next recommended step is the conflict test (ideally in a staging environment):

    *Briefly* disable all other plugins and enable the default Twenty Twenty One theme. Please also disable all add-ons. If this fixes the problem, as it probably will, enable everything one by one, checking each time to see when the problem returns.

    Please let us know when you find the conflict so that we can take a look and see what we can do about it.”

    Please follow the steps I provided to you previously and we can continue the discussion on our platform.

    Kind Regards,

    Thread Starter nonopnt

    (@nonopnt)

    Hey there, thanks for your reply. Seems that by email we didnt’ received your communications, thats the reason why I tried this way.

    I’ve mounted a preproduction environment to achieve extensions deactivations and see what changes, but actually nothing has changed.

    What I can see is that through the backend It’s like I cannot translate some <a> tags. As you can see on the following capture : https://ibb.co/5KwSJBZ in orange it shows the French URL version without any possibilites to change this URL to EN version manually (the URL is on the entire blue dashed block).

    This bloc is made through the oxygen builder slider. I’ve first took a look on the term slug through the String translation tab to see if the slug was translated properly and it does as you can see there : https://ibb.co/2Z8nxXd

    Is there any chance to make those contents appears translated ?

    Thanks for you help,

    Plugin Support Alex

    (@alexcozmoslabs)

    We need to take the pulse of this ticket. Is it still relevant?
    In the meantime, I set this ticket as Resolved. You can also change its status back to unresolved and let us know by replying to this topic if your request still needs attention.
    However, we encourage you to leave this ticket as it is and open a new one where to mention the issue again and ask for support. You can mention the link to this thread in the new ticket.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Not translated links’ is closed to new replies.