If you look at the css, you’ll notice that certain variables are missing completely, e.g. colors_text, which is used to render a border on inputs. I’m unsure of why certain global liquid variables would not be rendering on this page in particular.
Any ideas about why this is happening would be greatly appreciated. Thank you!
If it’s missing how are others going to observe it.
You’ll need to provide a concrete example to move forward that other people can reproduce some X result, and or sample code such as where to look in the CSS that is RENDERED and MINIFIED.
We haven’t changed much except the appearance of things.
Thanks for your reply. HTML/CSS validation not terribly helpful. There are “errors” but those errors look very similar to other pages which are presenting correctly. I’m guessing it would show the same errors on those pages for the base dawn theme.
Additionally, we haven’t changed any code on this template. The template matches exactly the original dawn template for activate_account.liquid. When I revert theme.liquid to match dawn’s base theme.liquid, things still look wrong. And I would have thought that’s the only other file which could have this effect. When reverting the theme, our custom css isn’t even rendering, so it should pretty much entirely be the dawn theme at work.
If I knew what specifically we had changed to produce this issue, I would definitely share that. But we haven’t been looking at this page since now because we did not previously activate customer login.
If you have any other ideas for how I can troubleshoot, I’d be greatly appreciative and will try them out. Thanks again.
Without knowing specifics of those changes there’s little others can do, this is why at mininium basic notes as comments in the code to allow retracing of steps, or source code version control should be used especially given shopifys new integration with github being available.
If you changed the CSS files, or some other templates you need to get a copy of the original Dawn, or just a latest version and do a comparison to look for differences and see if you can spot an issue.
You can use a tool like meld to compare a directory of files and see changes between files in each
No, “looks very similar” doesn’t cut the mustard for troubleshooting. Errors can cascade, exacerbate or just behave differently between different templates and content.
When on a page there is not just that template, but the layout, snippets, assets, apps,etc. It’s the ENTIRETY of the thing as it’s rendered is what you are validating to surface clues as part of general troubleshooting.
It could be related, it could not be /shrug that’s the ambiguity here with pre-existing errors and new errors that can only be resolved by addressing and fixing as many existing errors as possible so they become non factors now and in the future.
If the above doesn’t get you closer and you just need the thing debugged you can hire me at paull.newton+shopifyforums@gmail.com please provide store url, theme name, and topic url with details.