When something gets sent through the gauntlet of 60+ mobile devices and comes out clean, we tend to take it pretty seriously. That’s why “Responsive Nav” is on our list and many other WordPress lists this week. While it’s a plugin that’s not specific to WordPress, it would be pretty easy to integrate with a standard theme. Accessibility and touch sensitivity in mind, Responsive Nav is worth a look.
One of our links last week basically said “don’t host your own videos in WordPress,” opting instead for some kind of content delivery system, whether it be YouTube, Vimeo or what have you. News is now out that WordPress 3.6 will allow you to add video through your media library and into a post easier than it’s ever been before. Piggybacking on MediaElement.js, the audio video format looks to continue the on-going discussion of “where should I host my media?” No matter what your take on where to host it, fact remains that it’s awesome to have audio video support in the core.
In releases this week we have BuddyPress 1.7, coming out with lots of bug fixes, new social features, and new features in general. I haven’t personally tested out the update, but have heard good things and look forward to trying it later in the week. What’s your favorite part of the update?
There are hundreds of front-end frameworks or starting points on the web today and it can be tough to know which are best for your project. Lucky for you, usabli.ca has made a great comparison chart of the top frameworks out there. From well-known Foundation to lesser-known Gumby, each framework shows browser support (which versions of IE), whether you can use LESS or Sass, and if the framework is responsive. I’m planning on testing out 1KB Grid after perusing this list.
It’s been an interesting week security-wise with WordPress and the folks over at Securi have added an extra bonus to “things to watch out for.” The Social Media Widget has been found to inject spam and other nasty things into your WordPress install and will eat it alive if not removed immediately. It may not be quite that extreme, but it takes a lot for a plugin to be removed from the WordPress plugin directory and that’s the case here.
If you were under a rock this weekend then you might not know about the large-scale botnet attack on WordPress sites. Folks are speculating that the botnet was designed to help make a larger, heftier botnet that could essentially take down the internets. The extent of how true that is doesn’t really matter, but what does matter is how you protect yourself. The main attacks were through the admin username with passwords being pounded in until there was success. Ways to prevent attacks? Get rid of the “admin” username, add a login attempt lockout system and install some security. I personally favor WordFence and made sure it was installed on all of my WordPress sites. You can never be too careful, so buckle up and keep your eyes peeled.