UPDATE: wp-days-ago has been updated to v2.6.
It turned out using WordPress core for a potentially massive amount of AJAX calls was a bad idea; the way WordPress handles AJAX basically loads the entire WordPress core on every single call, which put quite a lot of strain on the server and took a while. In this maintenance release I’ve modified the AJAX method so that it will only actually use AJAX if a post or page is published before a certain threshold. The plugins show publish date information if variety of different ways when the content is fresh, not so much when it’s old. So if it’s older than the threshold, the date information will be displayed without AJAX. This makes everyone a lot happier.
Changelog from 2.5 to 2.5.2:
- Bugfix: Fixed a major bug that happened when using the wp_days_ago method. Thanks to user heinnge for reporting this.
- New feature: Added a threshold parameter to control when AJAX should be used and when the plugin should automatically fall back to the old way of displaying information. After a day, the plugin doesn’t display any detailed information anyway so there is no need to strain the server with a lot of AJAX calls. The information displayed by wp-days-ago will of course be updated when your cache plugin invalidates the content and rebuilds it. The value of the wp_days_ago_ajax method threshold paramterer should match the configured invalidation threshold of your cache plugin.
- Change: Optimized date calculation and database access code.
This update is recommended for all users who use the AJAX functionality of wp-days-ago. Get the latest version from the WordPress plugin repository or use WordPress’ plugin update functionality if you already use wp-days-ago.