Thanks for writing – sometimes a new widget template doesn’t click into place in cases where a Saved Widget using that template has its own changes/overrides saved, or sometimes a syntax error in the .xml prevents LW from loading the new version so it falls back to a prior version.
The cache files in /livewhale/data are not user-editable (only system-editable) by design so they can only be edited by LW (and really, while you’re welcome to poke around out of curiosity I’d hate to think that anyone is spending time in that folder or being stressed by its contents!). LW’s cache-clearing mechanisms should detect and reflect changes as needed—sometimes re-saving a profile, widget, or logging out and logging in can help goose the cache if it’s not showing what you’d expect.
If those tactics (double-checking the .xml syntax of your template, and re-saving a profile to force the cache to clear) don’t do the trick, feel free to reach out via your personalized support email and we’re happy to take a look at the widget template with you to see if we can help with diagnosis of why your changes aren’t showing up on the live site. Thanks!
thanks, karl. all i changed was text: from “Majors & Minors” to “Areas of Study”. i can’t imagine that that would render the xml invalid. when you say “re-saving a profile”, what do you mean by that? the widget is pulling in pages and not profiles.
Sure, that might not be it at all, just trying to think of all the things it might be—the reason I said to re-save a profile is because _ingredients/templates/widgets/profiles.majors-and-minors.xml is a profiles widget template (the first block before the period in the filename indicates the data type). In those cases, re-saving a profile of the correct type will already clear all related widget caches. Maybe your page has a certain profile type that points to Majors/Minors pages via a custom URL or such, and that’s what’s being shown and filtered? We’re not able to log into your site or server via the forum, so let me know if there’s more advice we can give in the abstract, happy to keep chatting through things here, otherwise we can get more hands-on via email. Thanks Steve,
@karl I’m also experiencing issues with widget styles caching. See screenshots of style being delivered to browser, actual styles as appear on the server, and LW User settings that should disable caching. I have validated my widget theme’s xml and widget styles’ .less. Is there something I’m missing, or are you seeing any errors?
I believe this might be a known bug with 2.20.2 on staging and dev servers with LESS processing we just became aware of today — we’ll check into that and let you know what we find, more soon,
We’ve got a fix for this into our next version (it had to do with how our clean-css implementation handled silencing warnings for unsupported style elements like @supports) but also I gather our team patched a workaround to your staging site’s styling to address this in the meantime. Let us know if you continue to run into issues with your CSS work; thanks!
