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;
If you want to use
crontab Linux command with WordPress, you should first read this great explanation of crontab by Kevin van Zonneveld. Seriously, this is probably the simplest guide ever.
Now that you read it, you want to use it for WordPress. You don’t want to store output so you are trashing it, and you are calling WordPress pseudo cron functionality, located in
/wp-cron.php file. We use curl for this.
* * * * * curl http://example.com/wp-cron.php > /dev/null 2>&1
example.com with your actual domain. In this example we use
crontab every minute, but you can follow this guide for setting any value.
Don’t forget to save new settings when you are done!
Many had same experience:
- schedule couple of posts to publish over time
- something happens and you need to publish a new post and reschedule each one
- you got an idea so you have a new post that you need to place somewhere between scheduled posts and reschedule all
In short, this is one of the problems Post to Queue tries to solve. Instead of manually scheduling posts, you put posts in queue, and they are published after chosen time since last post is published, on selected hours and days.
If you publish a new post, queue is prolonged so time needs to pass since that new post. If you got a new idea, you can place that post wherever you want in queue, since you just reorder queue.
This is a plugin with actions and filters everywhere, and since everything is in PHP classes, you can extend it even more to any option you want.
Try Post to Queue now.