[Feature Request] problems with links

Hello,

My apologies, but I am not fully understanding your last message "deactivation of the module and the cancellation of the related charges".

Do you refer to costs for automatic translation?

Usually, there should not have been any charges here, as internal links are adjusted automatically.

Further, the kind of module does not really matter when it comes to costs for automatic translations. What counts are the text segments inside the Advanced Translation Editor. If you use the same text in another module, you will not get charged, as the Advanced Translation Editor's translation memory will autocomplete such translations.

About the issue:

The issue here was that WPML did not send the links for the Avada Title Widget to the Advanced Translation Editor, which is why I provided a custom XML configuration that makes those links available inside the Advanced Translation Editor.

This means that now you will need to update the original contents and then update the translations.

Internal links should point from there on automatically to the translated destinations in each language, unless these links have been altered inside the Advanced Translation Editor.

If you would like me to investigate this further, please allow me admin access to the site so that I can revise why the links are not translating as expected.

The private reply form is enabled again.

Best regards
Andreas

My apologies in case I am understanding correclty, but do you mean that you decided not to use WPML any longer for your project and you would like to ask for a refund for the 99€ subscription fee?

If so, please request a refund on the following page:
https://wpml.org/purchase/refunds/

In case you plan to continue working with WPML but would like to ask for a refund for translation credits, please take note that such credits are usually not refundable.

If you can confirm any bug that caused unjustified charges of automatic translation credits, we can credit the account with new credits as compensation, but we need to be able to verify that such charges actually occurred.

Your site currently has 194.957 credits, which will still be billed at the beginning of the next month.

Note that the issue about internal links does not require any credits for translation. WPML will adapt internal links automatically and does not translate them using automatic translation engines.

I can offer again to take a look into the issue, if you can provide access to a staging site or provide a package of the site (Duplicator or WP All in One Migration) on which you removed any sensitive data.

This is the only way I would be able to run tests and identify what, in your specific case, is going wrong and provide a solution.

If the issue persists, it might be due to a missing or incomplete XML configuration for specific page builder widgets, or maybe someone translated links inside the WPML Translation Editor and entered the wrong target URL. We can provide solutions in such cases, but we need to know exactly how the content was created, which modules are affected, and which XML Configuration is used.

For example, an internal link might fail in some cases if you did not use a complete URL in a module or if the URL has some additional parameters.

Also, internal links will only then point to a second language if a translation for the content that you are linking to has been published.

You further find a dialog at WPML > Settings > Adjust link targets, which can be used to solve internal link issues.

Also, always verify if such issues could be cache-related (see Redis Object Cache and WP Super Cache).

Furthermore, according to the provided debug information, the site is not using the latest versions of WPML. You can find updates for WPML at Plugins > Add new by clicking on the "Commercial" tab and then clicking "Check for Updates".

Something you could do from your end, after making sure that everything (theme and all plugins) is updated:

Create a localhost copy or staging site and try running it with a minimal setup to see if the issue persists:

1) Deactivate all additional plugins that are unrelated to WPML and our add-ons. Now test again. Make sure to edit the original content, save it, and then save the translation again inside the WPML Translation Editor.

If the issue persists, then we need to have a look at the content, the settings, and the existing translation.

2) If the issue disappears, start by reactivating the plugins individually or reactivating them in small groups. This way, check where the issue recurs to identify the plugin causing the issue.

3) If this doesn't resolve the issue, please switch to a standard theme like Twenty Twenty-One to see if the issue might be theme-related.

Once we identify the cause, we can then attempt to replicate the issue and then escalate it internally. In this case, I'll provide a test site with WPML.