Subject: Translation issues with link texts, spoiler titles and add-on phrases, Forum categorie + feature request

stefan

New member
Hi @lutish,

I have noticed several issues with the multilingual translation system on my XenForo forum and would also like to suggest an improvement.


1. Link texts and spoiler descriptions are not being translated

The visible link text remains in German on the English, French and Spanish versions of the forum. Spoiler titles and descriptions also remain in German instead of being translated.

Example:
https://urlvanish.com/890d8b27

The URLs themselves should remain unchanged, but the visible link texts and spoiler descriptions should be translated into the respective language while preserving the BBCode structure.


2. Language-specific phrases from third-party add-ons

I have also noticed an issue with phrases from third-party add-ons, such as those developed by WuTime or AndyB.

Only the first language appears to be translated or displayed correctly, even though individual translations for all other languages have already been created and saved in XenForo.

Could you please investigate why the existing language-specific phrases are not being used correctly for the other languages?

The multilingual system should respect the translations already stored in XenForo and display the appropriate phrase for the currently selected language.


3. Forum categories are detected but not translated

Forum categories are correctly detected and displayed in the Translation Manager with their original master-language names. However, the category names are not being translated into English, Spanish or French.

Since these categories are already recognized by the Translation Manager, I would expect their names to be translated into all configured target languages.


4. Feature request: Immediately queue new threads and posts

I would like to suggest automatically adding newly published threads and posts to the translation task manager immediately, rather than waiting for the next discovery cycle.

Ideally, the system would:
  • Automatically create translation tasks as soon as a new thread or post is published.
  • Queue the content for all configured target languages.
  • Allow the existing translation worker to process these tasks directly from the queue, without waiting for another content-discovery scan.
This would significantly reduce the delay before newly published discussions become available in other languages.

Thank you for your continued work on the add-on. I would appreciate it if you could investigate these issues and consider the suggested improvement.

Best regards
 
Last edited:
Hi,

Thanks for the detailed feedback. Here is where each point stands:

1. Link texts and spoiler descriptions
This is intentional. URLs and email addresses inside posts are treated as protected blocks: the link target and any brand-related vocabulary are deliberately kept untouched so that every language version points to exactly the same URL with consistent anchor wording, instead of each translation rephrasing the link text. The same protection covers the spoiler tag's title attribute. URLs themselves are never modified in any language version.

2. Phrases from third-party add-ons
The multi-host translation system translates content (threads, posts, resources, nodes) through its own translation pipeline and does not touch the XenForo phrase system. Static phrases shipped in an add-on's phrase.xml are plain XenForo phrases: their translations must be added per language in the ACP (Languages → Phrases), exactly as in a single-language setup. If translations you already saved in the ACP still do not show for the other languages, please run a phrase rebuild first (Tools → Rebuild caches), since the phrase map is an aggregated cache — that resolves most "saved but not displayed" cases.

3. Forum categories
Appearing in the translation manager only means the category was detected as translatable content — it does not mean a translation task was already queued. Task creation follows the discovery cycle, and processing follows the task queue. Please check the translation tasks table (status / error message) for entries with content_type = category; if tasks exist and are pending, they will be picked up by the worker, and if any show as failed the error message will tell us exactly why.

4. Immediately queueing new threads and posts
We deliberately do not enqueue content for translation at publication time. On an active community generating hundreds or thousands of messages per day, immediate per-post enqueueing would flood both the translation API quota and the job queue, which is not sustainable on typical server hardware. The discovery cycle plus the continuously draining task queue keeps the delay bounded to one scan interval while providing natural backpressure. We may revisit a lightweight prioritization path in the future, but it will remain batch-based rather than per-message.

If you want to translate a specific piece of content right away, you can specify it under Tools → Rebuild Caches → Rebuild Translations in the admin panel. It will be queued and processed almost immediately.

Best regards
 
Last edited:
Hi Lutish,

Thank you for your detailed explanation and feedback. Here is my response to each point:

1. Link texts and spoiler descriptions
I understand that the current behaviour is intentional. However, I would appreciate optional settings to translate visible, human-readable link texts and spoiler titles while keeping URLs and technical elements unchanged. For example, Weitere Informationen should become Further information in English. Similarly,
Text
should become
Text
. Vehicle names, usernames and technical identifiers must remain unchanged. German link descriptions and spoiler titles within otherwise fully translated pages look inconsistent, particularly for international visitors. Ideally, both translation options could be enabled independently.

