Item 1- I have run into an issue with a site that had a version of Shadows installed. When Miva had an update for Shadows it updates whatever version of Shadows is installed in the store. Thankfully it does not apply the framework to the templates. But the store shows that latest version of Shadows as the "Active" Framework. This is very misleading. In this case the store shows in the (Production Primary) Framework screen that Shadows 2.03.00 is the Active Framework with a Last Applied date of 4-8-2022 and Created Date of 3-29-2022. This is incorrect. In this store (Production Primary) Framework Shadows was applied on 8-5-2021 and was never "updated". I have no idea which version of Shadows is actually applied because of the way Shadows is updated.
Item 2 - (and might be a bug) I created a Branch (after first saving the Production Framework). I applied the latest version of Shadows to the new Branch. When I went to compare the Production Branch to the new Dev Branch (using the development preview) I noticed issues with the look & feel of the Production Branch. I created a third branch and applied the saved framework to it. I was expecting the Production Branch to look just like the saved framework branch but it didn't. I suspected an issue with the CSS files. I opened the site up via FTP and stated comparing file modified dates. In the Production directory /mm5/themes/00000001/shadows the dates on these files jumped right out at me:
core.css
core.js
extensions.css
extensions.js
polyfills.js
theme.css
theme.js
All of these files had the same time stamp as the Branch I created for the newest version of Shadows. I dug into other folders and discovered changes there too. The clue that gave it all away was the theme.css file. I had had an annotated version of the theme.css in the Production version and it had been overwritten when I installed the latest Shadows version into the Branch. I did notice that the folder dates for the Production directory /mm5/themes/00000001/shadows had the "correct" dates from when the ReadyTheme was first applied. But it went in an updated files in folders such as:
/mm5/themes/00000001/shadows/core/images
/mm5/themes/00000001/shadows/extensions/contact
Granted these updates might not be a bad thing but overwriting the theme.css that is not good. What is did to the entire Production version of Shadows is not good. I suspect the problem might be related to Item 1.
And as a side note, when I did apply the Shadows 2.03.00 to the branch, in addition to the ReadyTheme categories (I thought there were plans to not allow the framework to add these categories), some how categories that had been deleted back last fall right after the initial set up of the dev site were resurrected and re-added to the site.
FWIW - I really like having a copy of the current version of the UI but it really needs to not have the ability to overwrite the UI I 'm using just because they are the same file name.
Leave a comment: