Determining the version number

[lesliekirk]

lesliekirk If the Shadows theme was last applied on 5-8-2018 then it is not the newest version of Shadows.

Shadows was built into the framework in 10.00.00 and that was released in 9-23-2020. From 10.00.00 and up Shadows has inherited the version number of the software.

In Version 10.05.00 (released 12/19/2022) a significant update was made to the Shadows Framework that restructured the CSS and JS files. Many have referred to the 10.05.00 version as Version 2 of the Shadows Framework.

If the Shadows Framework was last applied before 5-8-2018 or does not look like this, https://shadows.mivareadythemes.com, then the framework is not up to date.

If the Framework looks like the newest version and was applied after 9-23-2020 then you should look at the template changes to confirm that they have been applied.

Template changes can be found here:
https://www.miva.com/template-changes
https://github.com/mivaecommerce/shadows?

The version number you are seeing in the admin is correct as the PKG file that is loaded on the store is version 10.08.02 (when applied it will install version 10.08.02 not an old version) if you are on that version of the software. The last applied let's you know when the framework was last applied to the store, if the date was before the last update then the version applied can not be the most up to date version. So you can conclude that if the framework was not applied before the most recent software update or the template changes were not applied then the framework is not up to date.

Hi Nick - great info for those who might not be aware of the "History of Shadows". I think I was one of those who complained about the original version number being overwritten by the latest PKG file version which could lead to some confusion in older stores. I was just trying to find out if there was a way to determine the applied version number (I needed it for information to get to the store owner instead of just telling him "It's out of date".) Thought I was going to have an "ah ha" moment when I went to look at the SFNT Page Template to check the Versions but all it has is the same info 5/8/2018 Updated by Framework 'shadows' - LOL that doesn't tell me which version it was. And yes the end game IS to update to the latest version but ya know about that cat and curiosity? There is a happy ending, "the satisfaction brought him back!"

[Nick]

lesliekirk If the Shadows theme was last applied on 5-8-2018 then it is not the newest version of Shadows.

Shadows was built into the framework in 10.00.00 and that was released in 9-23-2020. From 10.00.00 and up Shadows has inherited the version number of the software.

In Version 10.05.00 (released 12/19/2022) a significant update was made to the Shadows Framework that restructured the CSS and JS files. Many have referred to the 10.05.00 version as Version 2 of the Shadows Framework.

If the Shadows Framework was last applied before 5-8-2018 or does not look like this, https://shadows.mivareadythemes.com, then the framework is not up to date.

If the Framework looks like the newest version and was applied after 9-23-2020 then you should look at the template changes to confirm that they have been applied.

Template changes can be found here:
https://www.miva.com/template-changes
https://github.com/mivaecommerce/shadows?

The version number you are seeing in the admin is correct as the PKG file that is loaded on the store is version 10.08.02 (when applied it will install version 10.08.02 not an old version) if you are on that version of the software. The last applied let's you know when the framework was last applied to the store, if the date was before the last update then the version applied can not be the most up to date version. So you can conclude that if the framework was not applied before the most recent software update or the template changes were not applied then the framework is not up to date.

[lesliekirk]

How do you go about determining the version number for Shadows if it doesn't have

mivaJS.ReadyThemeVersion =

in the source code and the admin tries to convince you it's 10.08.02 (when you know it's not).

It does show that it was "Last Applied" on 5-8-2018