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.
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.
Every WordPress developer who have ever looked into database knows that transients can leave big mess. There are couple of plugins that already do cleaning, but they have a few problems:
- unnecessary complicated
- don’t remove all transients
- not multisite compatible
- performing direct database calls for deletion
Since I didn’t like all of this, I created Clean Expired Transients. It is simple, hooks to native WordPress hook that runs once daily, cleans all transients older that one minute, and it’s multisite compatible.
You can call it any time using simple
Clean_Expired_Transients::clean(); call from your custom code, or use it in your project.
It is also first plugin that I made available through Composer.
After several reports of issues from the title of this post, I decided to write a quick answers instead of writing separate each time.
It’s worth noting that from day one plugin’s description stated:
Although this plugin displays uploaded images out of the box, it will probably not give best possible look, so it’s recommended to create custom CSS styles for affected elements.
It is impossible to solve all of the problems people are having with displaying images because there is unlimited number of combinations: there are tens of thousands of themes, each theme can have multiple menu positions, and you can use different image size.
This means that each site requires a custom solution, you can do that by yourself, hire me or someone else, but you can’t expect from me that I do that for free for each of you. Imagine this plugin as a framework, it solves one thing for all and it’s enough for many, others need a little customization.
Mobile—using responsive theme
If you are having issues on mobile and you are using responsive theme, you should apply changes to it. Note that depending on what you want you can also change the output of the plugin with combination of CSS changes, not just pure CSS.
Mobile—using mobile-only theme
If you are having issues on mobile and you are using separate theme for mobile, you should apply changes only to mobile theme. There is no general rule how to do that, you can see in plugin that switches themes is there any way to know when you are on which theme, and you can also check against