5:30 am, Monday morning, and the first bug to bite me this week? Edit Flow / lack of custom status support in core.
Breaking my radio silence on this here blog to call out for help: if you know why my
alloptions cache ends up as
0 when I restart Memcached, I’d love to hear from you.
alloptions ends up as
wp_cache_add() never adds
alloptions to the object cache, resulting in hundreds of options queries on every page load.
Corrupt synced folder cache using Vagrant 1.4.2 and VMWare provider. Should you ever run into this problem, read this thread.
Not Getting GitHub Notifications? This makes my week. Many, many apologies to those who have opened issues I haven’t responded to.
For one reason or another, upgrading Growl to v1.3 causes all sorts of mayhem. Growl v1.3 is a new, paid application that’s different software from the previous preference pane. The only instruction I saw when I upgraded was to run the uninstaller for the preference pane. After a bit of trial and error, I discovered there’s a couple more steps you’ll most likely need to do to get things working properly again.
First, download and open Growl Version Detective. You’ll see something like this:
Select each application Growl supports and upgrade the framework version to 1.3. Notifications should start working again.
Second, if you use Skype, you need to tell Skype to use Growl instead of its internal notifications system:
The second step finally quells unstoppable notifications of contacts signing in and out of Skype.
iCal fail. With how often this happens to me (this time deleting a significant part of my upcoming calendar), you’d think that Apple would’ve introduced some sort of revision history for their syncing. I’m ready for something new.
#18362 Post timestamp creation should use whitelisted post statuses instead of blacklisted. One approach to solving a timestamp problem with Edit Flow custom statuses. Instead of blacklisting the post statuses that shouldn’t receive GMT timestamps, whitelist the ones that should.