We’ve created a custom JS method for some custom locale work that loads the browser side I18n object with a custom attribute. I want to trigger a re-evaluation of this JsLocaleHelper method on each of the dependent clients. I’m trying to find a way to trigger this from server side. This used to work but seems to have changed recently. The data is correct when I delete the local client cache from the browser, but obviously this is not tenable for production use. It proves the issue is the local caching though. Things I’ve tried include: Discourse.request_refresh! or the more targetted: Discourse.request_refresh!(user_ids: user_ids) which appears to force refresh on navigate. However suspect the script is being cached so this is not a solution. Any help appreciated!

[image] Robert: Discourse.request_refresh! or the more targetted: Discourse.request_refresh!(user_ids: user_ids) Note that this function behaves very differently when the user_ids parameter is present and when it’s not. Did you try MessageBus.publish "/file-change", ["refresh"] ?

[image] Richard - Communiteq: Did you try MessageBus.publish "/file-change", ["refresh"] ? Excellent idea, that works! Thanks But is it scalable?

Nope, I don’t think so :frowning:

That helps a lot though I will continue digging. If I can find a flavour of that that spreads over time we may be good to go. Although it would be nicer to target the exact file.

OK, so between a rock and a hard place here. Here’s what I’ve learnt: The extra-locales bundles are added as script tags. They contain a version parameter that depends on the name of the bundle The version number is only evaluated at bootstrap I believe, so will remain cached until: you force the clients to completely refresh, which can only apparently happen en-masse? you restart the server or a client clears their browser cache This is unfortunate to say the least, that there is not more granular control. Could we introduce a “total refresh” on nav message?

I just tested Discourse.request_refresh! and it does seem to be reloading all javascript assets on the next navigation. It might not be triggering a JsLocaleHelper refresh, I am not sufficiently informed on how that works.

There’s a subtle thing going on. the “200” is actually “200 (cached)” which is browser side. Good Stack Overflow post about it.

Argh…:scream: … didn’t check that.

Thanks. Yes I have. I believe that’s just server side and does not change the version number on the provided JS file set up during bootstrap. Server side there is no issue. I’m considering moving this data to the site object and serializer so see if I can have more control.

In a plugin, how can I force clients to re-load extra-locales file?

Development

gerhard (Gerhard Schlager) July 22, 2022, 11:39am 10

Did you try to call ExtraLocalesController.clear_cache! after you make changes to extra-locales? It should recalculate the version during the next request.

Topic		Replies	Views
Force refresh on clients post administrative changes Feature	3	732	November 9, 2020
Unable to see i18n strings during development Development	2	199	October 29, 2024
Hot reload for plugin development? Development	19	2996	October 23, 2021
Client fails to fall back to English locale for admin_js and wizard_js Bug	2	870	May 24, 2019
Enforcing Hard Refresh Product Support	1	515	July 13, 2021

In a plugin, how can I force clients to re-load extra-locales file?

Related topics