I am currently making changes in a live shop. So I have duplicated my live theme and am making changes in my duplicate.
Still all my changes are visible in my live website. Somehow, all my themes in my shop are routed to my hosted domain at GoDaddy.
Does anyone have an idea how I can prevent this from happening and can only route my live theme to GoDaddy?
Kind regards
Let's call the duplicate theme dev and the live one live. They are all hosted on the same domain from GoDaddy
This should be the way to modify dev vs live environment, by using theme kit and use git to track files
3 Simple Steps for Setting Up a Local Shopify Theme Development Environment
Live Reloading Shopify Themes: Sass Compilation with Theme Kit and Prepros
Base on the information you gave, I will check the following
-check that you are not previewing the dev theme.
-check that when you are editing the correct theme.
-make sure to only edit files offline. This will save you so much trouble.
Related
I have never worked with shopify before but I have experience with other CMS's.
I recently got a client with a website already live and with some quick research, I see that I need to create a private app and manage the site with themekit.
What I need help with is how to properly set up a staging/dev environment to view the changes I make before pushing the changes into production.
Thanks!
Make a theme backup by duplicating your current theme. and make code changes in to this theme ( you can preview your changes without affecting live theme/store) when you and your client happy with the changes you can publish this theme to live.
Have a look how to backup / duplicate theme.
https://help.shopify.com/en/manual/using-themes/managing-themes/duplicating-themes
Hope this will help
I have created shopify site now i want to create backup system for it.
I want to know is there is any way to create backup of each and everything daily basic on my local computer by default. Actually i don't want to depend on plugins
You can create a private App for yourself in your shop. With those credentials you are free to use the Shopify API to download all the assets of your shop to your local computer. Consider that a backup. Note that you cannot as of yet download your navigation links, but that is pretty much the only thing you cannot backup.
You will find this to be a challenge, backing up your site.
I've studied the link below:
Storefront Source Code Getting Started.
According to the "Configuring content connection string" Section, I realized that the need to be placed physical address of "cms-content" of admin.
but We've deployed web applications(admin and storefront) to dedicated server.
So for a configuration with these conditions I read the link below:
Deploy web applications to dedicated server
But this link is not yet clear how the "ContentConnectionString" was initialized.
ContentConnectionString storefront setting pointed to place where themes files stored and has default value ~/App_Data/cms-content.
VC platform, with installed module vc-content allows to manage themes files from manager UI and have similar setting CmsContentConnectionString.
If storefront and platform have installed on same Azure apps or dedicated server this both settings should pointed to same physical place and have follow valuesprovider=LocalStorage;rootPath=~\App_Data\cms-content in platform Web.config and provider=LocalStorage;rootPath={ vc-platform physical path}\App_Data\cms-content in storefront Web.config.
For case when VC platform and storefront have separated installation need to use azure blob storage provider=AzureBlobStorage;rootPath=cms-content;DefaultEndpointsProtocol=https;AccountName=yourAccountName;AccountKey=yourAccountKey to share themes files between storefront and platform.
We strongly recommend use store and change your theme in GitHub repository and use CI (continuous integrations tasks) for update themes on production and use admin UI theme management only for emergency fixes or other not historical changes.
We are in the process of developing a theme for a client using Stencil. On our local development the checkout.php just hangs. Cart loads fine but just sits there moving to the checkout. Should it be possible to complete checkout thru our local development? Are there special configurations that have to be made?
The problem is that site view in cms differs from live site itself.
In cms edit mode I've deleted component from container inside page, saved, then published changes. Publish done successfully without any errors and site view in cms looks correctly, i.e. without that component that was removed. But this component still appears in live site.
I can easily fix this problem by removing this component in console. In cms console it can be seen that preview and working configuration differs.
But why this type of desynchronization happens? And what can I do to prevent this kind of problems?
This type of desynchronization happens rarely, but this problem may be very critical in production.
I am using Hippo CMS 10.1.0 Community Edition
If Your configuraton have been resynchronized, good way is to remove whole preview node. This node will be reconstructed from Your live node when You enter in CMS and turn on edit Mode.