Skip to main content

Migrating Ambassador Storefronts and Ambassador Hub to the Live Theme

Instructions on how to copy pages from a theme copy to your live theme.

Gary Garofalo avatar
Written by Gary Garofalo
Updated over 2 years ago

Before migrating your Ambassador Hub and Ambassador Storefronts, ensure:

1) You've previewed the pages in your Theme Copy and they are ready for Production.

2) You have not made any updates to the "Customers/Account" page since the Theme Copy was created.

Step One: Turn on LoudCrowd app ON in Theme Editor > App Embeds

  • Click Customize on the Live theme and go to App Embeds.

  • Make sure LoudCrowd is turned ON and the secret exists.

  • If the secret is empty, request you can refer to the LoudCrowd copy theme – copy & paste it into the same place in your live theme.

  • Save

  • Contact your Client Strategist to request your secret if you are unable to locate it

Step Two: Copy the LoudCrowd page template code from the theme copy to the live theme

  • Open “Edit Code” in both your Copy theme and their Live theme. It’s easiest to put these in two windows next to each other so you can easily copy/paste.

  • Ambassador Hub

    • In the Copy theme code editor, find the ambassador-hub page template. Copy the entire page

    • In the Live theme code editor, find the same page template. Paste everything you copied.

    • Save

  • Ambassador Storefront

    • In the Copy theme code editor, find the ambassador-storefront page template. Copy the entire page

    • In the Live theme code editor, find the same page template. Paste everything you copied.

    • Save

Step Three: Update the Customer Account page in your Live theme

Option A (Most Common): Account page was updated by adding Ambassador Hub Profile app block

You’ll need to determine which type of page (liquid or json) is your account page:

  • Go into “Edit Code” on your Live theme

  • Look for a page template called customers/account. This page will end in either .json or .liquid

  • Follow the corresponding steps below

(More Common) Instructions for a customers/account.liquid page

You’ll be converting your .liquid page into a .json page in order to add the LoudCrowd app block. You do this by building a json version of your account page and making your existing liquid page a section that sits inside of your new json page. This allows you to add the LoudCrowd app blocks above or below your previous account page section.

  • In “Edit Code” on your Live theme, create a new section template called ‘customers-account’ (make it a liquid section)

  • Find the corresponding section template in your Copy theme. Copy all the code and paste it into the Live theme ‘customers-account’ section template

  • Save

  • In your live theme, create a new page template called customers/account.json – this will exactly match the existing customers/account.liquid file. Shopify preferentially uses a json over a liquid file where both have identical names. (you have to name it something else and then change it back)

  • Copy the entire code from the customers/account.json file in your Copy theme into the same page in your Live theme

  • Save.

(Less Common) Instructions for a customers/account.json page

  • In Edit Code of your Live and Copy themes, go to your customers/account.json page.

  • Copy paste the entire page code from your copy theme into your live theme. This will copy the Ambassador Hub Profile app block and all its settings.

  • Save

Option B (Less Common): Account page was updated by adding Hub & Storefront links to an existing navigation menu

Typically these are managed by your ecomm/web dev team rather than by LoudCrowd. As such your team should manage the deployment steps, using the “how to build links” documentation provided by LoudCrowd (above, in Building Pages).

Option C (Least Common): Other customizations

Typically these are managed by your ecomm/web dev team rather than by LoudCrowd. As such your team should manage the deployment steps. Coordinate with your Client Strategist to determine which modification method was used, and how to manage go-live steps.

Did this answer your question?