I've been messing around with a new core template on our dev site and I've run into something strange with the default css file.
For starters, I've been working on the listing_0 template. In order to save time, I added a <style> section to the top of the listing_0 template so that I could quickly make and test changes without having to keep flipping back to the default.css file.
Now that I have things looking close to how I want them, I am trying to move these new css items into the default.css file, but for some reason, it's not applying these changes. It's as though all of my new styles don't exist. BTW - I am checking the changes in FF (which updates the css automatically), but I have still tried clearing both the store and browser cache to no avail. I have also checked the /web/assets/templates/bikes-core/css/default.css file to confirm that it is showing my latest save date.
I know that I am missing something simple here. Can anyone shed some light on this bizarre behavior?
For starters, I've been working on the listing_0 template. In order to save time, I added a <style> section to the top of the listing_0 template so that I could quickly make and test changes without having to keep flipping back to the default.css file.
Now that I have things looking close to how I want them, I am trying to move these new css items into the default.css file, but for some reason, it's not applying these changes. It's as though all of my new styles don't exist. BTW - I am checking the changes in FF (which updates the css automatically), but I have still tried clearing both the store and browser cache to no avail. I have also checked the /web/assets/templates/bikes-core/css/default.css file to confirm that it is showing my latest save date.
I know that I am missing something simple here. Can anyone shed some light on this bizarre behavior?
Comment