There are many WordPress plugins that cache full HTML pages. Some are using disk, some memory, but what is common for them is that they are using your server resources.
CloudFlare offers many services that enhance sites and among them is CDN (Content Delivery Network) that caches and serves content from its servers. By default, this feature is enabled for static files, like images, CSS or Javascipt, though it is possible to enable serving of all HTML pages this way. That means that cache is not stored on your server and as a plus it is served from CDN.
Problem with this is that on many times you want to remove some content from cache. For example, you publish a post and you want to have fresh copy of home page. There are a few plugins that use CloudFlare API to remove or purge content but they have a few problems: they include other features offered by CloudFlare, badly coded, not extensible, or limited purging coverage.
To solve this, I created Purge Cache for CloudFlare and its premium extension Purge Cache for CloudFlare Plus. These are written from ground up with some things in mind: to be simple, extensible, lightweight, doing only one thing.
Free basic version cleans cache in scenarios that are most common for most sites. Premium extension goes even further and cleans cache of even more pages and for more things, not just new/edited post.
When setup right, CloudFlare cache and CDN could greatly improve speed of your site, while at the same time not using any of your server resources.
If you aren’t using dedicated server or VPS, your host is probably having limit on number of emails that your account can send in some period.
You should see this in your host’s documentation or support to find this out. For example, SiteGround for its StartUp and GrowBig WordPress hosting plans is having a limit of 400 emails sent per hour. You can see other limits on MailPoet site.
Most sites don’t reach this limit, but there are cases where sites send large number of emails and require more resources than available. Other, even those that don’t have limits, send large number of emails at once and create heavy load on server.
Because of this, I have created solution for WordPress that allows you to behave according to limits while still sending all emails you want.
Simple Email Queue is a free plugin for WordPress aimed to developers who can set limits by using of filters and then using dedicated function (that is alias of built-in
wp_mail()) for sending emails.
Simple Email Queue Plus is a premium plugin aimed to all users that provides user interface for free plugin and additionally reroutes all emails sent using built-in
wp_mail() so that it passes restrictions.
Both plugins are very light, try to add minimal footprint to your WordPress installation and use minimal resources and database options.
Maintenance and security releases, or minor releases for WordPress should be safe, without breaking sites, plugins, or themes, but this year WordPress had some versions that break sites with automatic updates. Since plugins and themes can get same treatment too, some people don’t want this kind of updates, even if their imporve security for previous versions.
While there are plugins that prevent background automatic updates, they don’t do it by default and you need to manually choose what kind of automatic updates you don’t want, I have created new plugin that does this but that works out of the box, without need to select any options, automatically with activation.
Admin Bar Plugin Switcher is a simple plugin that can mostly benefit developers who want to quickly see something before and after plugin is activated.
Go check it out.
This little code snippet can be used to get ID of a Tumblr post if you have URL of post, no matter if there is unique slug at the end (
http://staff.tumblr.com/post/122809548365/apologies-for-the-disruption-some-of-you) or not (
http://staff.tumblr.com/post/122809548365), or if it’s on custom domain (
Can be useful when you have to deal with Tumblr API.
$full_url = 'http://staff.tumblr.com/post/122809548365/apologies-for-the-disruption-some-of-you';
$path = parse_url( $full_url, PHP_URL_PATH );
$path_components = explode( '/', trim( $path, '/' ) );
$tumblr_post_id = $path_components;