Template Branches

[lesliekirk]

Another thing I noticed when applying a New Framework in a Template Branch.

This instance being applying the latest Shadows v10.04.00 to a copy of a Production (Primary) Branch using a modified version of Suivant. I'm sure this is true for any instance though.

Settings > Store Settings > Customer Fields

All of these setting will change to whatever the framework defaults to.

Luckily I checked this before applying the framework since our store uses the billing address as the primary address.



Another thing to take note of are all of your Image Machine sizes within the page templates that use the Image Machine as well as the search preview setting.

These will all change as they are branch specific as well.

If you don't want to overload your server with new images that arent being used on the live site, then you may want to adjust these to match your current Production (Primary) Branch image sizes BEFORE you start previewing the New Template Branch.

Maybe write a list, make a spreadsheet, or word doc with each Page Template Code and the new image sizes that were overwritten by the new framework. In Case you want to migrate your original image sizes to the new image sizes later on when you're ready to make the New Branch the Primary Branch. Just an idea.

Cheers,

Nick

Interesting - I wonder if this could be a new bug or if it's related to one I found (and hasn't been resolved yet). I think you may have found something related to BUG ID: MM-11625 but different.

[SidFeyDesigns]

Another thing I noticed when applying a New Framework in a Template Branch.

This instance being applying the latest Shadows v10.04.00 to a copy of a Production (Primary) Branch using a modified version of Suivant. I'm sure this is true for any instance though.

Settings > Store Settings > Customer Fields

All of these setting will change to whatever the framework defaults to.

Luckily I checked this before applying the framework since our store uses the billing address as the primary address.



Another thing to take note of are all of your Image Machine sizes within the page templates that use the Image Machine as well as the search preview setting.

These will all change as they are branch specific as well.

If you don't want to overload your server with new images that arent being used on the live site, then you may want to adjust these to match your current Production (Primary) Branch image sizes BEFORE you start previewing the New Template Branch.

Maybe write a list, make a spreadsheet, or word doc with each Page Template Code and the new image sizes that were overwritten by the new framework. In Case you want to migrate your original image sizes to the new image sizes later on when you're ready to make the New Branch the Primary Branch. Just an idea.

Cheers,

Nick

[lesliekirk]

We're going to add a version of this to the docs

Something that Ryan didn't touch upon is the data exports. I mention this as a reminder for those who are still needing to use a dev site to build out a makeover in those instances that call for one.

If it's "Branch specific" it gets exported in the framework but if it's "Global" it is (can be) exported. But this can get dicey if you don't remember that these items are part of the framework

1. Categories - Everything is global , other than:
   1. Title Image: Branch-specific
   2. Tree Image: Branch-specific
   3. Header: Branch-specific
   4. Footer: Branch-specific

If you have done a lot of makeover work in these areas, do not include them in a Category export from a dev site (to import into the site being made over)

[Rick Wilson]

We're going to add a version of this to the docs

[SidFeyDesigns]

Thank you! This post should be a sticky or just add it to the docs.

[Leanne]

Thanks for this comprehensive outline, and congrats on the marriage! It looked like a beautiful wedding.

[Bruce - PhosphorMedia]

thanks, never noticed that. should be on the front side of the site doe...(IMO)

[lesliekirk]

Excellent work and I will fifth, sixth, seventh, etc upvote the idea that MESSAGING which branch you are in needs to be VERY VERY VERY noticable. Both in Admin AND on the front side.

I would also like to plead the case of these changes to front side messaging as well:
Make location of 'branch bubble' positionalble.


(Btw, Scot R reminded me that we can change the branch bubbles ourselves by simply adding our own CSS...but would still like to have this Out of the box.)

I think it might already be positionable. Click the blue square in the corner to display the other positions available.

nX31jI.png

[alphabet]

Congrats! It looks like a beautiful bride and a lovely wedding. I wish you a lifetime of happiness!

[RTHOMASDESIGN]

Thanks everyone!

Have you ever had anyone complain about a branch "link" you may have shared to allow for review getting "stuck"? I've had to remind a number people how to end the preview but some have had to clear their cache to get back to the live view.

I've had a couple people tell me they're stuck in the dev branch (on the frontend)... or don't realize that they're in a dev branch. I think it's usually because they accidentally click "Suppress Development Overlay", rather than "End Development Preview". If they don't have UI privileges, I tell them to preview the site again by clicking the "eye" icon within the admin, and then remind them to click "End Development Preview" from the overlay. Otherwise, I tell them to make sure they're in the correct branch within the User Interface panel. There's now a popup if a user clicks "Suppress Development Overlay" -- hopefully that helps moving forward.
.
Personally, I've never had an issue.

[Bruce - PhosphorMedia]

Excellent work and I will fifth, sixth, seventh, etc upvote the idea that MESSAGING which branch you are in needs to be VERY VERY VERY noticable. Both in Admin AND on the front side.

I would also like to plead the case of these changes to front side messaging as well:
Make location of 'branch bubble' positionalble.
Make it minimizeable.
Make the size setting controllable.

(Btw, Scot R reminded me that we can change the branch bubbles ourselves by simply adding our own CSS...but would still like to have this Out of the box.)

[lesliekirk]

Woohoo! Congratulations Ryan! And thanks for Template Branches outline too! It affirmed what I had figured out about some odd behaviors I have had when using the Template Branches. Question - have you ever had anyone complain about a branch "link" you may have shared to allow for review getting "stuck"? I've had to remind a number people how to end the preview but some have had to clear their cache to get back to the live view.

[Rick Wilson]

Congrats!

[ids]

Awesome Ryan!

Scott

[William Davis]

Impressive.