There is mounting excitement over the WP REST API being added to core and rightly so! It is going to fundamentally change the WordPress landscape and open up all sorts of new possibilities. Developers are drooling over all the cool stuff they are going to be able to build. Exciting times!
When it comes to using the REST API with themes, it may not always be the best choice.
16 Feb 2015: This post attempted to answer the ‘why’ of Jetpack’s bloat. On 23 January 2015, at Pressnomics, Matt Mullenweg talked about Jetpack being the reason that WordPress wasn’t in decline
and a key factor in the fight against WordPress’s competitors. Although I don’t necessarily agree with this or that it makes Jetpack’s approach okay, I do absolutely believe that Matt believes this very strongly. It actually validates most of this post – although I now believe the driver is helping to grow the platform, rather than simple business benefits for Automattic.
Recently, there has been some discussion around whether Jetpack is bloated. Hmm, actually, we’ve been talking about that for years… Anyway, the interesting part to me isn’t whether Jetpack is bloated, it’s why Jetpack is bloated.
Scary post title right? Well, I wish it was link bait, but it’s not. This is really serious.
Yesterday, it was announced that there was a critical security vulnerability with versions 3.0 to 3.9.2 of WordPress.
While catching up on some old podcasts, specifically Episode 82 of WordPress Weekly, I came across a discussion about WordPress beta testing. The discussion centers around the problem of bugs not being caught during beta testing because there just aren’t enough beta testers.
To me, the solution seems straightforward – but that may be because I worked in the software industry for 10 years and have experience in software release management, so I’ll take the long path and set the scene properly.
I’ve been using using and developing on WordPress for almost 10 years. In all that time, the single most important (WordPress related) thing to happen to me was WordCamp Gold Coast 2011, which was held 5 years ago today.
I’m writing this post because of the very sad passing of Kim Parsell, but it’s not going to be about her. Much has already been said by people who knew her far better than I. Continue reading
For those of you who don’t know, there’s a new social news site for WordPress, called WPVote. I’ve been using the site for a couple of days and while the concept is great, the quality of entries are poor at this early stage. Continue reading
The upcoming release of the DualFeeds plugin for WordPress includes an optional feature which promotes the plugin by displaying ‘Powered By DualFeeds’. I want to know what you think about this – is it okay for plugins to promote themselves? Continue reading
Editorial Note, 12 August 2011
So, some things have changed since 2007 – I now use the very same permalink structure I warn against below. There are a few reasons for this:
- WordPress now deals with permalink structure changes much better these days and will automatically 301 redirect the old URLs for you (in most cases).
- Even if WordPress didn’t do it automatically, I’m now comfortable setting up 301 redirect via .htaccess (which is what I do, because I don’t quite trust leaving it to WordPress).
- Having the category in the permalink does provide SEO benefits – I don’t care so much about getting the keywords in the URL (you can get that through postname), but I do like the benefits for the site structure (pseudo folders creating a silo structure).
There are still some problems with the
/%category%/%postname%/ permalink structure: if you have a lot of pages (more than 50ish), this permalink structure can really slow down your site. Having said that, even this problem is likely to disappear, as it looks like they’ll change the way this works in WordPress 3.3.
This is only my second post since launching www.scratch99.com and I’ve already changed the Permalink structure! In this article, I examine why my original structure:
doesn’t work for me. Continue reading
This post was supposed to be titled All My Loving and announce the adoption of the CommentLuv plugin. In combination with my very own KeywordLuv plugin, I would have indeed been giving you all my loving. Unfortunately, I had a problem with CommentLuv and have deactivated it. For now…
Lesson to be learned: When you are sitting on semi exclusive news, POST IT! I originally wrote this on 29th March, but ran out of time to post it because of our move from China. Since then, Mark Jaquith himself has written about this, and others such as the Weblog Tools Collection have picked the story up. I decided I’d go ahead and post this, because my point about it being removed without warning still stands.
When I recently finished the LocalCurrency plugin, I tried adding it to the various WordPress plugin lists that exist and found that several are gone!
I’m not talking about individual lists on people’s blogs listing which WordPress plugins they use. There are many of these! I’m talking about complete lists or repositories of all WordPress plugins in existence (or as close as possible).
In this post I look at a several WordPress plugin lists which have been removed, are down, or don’t seem to have any people running them. Continue reading
After listening to recent episodes of the WordPress Weekly podcast (episodes 67 and 68), I was surprised to learn that in future versions of WordPress, the Delete link will be replaced with Trash. Continue reading
In case you missed it, there’s a new WordPress podcast in town: daWPshow. Fantastic! I think it’s great that people are willing to put their time into creating content about WordPress! Now, with that out of the way, I’m going to lay down some tough love for the show.