|
"I noticed that when I change in WPML the property type to not translated, then the proeprty type that mains only active is the french. Also the problem occurs not only in the home page hpml widget but also n every saved template I have in proeprties again at the html widget, lastly, th elocation taxonomy has the smae problem, at the properties at the upper left corner where the city link appears"
that new detail changes the diagnosis quite a lot.
What you are describing now points much more strongly to a taxonomy translation configuration / taxonomy mapping problem inside WPML, not just an Elementor HTML-widget problem.
Why:
When you set the taxonomy to “Not translatable” and WPML leaves only the French version effectively active, that suggests WPML’s stored language relationships for those taxonomy terms are already inconsistent or the site’s taxonomy language setup is no longer aligned with the current default-language structure. WPML has documented multiple fixes around taxonomy term synchronization and incorrect translated term behavior in past releases, including issues where taxonomies or terms were not synchronized correctly depending on language/default-language conditions.
Also, the fact that the same issue appears in:
homepage HTML widgets,
saved Elementor templates,
and the property city link shown dynamically on single property cards/pages
means the problem is not limited to one widget’s raw HTML. It is affecting both:
manual taxonomy links inside HTML, and
dynamic taxonomy permalinks generated by the theme/plugin.
That is the biggest clue.
What this most likely means
At this point, the strongest candidates are:
1. Corrupted or mismatched WPML taxonomy translation records
for property-type and property-city.
Because the issue now affects dynamic city links too, WPML is likely resolving taxonomy terms through its internal term-language mapping and returning the wrong language permalink.
2. Wrong WPML setting for those taxonomies
such as a bad combination of:
translatable / not translatable,
display as translated,
taxonomy slug translation,
existing translated terms that should no longer exist.
3. A RealHomes + WPML compatibility path
for property city/property type links that still reads translated term mappings even after you changed settings.
The most important conclusion
Because the upper-left city link on properties is also wrong, this is no longer just:
“WPML rewrites URLs inside Elementor HTML.”
It is now more like:
“WPML thinks the active/target language version of these taxonomy terms is French, or the taxonomy term translation table is inconsistent.”
That fits your observation far better.
What I would do now
1) Do not keep property-type or property-city as “Not translatable” yet
If switching them to not translatable causes French to remain as the effective surviving version, that is a bad sign. Leave them in the normal translated mode for now until the mappings are cleaned.
2) Inspect WPML taxonomy translations directly
This is now the next proper step.
You need to inspect records for:
tax_property-type
tax_property-city
inside wp_icl_translations
You are looking for:
English terms whose source/default language mapping is broken
French terms incorrectly acting as originals
missing English originals with French as the canonical row
duplicate translation groups (trid) for the same logical term
3) Check WPML Taxonomy Translation screen carefully
Go to WPML’s taxonomy translation interface for both taxonomies and confirm:
which language WPML thinks is the original for each term
whether English terms actually exist as originals
whether French/German terms are attached to the correct English source terms
whether slug translations are mismatched
WPML notes that taxonomy slug translation exists as a separate capability, so wrong slug-language pairings can also contribute to bad term URLs.
4) Re-save the affected English terms
For a few affected property types and cities:
open the English term
update slug/name without changing meaning
save
then verify attached French/German translations
This can sometimes expose whether WPML is treating the wrong language as the source.
5) Rebuild one affected Elementor template translation manually
WPML support has specifically noted that links inside Elementor widgets / HTML / similar structures sometimes need manual correction in the translation editor, and that auto-adjustment is not always enough.
But in your case, this is now a secondary symptom, not the root cause.
My current diagnosis
Based on everything together, I would rank the causes like this:
Most likely: broken taxonomy language mappings in WPML for property-type and property-city
Second: RealHomes theme pulls taxonomy permalinks through WPML using those broken mappings, so dynamic city/type links come out French
Third: Elementor HTML widgets/templates are separately inheriting the same wrong taxonomy target language during translation/render
What not to waste time on anymore
I would stop testing:
JS click fixes
CSS tricks
cache-only theories
more homepage-only fixes
more wp_footer URL rewriting
HTML widget wrappers like notranslate
Those are not the root issue if dynamic property city links are also wrong.
|
