Support Ticket
Site Down due to rendering error? CSS or JavaScript tomfoolery?+issues
My wagn site on cloudstore (http://ledge.971.cldstr.com/wagn/) is down with the following error:
error rendering Home+original (core view)
I was editing some of the CSS style cards and I added a JavaScript card (with no content). It was all working for days before the site went down so I'm unsure if that was the cause. The cloudstore guys say everything looks fine on their end so I'm hoping you can help me out. I made a backup of the site in its current state.
Hmm, I'm not able to see even that error. Just a completely blank page.
I'm not currently getting any automated error reporting from Cloudstore since they moved servers. I'll try to fix that for Cloudstore's next release, but I'll probably need to get in touch with them if I want to make any headway in the meantime.
Do you remember when the site went down?
Have you tried going to /admin/clear_cache?
Hmm, yeah I see that it is blank now. It was working last weekend, for sure. I first noticed it was down on Wednesday the 13th I think. Not sure what you mean by /admin/clear_cache/ but I tried both http://ledge.971.cldstr.com/wagn/admin/clear_cache
and http://ledge.971.cldstr.com/admin/clear_cache.
I wrote the Cloudstore folks to try to put together a way to tackle this. If it turned out that I was struggling to find the problem without a copy of the site, how would you feel about sending me a copy of the backup?
That's fine, there's nothing incriminating on there...
Cloudstore sent some log information and is working with me to try a few things first. Is there any chance you were editing read rules recently on the site?
I don't think so. I was editing some styles for the Game Cards and I tried adding a javascript card. It didn't work so I commented out the code. Again, things were working when I was last editing - I only noticed it was down a few days later.
That's what I was hoping you'd say. The most optimistic interpretation of the data I've seen so far has been that the issue really just boils down to the cache getting screwy and acting as if there were no default read rule. If it's just the cache, it should be a very quick fix. If the rule is broken in the data, it may be a bit trickier.
Hi Lake. Good news: the site is working! Oddly, I'm not sure we can claim all that much credit. I wrote Cloudstore with suggestions of things to try, but they ran their standard updates before getting to try them, and that appears to have fixed things. This seems to buffer my theory that it was a caching problem, and that the standard cache-clearing and server-restarting that happens in a standard update was enough to get things going again.
Very sorry for the inconvenience. Let me know if you see anything else of concern. These caching bugs are very eccentric, so I wouldn't expect this issue to return, but please do let me know if it does.