2. Phrases from third-party add-ons
The English, French and Spanish phrase translations are already correctly configured in the XenForo ACP. I have also confirmed that the Wutime AdBlock Detector Pro language issue occurs on other forums where Ultimate Multi Host System is not installed. Therefore, this issue appears unrelated to your add-on, and I am investigating it separately with Wutime.

3. Forum categories
Thank you for clarifying the translation process. This is no longer a priority for me, as forum categories only need to be translated once and I will translated them manually.

4. Immediately queueing new threads and posts
I understand your concerns about immediately creating individual translation tasks for every new post. The existing batch-based system is perfectly fine as long as newly published content is discovered and translated within a reasonably short period. However, an optional prioritisation of new threads and posts within the existing queue would be a useful improvement, especially for international visitors who want to read the latest discussions in their preferred language.

Overall, I am currently using GPT-4o-mini with my detailed translation prompt, and the translation process is working very reliably. My main remaining request is therefore the optional translation of visible link texts and spoiler titles to provide a more consistent multilingual experience.

Thank you again for your continued development and support. I would appreciate your feedback on whether these improvements could be considered for a future update.


Best regards,
Stefan
 
1. Using the same link with multiple different text, alt, and title values across different pages is very likely to have a negative impact on SEO — so this idea cannot be considered.
2. Please consider rebuilding the language cache.
3 and 4. Please use Tools → Rebuild Caches → Rebuild Translations to quickly to get result.
 
Last edited:
Hi Lutish,

Thank you for your reply. I would like to clarify a few points:

1. Link texts and spoiler descriptions

I respectfully disagree with your SEO assessment. Google's official documentation recommends descriptive, relevant anchor text and appropriate language usage on multilingual websites. There is no general Google guideline requiring identical anchor text for the same destination URL across different languages. Translating "Weitere Informationen" into "Further information", "Más información" or "Plus d'informations" while preserving the exact destination URL is normal multilingual behaviour and does not inherently harm SEO.

Furthermore, these links are primarily part of user-generated content (UGC) in forum posts. Google explicitly supports identifying such links with rel="ugc". Translating their visible anchor text into the visitor's language while preserving the original URL does not inherently create an SEO issue. Of course, rel="ugc" is not a guarantee against SEO problems, but it helps Google identify the nature of these links.

Google's official documentation:
https://developers.google.com/search/docs/crawling-indexing/links-crawlable
https://developers.google.com/search/docs/advanced/guidelines/qualify-outbound-links
https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites

I am not asking to modify URLs, technical identifiers or protected content, only human-readable link descriptions and spoiler titles. Could you reconsider implementing this as an optional feature, disabled by default and enabled entirely at the administrator's own risk? This would allow administrators to make their own SEO decisions without changing the default behaviour for other users. Ideally, link texts and spoiler titles could be enabled independently.

2. Phrases from third-party add-ons

Thank you. I will check the language cache rebuild. However, I have already confirmed that the Wutime AdBlock Detector Pro language issue also occurs on forums without Ultimate Multi Host System, so I am investigating this separately.


4. Immediately queueing new threads and posts

I do not want to manually run "Rebuild Translations" every time new content is published. My forum has not yet been fully translated, so there is still a substantial backlog of older threads and posts. As a result, newly published content is not prioritised and may have to wait behind thousands of existing translation tasks.

What I am requesting is an automatic prioritisation mechanism for new threads and posts within the existing batch-based translation system. New content should be translated first, while the remaining backlog continues to be processed in the background. This should happen automatically during the regular discovery and worker cycles, without manual intervention or creating an individual API request immediately upon publication.

I believe this would significantly improve the experience for international visitors, who should be able to read the latest discussions in their preferred language without waiting for the entire forum archive to be translated.

Thank you for considering these suggestions.

Best regards,
Stefan
 
1. Google's Penguin algorithm has dealt heavy penalties for anchor text manipulation, over-optimization, and keyword stuffing. I can't afford to apply that kind of uncertainty to the extension's URL handling — better too little than too much. I'm also not sure whether Google can reliably distinguish URLs across multiple languages, so the current approach will stay unchanged until that's confirmed.
2 -
4. that is easy to do that ,i will change order by to DESC for ALL. waiting next version.
 
Back
Top