Shadows 2.0 pkg overwriting older pkg?

[lesliekirk]

I have been working on a site that has (had?) an older version Shadows. I went in the admin to try and determine what version it was. Imagine my surprise when the only version number I saw was 2.00.05 and that it had been APPLIED! How do I even begin to confirm that it was applied? The old pkg has the same file name as the new pkg

QZGVUi.png

[Matt Zimmermann]

Hi Leslie,

According to your image, the last time the framework was applied was 02-25-2020. In that case, the v2.00.05 version is not being used. I am working on a way to update the Framework section of the administration portal to better differentiate the applied framework version from the one currently available in the latest release of the software. In the front-end, there is a variable you can use in the console to get the current release information, mivaJS.

[lesliekirk]

Hi Leslie,

According to your image, the last time the framework was applied was 02-25-2020. In that case, the v2.00.05 version is not being used. I am working on a way to update the Framework section of the administration portal to better differentiate the applied framework version from the one currently available in the latest release of the software. In the front-end, there is a variable you can use in the console to get the current release information, mivaJS.

Yes, the applied date would be when the v1 unknown version number was applied. My question how did this version overwrite the one that was there? If I had tried to upload a pkg with the same file name, it would not have let me. I have always had to rename a pkg to get it to upload.

Pressing on, will any of this cause any sort of issue in a Branch?

And a final note, I noticed that the CSS is off a little since the recent updates. Anything I should check to see if it changed?

[Matt Zimmermann]

Hi Leslie,

When there is a software update, the most recent version of Shadows is shipped with it and will be available to the store. However, it is not applied until you select it and apply the framework. As for branch issues, I cannot think of any. There are no CSS issues that I am aware of with the most recent update. What are you seeing?

[lesliekirk]

Hi Leslie,

When there is a software update, the most recent version of Shadows is shipped with it and will be available to the store. However, it is not applied until you select it and apply the framework. As for branch issues, I cannot think of any. There are no CSS issues that I am aware of with the most recent update. What are you seeing?

I think I figured out the CSS "issue" - there were a number of images that were missing. I reuploaded them and things started looking good again.

[Jim Cockerham]

When creating a new branch and applying the new Framework to it, should I select "Overwrite CSS Resources, JavaScript Resources, and Other Resources" ?

[Matt Zimmermann]

Hi Jim,

While it technically shouldn't be necessary to check that option on a fresh branch, it couldn't hurt.

[Jim Cockerham]

Hi Jim,

While it technically shouldn't be necessary to check that option on a fresh branch, it couldn't hurt.

Ok, thanks Matt. I just wanted to be sure that it would not affect my live store.

[lesliekirk]

When creating a new branch and applying the new Framework to it, should I select "Overwrite CSS Resources, JavaScript Resources, and Other Resources" ?

I know I did do that

[Jim Cockerham]

I know I did do that

Thanks Leslie :)

[lesliekirk]

This is still trying confusing. I really would like to know what version of Shadows is truly active because it cannot be the "current" version because the "applied" version dates before the "created" version.

The store makeover has basically been rebuilt on a now obsolete version.


SQWkGC.png

[Matt Zimmermann]

Hi Leslie,

The only definitive way, currently, is to access the console in the browser developer tools and enter mivaJS

[lesliekirk]

I created a Branch, then applied the newest version of Shadows to the Branch. Then I went to look at the Production view and there are all sorts of problems. The CSS is missing, Images are missing (but seems to display of the branch). Why has applying the latest version of Shadows screwed up the Production version.

[Matt Zimmermann]

Hi Leslie,

For something like that, I would contact support.

[lesliekirk]

Done - waiting to find out what happened. I had also sorts of weirdness crop up with this one. Thank goodness I made a framework of all the work that has been done to date.