[Closed] Internal links not pointing to translated content

Thank you for the reply, and I appreciate you getting back to me.

I'll go ahead and install the theme and get the plugins installed. I don't necessarily think that it's fair to expect me to replicate this issue in your test environment from scratch. In particular since it's a blank website without even the WPML plugin set up, not to mention creating sample content, and then translating it. It's not as simple as pasting in my XML code and adding a couple of elements. We're all professionals with lots on our plates and I've sunk more of my time than I care to admit but unless there is an error on my end as the user, something in the documentation I am not following (I've read I think every piece of info in your documentation, many parts several times) or if the theme/plugin publisher is not doing something properly in setting up these elements (they say they are properly flagging these URL fields as translatable links, is this true or are they mistaken?), then I have to think that there is a bug happening somewhere.

You can check my implementation of the XML code as shown here as the edit did not seem like it was given to me in a way that was directly paste-able into the field as it as an edit to a previously provided snippet of XML: https://wpml.org/forums/topic/best-practice-guidance-on-internal-links/page/3/#post-15176628

I've tried other minor variations in case my implementation was not as intended by the devs (again, please go back and confirm) but this is what I have there currently:

<wpml-config>
<shortcodes>
<shortcode>
<tag>nectar_icon</tag>
<attributes>
<attribute>title</attribute>
<attribute type="link">url</attribute>
</attributes>
</shortcode>
</shortcodes>
</wpml-config>

Theme and plugins are otherwise installed and activated.

I'll say again that this was all initially tested and set up in the fall of 2023 and working correctly before an update changed this. On my site, I have tried deactivating ALL other plugins and the issue persists so I think it's narrowed down to being between these nectar elements and WPML but I am open to suggestions. I've since reactivated some of the plugins to return to basic functionality but am happy to test any other ideas here.

Thanks again for your time on this!
Brad

Thank you for doing some of the initial legwork to get a sandbox started.

I tried temporarily removing the XML to see if it was in fact addressing the issue, then reinserting it. I'm not sure if it is showing as not pointing to the english translation from the french page or not for you but that is what I am currently seeing. I don't know what cache settings might exist but I was careful to not populate any of the URL translation fields.

To be honest, the icons are only about 2% of my problems, where it's mainly the call-to-actions used throughout where I am seeing the same issue.

I also tried reproducing the nectar slider with a button pointing to the same post as a test and see the following (see attached) where the URL was automatically copied and is not being flagged as I think it should (dynamically in the background, hidden from view unless searched in the translation editor).

I think the common thread here is the way these URL's are input so I am also confirming with themenectar support that these are setup to be handled correctly. Can you please confirm that you are seeing the same behavious as I am, where the XML is in place as it should be, yet the URL still points back to English version only?

Thanks in advance,
Brad

Thank you Long, appreciate the follow up! I am on a work retreat and am commenting to keep this ticket from getting stale. I am hopeful in getting this implemented and will report back.

Thanks again!

My apologies! I had gotten the new password string but sent this without submitting the change. Should work now.

Thank you for your patience!
Brad

Thank you Long, I will take a look and try to replicate with the CTAs as they are the main pain point for me. Thanks again, will follow up (sending this reply to keep from getting closed...) Have a nice weekend.

Thank you for taking a look Long, that's great that it's working for the new test page.

What is different or special about the implementation about any of the occurrences on the actual content pages? I've been deleting and re-adding them without any luck and that is the core of my issue. To my knowledge, the implementation follows all the available documentation so I'm looking for guidance here.