You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just updated to the latest Typhoon release, and noticed that if the Active Theme is not Typhoon (mine was set to Quark) raw language strings are shown in the Typhoon settings page. However, if Typhoon is made the Active Theme then language strings are shown as expected.
Below is what I see when Typhoon is not the Active Theme:
If any more info etc. is helpful please let me know.
Thanks very much,
Paul
The text was updated successfully, but these errors were encountered:
This is actually a known issue of Grav admin plugin, and not Typhoon. If not active, it's similar to a plugin being disabled. Basically languages are not loaded. Also any custom fields are not loaded, so I think the best option is to not show config unless enabled/activated.
rhukster
transferred this issue from getgrav/grav-premium-issues
May 5, 2021
rhukster
changed the title
[Typhoon] raw language strings displayed when Typhoon is not Active Theme
Raw language strings displayed when theme is not the active theme
May 5, 2021
We can see the same problem affecting sites which skipped many releases and were recently upgraded to latest Grav release. However, in these sites admin literally everything is looking like that, including all admin menus and buttons. We have checked site settings etc and everything looks fine, yet, the default (en) language is simply not loaded in the admin panel at all.
I just updated to the latest Typhoon release, and noticed that if the Active Theme is not Typhoon (mine was set to Quark) raw language strings are shown in the Typhoon settings page. However, if Typhoon is made the Active Theme then language strings are shown as expected.
Below is what I see when Typhoon is not the Active Theme:
If any more info etc. is helpful please let me know.
Thanks very much,
Paul
The text was updated successfully, but these errors were encountered: