Actualización forzada en clientes tras cambios administrativos

riking · 9 Noviembre, 2020 05:34

If you’re in a plugin, either use refresh: true in your site_settings.yml or Discourse.request_refresh!.

lib/discourse.rb

af4938baf


      
          def self.request_refresh!(user_ids: nil)
            # Causes refresh on next click for all clients
            #
            # This is better than `MessageBus.publish "/file-change", ["refresh"]` because
            # it spreads the refreshes out over a time period
            if user_ids
              MessageBus.publish("/refresh_client", 'clobber', user_ids: user_ids)
            else
              MessageBus.publish('/global/asset-version', 'clobber')
            end
          end

Tema		Respuestas	Vistas
Enforcing Hard Refresh Support	2	449	13 Julio 2021
What does refresh: true in settings.yml mean? Dev	3	52	28 Julio 2025
In a plugin, how can I force clients to re-load extra-locales file? Dev	16	609	22 Julio 2022
'discourse remap' ought to notify app servers of any site settings that changed Bug	3	508	23 Abril 2018
Moderators can see the "Force Browser Refresh" but can't use it Bug	4	743	20 Febrero 2019

Actualización forzada en clientes tras cambios administrativos

Temas relacionados