Switching Framework Questions

[marshallw]

Our sites are pretty old and need a refresh. I am looking at switching to the new Shadows Framework. I have a couple questions.

1. Can I create a Branch on my live store, load the new framework and work on it without effecting my live site. (I know some global data can be effected, just trying to understand branches a little better here)

2. I notice in Frameworks - Shadow Theme gets regular updates. If I use that framework will it continue to update and if so will that update wipe out some of my data?

I am just looking to update the look and feel and some of the core functions found in the new framework. I am also trying to do this without a dev site. I have a dev site but the data in my dev site is very old, so I do not want to try and untangle that mess.

Thanks,

[Nick]

marshallw Miva Version 10.07 introduced page and JS/CSS resources branch isolation to help improve the process to create a new branch and not effect any other branches. In Miva Version 10.08 the software will also include branch isolation for page items and other areas for a completely isolated branch.

All that being said to answer your first question in most cases you can create a new branch, install the Shadows framework and not effect the primary branch. The cases in which you might run into issues is when there are modules that require an item to be assigned to the page. In Version 10.07 the item will be unassigned/assigned to all branches which could cause issues with load time or the loss of functionality (if item is unassigned). One recent example that I saw was with a store that had the Category Template Manager module by Sebenza installed and there were issues with images loading due to the outdated module. The module could not be unassigned from the development branch page because it would be unassigned from the primary branch page as well and remove the functionality from the live store (the store needed to create a development store on a subdomain then export/import the framework).

Aside from item assignment in the branch system (which will be updated in 10.08) you should be able to create a new branch, and assign the Shadows Framework with no issues (the installation of the framework will not deactivate items).

As for the Shadows theme updates they will only be applied to new installs of the framework and not applied to existing installs. With each update we will be releasing the template changes, https://github.com/mivaecommerce/shadows, in which you can manually apply to the framework.

For more information about the branch system you can review the docs page here: https://docs.miva.com/miva10/referen...nches-overview

[ids]

Marshall,

I've done this a few times. The current versions will share the live data. It's all minor, but needs to be looked after. The two issues, categories, and theme components such as menus. IOW, Shadows has some placeholder data for category and navigation items. This data can show up in the primary store branch when you add the default theme to a development branch.

HTH,

Scott

[Nick]

ids In Version 10.07 Theme Components became branch specific so there should be no issues when a component is created within a branch. So when Shadows is installed it will create Theme Components on the active branch and the primary branch will be left untouched.

As for categories you are correct, when you apply the Shadows framework there are 10 categories created in the store. The categories are added to a Theme Component Navigation Set within the working branch so there should be no issues with the categories being added to a Theme Component within the primary branch. It is probably best to remove the categories from the store if they are not needed so there are no issues with SEO.

[ids]

Good to know the theme components are branch specific in 10.07+.

Scott

[Bruce - PhosphorMedia]

totally non-germaine, but if you still have Category/Product template manager, you should remove/replace them at once. otherwise, you'll never be able to use the Tokens | View All Tokens feature as those modules have templates what will never compile correctly.

[marshallw]

I do not have any template managers outside of miva provided modules (example: email templates). Should be pretty straight forward in updating content. We currently use a ready theme, so if I make a branch and update content sections on a branch it shouldn't change the live site. This is my understanding.

Only global data I have to be careful with like Global Header/Footers, attached CSS and JS, and anything on the SQL server (ie customers, products, etc.)

If I change the way a product is displayed that is no issue, but If I change the image... issue.

I think I have a good understanding on it. I will do this stuff first before hitting the modules up.

[Nick]

Only global data I have to be careful with like Global Header/Footers, attached CSS and JS, and anything on the SQL server (ie customers, products, etc.)

Global Headers and Footers are branch specific. Everything inside of the User Interface section is branch specific (except pages and items as of 10.07).

If you have any scripts that are not in CSS or JS resources and hardcoded on a template then they will be global.

Customers, catalog, marketing, order processing, store settings, domain settings are all global and not branch specific.

However if you wanted to test those features they can be assigned to an availability group and only the user that is assigned to the group will be able to view those features (including payment and shipping options).