I seem to have encounted an issue, that I'm not sure if it's a bug, or simply not understanding how something should work, or a feature not yet implemented.
I'm using the product-variant-container element, with select boxes.
However when you deep link a specific variant (product?variant=id) the select boxes aren't set to reflect this. I dug through the liquify_custom.js code and when the variant is switched, you're pushing this urlparam and setting the window history. But either something is broken in my implementation, or this was never fully implemented. Can you advise?
Looking for a recommendation on how to best manage customizations I need to make to the 'add-to-cart' javascript. We have a complex product configuration that can't be covered by out of the box Shopify and currently handle this when "add to cart" is called in our legacy theme. It's great that Liquify has the element to handle creating this client side code during conversion, but if I need to insert some logic to this, is there a way to do so that won't have to be manually merged with each conversion?
I've used the starter template, and run through Liquify and it works great.
During the conversion, I noticed it converts the reference to webflow.js into /assets/webflow.js.liquid.
Then, in the theme it references as {{ 'webflow.js' | asset_url }} and indeed it loads fine.
However, with my OWN webflow project I get a different behavior. I've generated a webflow from Relume, and I've added the webflow.js reference into the <head> in the site settings. On conversion, it does the same thing, creating an asset of 'webflow.js.liquid' - however, it won't load and it 404s. I'm not sure what the difference is or why it's not loading the same. Theme.liquid references it in the exact same way.
Hi - new to Liquify and kicking the tires. I would like to make sure that I understand this workflow correctly.
After the initial commit I make to my connected repo, any new pages that I create in my webflow project won't be converted into liquid page templates; but if I do create new sections (with the li-section tag) those will be merged and created in the published template, is that correct?
What about updating and changing those sections? Or, once published, do I have to do all of that in the theme files? If so, any guidance on keeping synched with my webflow project?
I can see both sides of this, but from a development workflow, this methodology has some gaps as well. When early in a project of developing a theme, much can change and it just means that the proper way to set this up is not necessarily a github flow, but to convert and manually upload the theme .zip.
