In most cases, the feed can be accessed by typing in “/feed” after your domain URL.

Ever since the release of the Plugin Update Checker library, one of the most common questions asked has been this: “How can I secure my download links so that only users who have purchased my plugin can download an update?

You might already have some kind of customer authentication mechanism in place that just needs a bit of tweaking to be used for updates, or you might need to build your own from scratch. Then, when they install the plugin, there’s a link to enter the license key.

I won’t include the license management code here because it’s beyond the scope of this post and built for that specific plugin, but the user interface looks something like this (click to enlarge): Now, how do we add our security token to each update request?

Since its purpose is to make your content easy to index, it can be shared in a myriad of ways to help promote the business.

It’s kind of like giving other people a table of contents to your site.

Turns out there isn’t a plugin (ok, just one, that’s gone over 2 years without updating) that can help you out with this, you’ll have to do some diving into code or simply have one of our partners do it for you. You can tweak the default feeds by adding custom content to your RSS Feeds, or even adding a post thumbnail to your RSS Feeds.

The default RSS and Atom feeds are enough for most users, but you may wish to create a custom RSS feed for delivering specific type of content.

Sites that publicize content, RSS reader apps and even some social media sites use this information to share your material.

Although it’s not nearly as popular as it was in 2005, it’s still an easy and viable method to share content.

You can do that by using the (Again, license management is beyond the scope of this post, so I’ve omitted most of the code that deals with loading and validating licenses.