I'm developing a Bigcommerce Stencil-based theme and there are some store settings that are being ignored when serving it locally. For instance, if I turn off "Enable Image Zoom" in the store settings, it is still enabled locally. Or if I turn off "Show Tiny Thumbnails" the thumbnails still show. I hesitate to rip out that code from the theme files, but is that the only way to handle this stuff locally?
While transitioning from Blueprint to Stencil, some settings will still be visible in the control panel that do not affect Stencil.
The reason for this being that in Stencil, we've moved these settings into the theme itself so they can be controlled by a theme editor and saved on a per theme basis. Blueprint, however, relies on global store settings and doesn't retain store setting styling that might occur.
You'd want to make these changes within the Stencil config file.
Related
Firstly, wow, Bigcommerce's own forums are dead as heck, huh?
Anyway, I've been working on my theme locally within stencil and for the most part it's been going fine. I did add a grip of images to the /assets/img directory that are displayed by category.js under certain conditions, which worked great when I'm serving from localhost but when I push the theme to Bigcommerce from the commandline (using 'stencil push') these images (and a couple custom icons, etc) are broken. I read the docs that warned me to make sure any added directories have the proper permissions but 1) this is an existing directory and 2) i'm getting a 404 anyway so it's not like they can't be accessed, they're just not there at all. Clearly Push isn't bundling them up, which means I'm doing something wrong.
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.
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
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.
The Cpanel product for Linux has a way with its SDK to create a new icon for your own custom form and PHP scripts to do various tasks. I joined a project where the original developer is no longer there, and left no documentation. We can change the PHP scripts and the form, but we have not been able to figure out how to change the label for the Cpanel icon that is shown to customers on this hosting plan.
How do we change the label on our custom cpanel icon? What file do we edit? Where do we make the change? Do we have to do anything after this editing in order for the change to be seen by all the customers?
On shared hosting you need at least WHM access.
If you have WHM access, you will see in cPanel a new functionality called Branding cPanel, in there you can play with css files and html files used to change the look and feel of you cPanel.
Anyway it's not an easy task. To change a label you would probably have to find the id of such label and using the branding editor upload a javascript file in the cPanel header that gets the id of the DOM object of the icon you want to chnage the label.
I mean in the branding editor I don't rememebr you can change a label of an icon, but just the icon image.
Here's the cPanel documentation for branding/customization
http://docs.cpanel.net/twiki/bin/view/AllDocumentation/WHMDocs/AdvancedBrandingGuide