Search: “plugins” (Page 2 of 146)

Supporting free WordPress plugins has been interesting to me for some time now because there are a number of inherent challenges that come with managing a freemium-based product.

WordPress 4.4 was released last week and there’s no reason for me to cover all the information about it. You can read all about it on:

– Post Status
– WP Tavern
– WordPress.org

As with any WordPress upgrade, there comes the commentary that:

The latest WordPress upgrade broke my site.
And I get it:

1. You’re a user.
2. Your site is powered by WordPress.
3. You upgrade WordPress.
4. Your site breaks.
5. Thus, the WordPress upgrade broke your site.

I’m likely preaching to the choir with this post given the audience of which I’m aware, but in case anyone reads this is not a WordPress developer and is someone who is tech-savvy and tries to say on the up-and-up with WordPress, then perhaps it’ll be useful.

If nothing else, I can reference this for others with whom I work as a means to explain something without doing so over and over again (and hopefully in a much clearer way).

The short of it: Just because you upgrade WordPress and your site breaks does not mean that the WordPress upgrade broke your site.

This sounds a bit like circular reasoning, doesn’t it? Bear with me.

A couple of days ago, I shared that I was looking to put some of my plugins up for adoption. I’ll go into a bit more details as to why later in this post, but I’m happy to say the WordPress plugins are adopted.