The first in a series from Wptuts+ covering WordPress 3.6’s Heartbeat API.
Anonymity is an option on the internet, but it is not an option for ethical business in my opinion. If you are running a serious website, or especially selling something, you should say who you are.
Agreed. Sort of. Anonymous businesses like WP Avengers are bullshit. However, anonymous blogs offer people a way to voice opinions they might not be able to normally share.
Beautiful & seemingly well coded. Nevertheless, “read more” links are a fucking pox on the internet – and this theme relies on them. Heavily.
Considering an upgrade to PHP 5.5.x? It’s dangerous to go alone! Take this.
Nothing against Yoast’s SEO plugin, but this shit is getting dropped into the mu-plugins folder on every site that I run.
I’ve spent a lot of time since WordCamp San Francisco thinking about Matt’s expressed desire for faster, Chrome-like automatic patching in his State of the Word. Mainly, I got caught up in the “how” of it. Like how could they balance development on the trunk alongside rapid-fire, stable core releases?
Then I read about the move to develop.svn.wordpress.org & Grunt for WordPress core development this morning and realized that it’s only a matter of time before WordPress has its own Canary build.
For the uninitiated, Chrome Canary is a version of Google’s Chrome browser that has the most cutting edge stuff crammed into it. The stuff that’s not quite ready for the general public, but still needs testing. Firefox is doing something similar thing with Aurora.
But WordPress can’t just go and call their cutting edge test branch Canary, can they? So, after combining the list of jazz greats in the version history along with my middling knowledge of the genre, I propose the early-adopter build be named after an innovator who was notorious for shaking things up: Ornette Coleman.
Think about it. WordPress Coleman has a pretty nice ring to it, right?
Anyway, now that I’ve given the project a name, I’ll just be hanging around waiting for an auto-updating build. Don’t worry though, I can be patient…
Addendum: As my buddy Mike Schroder pointed out in IRC, you could totally do something like this right now with the Beta Tester plugin and the bleeding edge nightly builds. But I’m thinking about something that’s a little less likely to break things as trunk development progresses.
Addendum 2: The Legend of Curly’s Gold: Yes, I realize that WordPress 4.5 used “Coleman” as its release name. This post was written 3 years before that release dropped. Nobody likes a pedant.
While following the directions on how to set up 10up’s wonderful dev environment for WordPress, I noticed that Vagrant was using a .pkg installer.
Now there’s nothing wrong with installing software that way. Hell, doing things via a graphical installer is easier for most end users. But Vagrant isn’t really something that was made for “end users”. It’s a command line utility to create and manage development environments.
So I did a quick check to see if I could install Vagrant via my favorite package manager, Homebrew. And while there’s nothing in the vanilla install of Homebrew, I stumbled onto an independently maintained add-on called brew-cask that allows you to install Mac applications on your computer via the command line.
Using it is as easy as loading up your terminal and typing:
brew tap phinze/homebrew-cask && brew install brew-cask
Then, to get Vagrant installed, just run this command:
brew cask install vagrant
Hell, you can even install VirtualBox if you’d like:
brew cask install virtualbox
Pretty nice, right?
Oh, and if you’ve been holding out on using Vagrant in your dev environment, consider giving it a try. It’s way more flexible than MAMP and nowhere near as quirky.
Have you guys heard about Instant Server? It’s pretty rad. Basically, you push a button, wait a few seconds and they give you 35 minutes of usage on an SSH-able server. Once the 35 minutes is up, you can either pay to keep it running or they trash the server instance.
Anyhow, after trying to figure out some of the fun things I could do with it, I’ve come up something that security minded WordPress folks might find useful.
There’s this command line security scanner called WPScan that performs a bunch of non-intrusive checks against WordPress installs. Folks with Linux based systems can install and run it easily. It’s also a fairly trivial install for folks who’ve set up Homebrew on their Macs. But if you don’t want to mess with installing Xcode on your MacBook or you have a (gag) Windows machine, try this out…
sudo apt-get install libcurl4-gnutls-dev libopenssl-ruby libxml2 libxml2-dev libxslt1-dev ruby-dev git make && git clone https://github.com/wpscanteam/wpscan.git && cd wpscan && sudo gem install bundler && bundle install --without test developmentruby wpscan.rb --url example.com --enumerateexample.com with your own domain.)If you stay on top of core, plugin & theme updates, you shouldn’t really see anything surprising. But it’s always better to know your threats and limit your exposure, right?