-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Show all themes on page add/edit #2964
Conversation
show all themes when adding
Show all themes when editing
@markdav-is this is actually not a typo - it was a deliberate change in 4.0. There is a long thread about this topic but the summary is that allowing completely different themes to be used on different pages within the same site has a lot of technical problems which cannot be resolved (due to SPA characteristics). It only works in scenarios where the themes are using the exact same version and source of JavaScript and CSS libraries (like the default Oqtane themes). However if themes use a different version/source of these JavaScript libraries, there will be conflicts and the site will break. Therefore a change was made so that you can only use themes from the same theme package within a site. |
This is the entire thread: There were problems with both CSS and JavaScript for this scenario - so it was best to prevent the behavior by restricting the ability to choose different themes within a site. Obviously you can still switch themes by changing them in the Site Settings. Also... if you create a theme which contains theme components that internally use completely different CSS and JavaScript, the framework is not going to prevent you from assigning these theme components to pages as they are part of the same theme. However you should be aware that they may exhibit JS and CSS issues. |
@markdav-is closing this PR as I explained the expected behavior above in 4.0 |
Thanks for the explanation. I'll check out that thread. We use the built-in theme for the admin pages and dashboard. We use a non-boostrap theme for the actual apps. I feel like we can have two themes as long as they don't both use boostrap. With this change, I feel like we need to re-build all the admin UI in our custom theme. So our themes will need to be "complete" and not just for apps. This will add a lot of opportunity costs to our projects. |
@markdav-is I am going to revert the behavior and allow overriding themes at the page level. I will simply add a warning message to the user. |
Found a small typo what would limit the theme dropdowns on page add/edits to show only the default theme.