Top level "All" page does not show changes

[pattern-lab]

Top level "All" page does not show changes

[dmolsen]

@fStop -

Hrm... I'm having trouble recreating this issue in Safari 6 or Chrome 32. Sounds like a cache issue but it should still be loading correctly. If you let me know which browser you're using I'll fire up BrowserStack and see if I can track it down. Sorry.

[isGabe]

@dmolsen weird, the issue seems to have resolved itself. I was using Chrome 31 (Mac OS 10.8) FWIW.

I couldn't see how it would be a caching issue, since it was the actual content that was not loading, and not resources (CSS, JS, etc). Maybe turning it off and on took care of it :)

Great tool, BTW. Loving it. 🍻

[dmolsen]

K. Sounds good. Any questions just drop 'em here. Appreciate the feedback :)

[mikes000]

@fStop I ran into a similar issue where things weren't updating or changes showing up. It turned out to be a caching issue and chrome would not let go of the cache even on a hard refresh. To get around this whenever working with pattern lab I set in chrome developer tools to disable caching when developer tools is open.

Open the developer tools for chrome and click the gear in the bottom right corner and check "Disable cache (while DevTools is open)" Now whenever you have the DEV tools open caching wont be an issue.

[bradfrost]

Yeah this is something that's been an issue for me. It's also worth noting that Codekit has been increasingly buggy. I'm not sure if you're using something like that as well, but once I moved away from Codekit my caching issues have been better. That being said, we're aware of the caching issue and @dmolsen is on it in #43

[isGabe]

Yeah, I've been moving toward Grunt and away from CodeKit more lately. Codekit has always caused issues with live reload enabled, so I've never used that feature much.

It was weird and hard to get Grunt set up at first, but I've gotten more comfortable with it, and it just works. Plus I get to feel like a hacker on the command line.

Cache busting is a good idea with something like Pattern Lab. The thing I'm still wondering about here, though, is the fact that it was the actual content of the templates, and not the assets (CSS, JS, images) that were not refreshing in my case. That doesn't seem related to browser cache.

But as I said, the problem disappeared on its own, and everything has been working fine since.

[isGabe]

Interesting, I guess I was wrong and the content does get cached.

I saw the issue again when updating some of the pattern templates. The build succeeded and the html file for the pattern in /public/patterns would update, but the content at the url (/?p=molecules-logobar in my case) would not show the update. Clearing the cache in Chrome solved it.

[dmolsen]

I've done the following:

• added no cache meta tags to the style guide, view all, and pattern templates
• each call to update the iframe source gets a time stamp added to it (e.g. ?1385830752106)

Hopefully these changes help. They're currently in dev branch and will be part of the 0.7.0 release. Learn more about it in #66.