Author: Tom (Page 185 of 428)

If you’re working on a plugin or theme that’s tightly integrated with a user’s social profile then you may find yourself wanting to pull in photos from their Flickr account.

If you’ve read my blog for any length of time, then you know most of the stuff I share like this comes from either working on something for myself or working on something for someone else.

So, in a recent project, here’s how I used the Flickr API to bring Flickr photos into a WordPress plugin to display on the front-end.

Continue reading

Regardless of your experience with WordPress, it’s almost inevitable that – at some point – you’re going to want to experiment with caching your website.

Cache, Not Cash

For those who have a background in computing, you’re likely already familiar with caching:

• how it works,
• how to control it,
• some of the pitfalls,
• and many of its advantages.

If, on the other hand, you’re someone who wants a faster site, finds a plugin, and then begins turning options on and off, you may end up negatively affecting your site in some way.

Because WordPress is available a one-click install on so many web hosts, and because the plugin repository has a variety of caching plugins, it’s easy to get overwhelmed and/or try out a number of different plugins potentially altering the appearance of your site when users are viewing it.

And the latter happens to all of us. At least I hope. I had a cache issue late last week :).

Anyway, despite this laborious introduction, the purpose of this post isn’t necessarily to outline the advantages and disadvantages of caching. Instead, it’s meant to answer the question:

Should I use caching on a shared web host?

And though it’s not a difficult question to answer, it’s important to understand that you can only push the limits of your caching so far in that type particular environment.

Continue reading

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’s often the following commentary:

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 (at least 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.

Continue reading

If you spend enough time with WordPress, you may very well become interested in development. No, of course not everyone will do this.

They’ll continue to use it exactly as it is:

• A blogging platform,
• Or a content management system

But just as with operating systems, desktop software, mobile apps, etc., you may find yourself wanting to build things for WordPress.

So the natural question becomes:

“How do I go about getting started with WordPress development?

And there are tons, and tons of articles available for this. There are videos, there are courses, there are seminars, webinars, and so on.

So this is not going to be another post about the 10 things you need to do to get started in WordPress.

Instead, it’s going to take a different approach.

Continue reading