Today I updated the plugin I wrote almost a year ago, bringing to to version 1.1. It’s not a huge accomplishment but I am proud of it. The plugin is used by several of my co-workers and it’s pretty cool that it’s useful enough to continue adding to it. I came across an http header that allows me to guess a little bit more about the proxy or load balancer in use, so I added detection for that.
I finally got around to adding a simple icon to my plugin on WordPress.org. It was very easy! Here is how to can do it in just 5 simple steps.
Before you start
In your plugin folder you should have an assets folder. This is where you can add files for things like the Plugin’s icon, the header, screenshots, etc. The folder should be a top level directory, so it’s not going to be in trunk or tags. It sits right at the top. Keep in mind that images can only be in the JPG or PNG format, nothing else.
From the WordPress.org documentation: Image sizes should be the same as implied by the names. That is, banner-772x250.png should be 772 pixels wide by 250 pixels high. Similarly, icon-256x256.png should be a 256×256 square.
Step 1. Create an icon file, which is a JPG or PNG that is 256X256 pixels. Then name it icon-256x256.png.
Step 2. Add your new icon to the assetsdirectory.
Step 3. Use the following svn command to add the icon so you can check it in.
svn add icon-256x256.png
Step 4. Check in your changes.
svn ci -m "Adding icon for plugin"
Step 5. Check out your plugin’s page on WordPress.org. It should now have your new icon!
Often times WooCommerce Subscriptions will fail to renew for a recurring Subscription because Cron is either not working correctly on a site or because of this. For traffic based firing of Cron, I suggest using JetPack Monitor. It solves this limitation easily and effectively.
For troubleshooting when WooCommerce Subscriptions Not Renewing (or other Cron based scheduled events) I like to use WP Crontrol. It’s great for getting a better idea of what’s happening with your site’s Cron jobs and most times the plugin will print an error on the WP Crontrol configuration page that will give you the right direction to head in for troubleshooting. Often times you will need to work with your hosting provider to resolve the issue. If you are running your own server, then this will be the same error that shows up in system logs.