Since the first time I was using the Google Pagespeed tools to increase pagespeed, I didn’t get it. You do everything you can to get the 100, but if you are using Google products like the Google Font API or Analytics, Google remains complaining:
Who gets it? Isn’t this at least awkward? Why is Google preaching pagespeed and not caching resources like the fonts, which are used widely over the Internet? Since Google fonts and scripts are used so widely over the Internet:
Wouldn’t caching the Google fonts, the Google scripts and so on not increase the Internets pagespeed all together?
I’ve just released my first CodeCanyon Plugin and so I am almost constantly checking on sales and new comments and what so ever. Mostly wasting time. Now on CodeCanyon. So, suddenly, I got an error page, saying, that something went wrong and the developers are informed, but I could also call the support, if its urgent. Well it wasn’t so much. The next thing that popped up was Envatos Twitter message:
Hey, we’re experiencing some unplanned downtime. The Devs have been notified, and we will update you here. Thank you for your patience. ^TC
And the Twitter wave started. They soon went online again, which might have been a mistake, because the database was reset to an older backup (probably) (see here) and so I’ve lost a sale. I went to the Twitter “enevato”-timeline, where @AvaThemes reported
@envato_support We’re having some issues with the amount of money we’ve earned this month? it’s smaller comparing to an amount 2 hours ago.
I replied, reporting the same and instantly realizing, the comments are reset as well – and reporting.
Again, I went back on the timeline just to see how a torrent of tweets bursted. My money, my money, my money! And I started to realize how familiar I am with such an situation, just with the difference, I have just one client and not thousands. Poor guys.
@envato tried to stop that wave by posting:
We are aware of the issues regarding Comments/Purchases/Items etc, and we're currently looking into it. Thanks again for your patience. ^TC
Anyway, second after second a new complain, some poor fellow had to reply constantly while more important stuff was to do probably and then Envato decided to make a clever move. Take down the site and call it “Big backend changes”, the torrent broke.
And, then, after a while: Everything set to normal. The first tweet reporting this came by Astoundify
And we are back! If you were waiting to purchase/browse one of our themes you should be able to now! – http://t.co/ZYU6LwH58p
There is a new forum thread, where envato explains a bit, what happend. John Viner one of the developer teams said:
Our initial investigation has indicated that between 6:30AM and 7:00AM AEST, after the site came up from the initial downtime, some data was written to one of our non-primary databases instead of the primary database. This explains why some information such as a small number of sales, appear to be missing. Nothing is actually missing however, we have all the data. But we are now working on merging this data back into our primary database so everything aligns correctly.
So, it was not an old backup, which was enrolled, but that “some data was written to one of our non-primary databases”. As far as I understand this, the sales and comments and items during the day haven’t been stored in the correct database.
Its quite obvious, when you see it, but I haven’t thought about this possibility yet. Why should the load-function just work with window?? I will try this one for sure!
And this one here $("p:not(:last-of-type)").after(" ");
is quite nice to investigate further. As the jQuery Docs explain “Insert content, specified by the parameter, after each element in the set of matched elements”. So this piece of code puts a break between all <,p>-Tags, but not behing the last one, because :not(:last-of-type) I like this usage of the selectors and once again it shows the power of them.
Thanks for the Tweet!