Bug Report: Manual edits to post translations are not displayed

stefan

New member
Hello,

I’ve discovered another issue with Lutish Ultimate Multi Host System.

When I manually edit an existing translation, the changes behave differently depending on whether I’m editing a thread title or a post.

Thread titles:
Manual changes are saved and immediately visible on the frontend. Everything works as expected.

Post content:
When I manually edit the translated text of a post and save the changes, the updated translation is not displayed on the frontend. The previously translated content remains visible.

I’ve already cleared and rebuilt all available caches through the XenForo Admin Control Panel, but this has not resolved the issue.

Expected behaviour:
Manually edited post translations should become visible immediately after saving, just like manually edited thread titles.

Could you please investigate whether post translations are being cached separately or whether the frontend is not retrieving the updated translation correctly?

Thank you for your help!

Best regards,

IMG_1236.webpIMG_1237.webp
 
Manual edits are saved immediately, but the front end serves translations from a cache with a one-hour lifetime. This is a deliberate design choice: translations are cached per content item (thread, post, forum) and per language, so the number of cache entries grows with your content and language count. Keeping a fixed, bounded lifetime lets those entries expire on their own without the translation cache having to be invalidated on every write — invalidating on every edit would tightly couple the write path to a cache structure that scales poorly on large forums, and would push Redis memory usage up with every post and language.

From a performance-design standpoint, we can't do immediate cache invalidation here either. If we did, every post or thread would end up with its own unique cache key — and as the dataset grows, even Redis wouldn't be able to handle that volume. For example, 100K posts × 10 languages works out to nearly 1 million keys.

For small sites, this isn't a problem at all — the number of cache keys stays well within what Redis can handle. But we expect our customers to grow into large communities, so that approach just isn't suitable.

The edited translation will appear automatically without an hour, with no action needed. Clearing XenForo's own caches does not affect this translation cache, which is why that had no effect.
 
Last edited:
Hi,

Thank you for your explanation.

Unfortunately, the issue still persists, even after several hours, well beyond the stated one-hour cache lifetime.

The manually edited translation is correctly saved and displayed in the Lutish ACP backend. However, the public frontend continues to display the old translation.

Interestingly, manual changes to thread title translations appear immediately, while changes to post translations are not reflected in the frontend.
Could you please investigate why the frontend continues to serve the old post translation even after the cache should have expired?
In particular, could you check whether the frontend is retrieving the correct translation record and whether the cache is actually expiring and being rebuilt with the updated content?

Would it also be possible to add a manual translation cache refresh feature? For example, a button in the ACP that allows administrators to selectively refresh the cache for a specific post and language.
Alternatively, a scheduled cron job to periodically refresh or clear expired translation cache entries could also be a useful solution.
My main concern is ensuring that manually corrected translations appear promptly on the frontend without having to clear the entire XenForo or Redis cache.

Thank you again for your support!

Best regards,
Stefan
 

Attachments

  • Bildschirmfoto 2026-11-21 um 22.34.23.webp
    Bildschirmfoto 2026-11-21 um 22.34.23.webp
    149.6 KB · Views: 2
Back
Top