Shadows PKG up streaming update?

[ids]

What gets updated?

I guess I am just confirming, that when I do the update to 10.03+, Only the PKG file is updated and no Shadows Theme files that have already been applied/expanded will be touched?

And the follow-up question is, will the newer template code be included in that package, for example, the features for attribute updates on BASK.


Scott

[lesliekirk]

What gets updated?

I guess I am just confirming, that when I do the update to 10.03+, Only the PKG file is updated and no Shadows Theme files that have already been applied/expanded will be touched?

And the follow-up question is, will the newer template code be included in that package, for example, the features for attribute updates on BASK.


Scott

Yes, only the file named shadows.pkg gets updated (no matter what version it may have been). You still have to "deployed" it. I tried to get the latest version of Shadows in a newly created branch and it did some weird things to my Production Branch version of Shadows. So make sure you save a framework of your Production Branch (if you are using Shadows). I may have had one of those freak "Leslie" accidents with my experience. I'm still waiting to hear back from support.

FWIW I created the Branch to install the latest version of Shadows just so I would have all the updated coding available to tweak the older version the site is using.

[RTHOMASDESIGN]

When updating a Shadows site that I've already heavily modified, I find it's easier to just refer to the docs that Matt put together. I use a diff checker & merge changes where needed (obviously in a dev branch before pushing live). The latest template updates can be found here:

https://github.com/mivaecommerce/rea...ne/14?closed=1

Older versions can be found here:
https://github.com/mivaecommerce/rea...s?state=closed

Everyone has their own workflow, and my methods may not be best for you ;)
-Ryan

[lesliekirk]

Yes, only the file named shadows.pkg gets updated (no matter what version it may have been). You still have to "deployed" it. I tried to get the latest version of Shadows in a newly created branch and it did some weird things to my Production Branch version of Shadows. So make sure you save a framework of your Production Branch (if you are using Shadows). I may have had one of those freak "Leslie" accidents with my experience. I'm still waiting to hear back from support.

FWIW I created the Branch to install the latest version of Shadows just so I would have all the updated coding available to tweak the older version the site is using.

It should be noted that there is a confirmed bug (BUG ID: MM-11625) in my method. If you have, as Ryan mentioned, as heavily or even lightly modified version of Shadows and you want to update templates, for the time being until the bug is fixed, do not deploy the latest version of Shadows in to a Branch, the package will also overwrite your Production CSS files (and maybe other files).