| Summary: | Fallback theme can appear instead of default theme | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Tim Buschtoens <tbuschto> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | 1.5 | ||||||
| Target Milestone: | 1.5 M6 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Tim Buschtoens
Created attachment 211907 [details]
Qiuck fix
When you enter a new URL the HTTP session is the same. Session store is not cleared in the GET request, but in the first POST. As a result, StartupPageConfigurer#addThemeDefinitions gets the previous "current" theme from the session store and send it to the ThemeStore.js together with fallback theme. In the first POST request the session store is cleared, the correct current theme is determined and set, but it is missing from the ThemeStore.js.
Fixed in StartupPageConfigurer#applyBranding. If there is no branding, default theme is set as current theme. |