Page 318 of 428

Comment Images 1.11.0 – Now Available

August 5, 2013 / Tom / 0 Comments

Last week, I had an interesting request for my Comment Images For WordPress plugin:

I wanted to make the default DISABLE so I could turn it ON on the ones I need it, instead of having to go through 200 posts and turn it OFF on 190 posts, that’s all. But if that’s not possible I understand.

Truth be told, this is a scenario that I’ve never thought of, but if you’re someone with a blog who has hundreds (or even thousands) of posts, then being able to disable or enable the feature across the board makes sense.

Retiring WP Audio Player For WordPress

August 5, 2013 / Tom / 0 Comments

With the recent release of WordPress 3.6 and its built-in support for audio files, I’m opting to to halt development on WP Audio Player for WordPress plugin.

Here’s the thing: This has nothing to do with WordPress folding something into core that was once available via plugins and putting a plugin “out of business.”

Mostly, it has to do with my personal preferences and opinion behind the core libraries used in WordPress 3.6.

Improve Your WordPress Development Skills

August 2, 2013 / Tom

Comments are closed on this post. If you have questions or comments, email me!

Last night, I sent out the first email to the subscribers for the Improve Your WordPress Development Skills class that I’ve discussed over the past couple of weeks.

The email hit on the following points:

What’s covered in the class
When the course will be held
The pricing
Some of the bonus content that’s coming after the course
…and more

Quick Tip: Disable Auto-Updating of CodeKit Settings

August 2, 2013 / Tom / 0 Comments

When it comes to CodeKit, there are normally global CodeKit settings that I use; however, a number of the projects that I work on often result in some minor deviation from my core settings.

For those who have used CodeKit regularly, you know that you can set per-project settings, but if you’re using a project that’s under source control, there’s likely one irritating factor that you’ve noticed.

The Dangers of Using pre_get_posts in WordPress

August 1, 2013 / Tom / 0 Comments

In the previous post, I talked a bit about using `pre_get_posts` and how to efficiently exclude categories from the main loop.

Of course, in posts like that, the code is meant to be a point of reference or a starting place for which more advanced functionality can be written.

But one thing that I failed to mention about using `pre_get_posts` in WordPress is that it’s not limited to the public facing side of the site.

Tom McFarlin

Comment Images 1.11.0 – Now Available

Retiring WP Audio Player For WordPress

Improve Your WordPress Development Skills

Quick Tip: Disable Auto-Updating of CodeKit Settings

The Dangers of Using pre_get_posts in WordPress