Alan Guo Xiang Tan d460229ed8

FIX: Update themes javascript cache after running themes migrations (#25562) ...

Why this change?

This is caused by a regression in
59839e428f3dc49213fedfd8b67acb9f2a5ec69a, where we stopped saving the
`Theme` object because it was unnecessary. However, it resulted in the
`after_save` callback not being called and hence
`Theme#update_javascript_cache!` not being called. As a result, some
sites were reporting that after runing a theme migration, the defaults
for the theme settings were used instead of the settings overrides
stored in the database.

What does this change do?

Add a call to `Theme#update_javascript_cache!` after running theme
migrations.

2024-02-05 14:35:11 +08:00

..

assets

FIX: Handle old Firefox versions that do not support isConditionalMediationAvailable (#25549)

2024-02-02 16:39:37 -05:00

controllers

DEV: Update confirm-email flows to use central 2fa and ember rendering (#25404)

2024-01-30 10:32:42 +00:00

helpers

SECURITY: Properly escape user content within <noscript>

2024-01-30 09:10:09 -07:00

jobs

DEV: Drop deprecated Badge#image column (#25536)

2024-02-02 14:09:55 +08:00

mailers

FIX: Add higher read & open timeouts for group SMTP emails (#24593)

2023-11-28 15:32:59 +10:00

models

FIX: Update themes javascript cache after running themes migrations (#25562)

2024-02-05 14:35:11 +08:00

serializers

FIX: Preload sidebar categories when lazy loading categories (#25332)

2024-02-02 10:35:15 +02:00

services

DEV: Trigger DiscourseEvent on push notification send (#25375)

2024-01-22 15:30:35 -06:00

views

SECURITY: Properly escape user content within <noscript>

2024-01-30 09:10:09 -07:00