======== TEMPLATE BUG FORM ========
Wappler Version : 3.7.3
Operating System : Windows 10
Server Model: PHP
Database Type: MySQL
Hosting Type: custom
Expected behavior
Making a change in Theme Manager should not replace the version of Bootstrap, removing a custom theme.
Actual behavior
bootstrap.min.css was replaced
How to reproduce
I’m not sure exactly how to reproduce this. It seem to behave differently on different sites - perhaps depending on when they were created and what version of Bootstrap was used.
I noticed a problem with a site I hadn’t worked on for about a year. The custom styles were missing*. Theme Manager showed the correct changes, but they weren’t reflected in the pages - probably because the version of Bootstrap had been updated automatically to the current version.
I downloaded the good version from the live site* and now everthing works as it should. The styles are correct, Bootstrap (4.4.1) is not automatically updated when I make changes and Theme Manager works correctly. I had to do the same with another site but a site I’m working on (also using 4.4.1) works fine - Bootstrap wasn’t replaced and Theme manager works.
What’s meant to happen with custom themes when a new version of Bootstrap is released and incorporated into Wappler? Should the old version, used for the custom theme, be retained? What’s the procedure if you want to upgrade to the new version but keep the style changes? Is it necessary to re-enter them or can the changes in theme.json be used to make the changes?
(This is one of those cases where I’m so pleased about the change which means saving a file can’t automatically update the live site. Once before I did this when bootstrap.min.css was replaced automatically. The results were very unfortunate.)
Last updated: