SiteTree 1.5.1 has been released to patch some bugs that could have affected the upgrade of the data related to the excluded posts and pages but it doesn't introduce any changes to the major version published three days ago. Unfortunately, the exceptions set with SiteTree 1.5 will be lost — sorry about this. If you ...
Slightly later than expected but here we go! In a matter of minutes, your outdated copy of SiteTree will be ready to morph into SiteTree 1.5 — prepare yourself! Version 1.5 is focused on security (3 vulnerabilities solved), general improvements (amongst the many fixes, 7 major ones join to the list) and, last but not ...
Early the past week, while the latest updates were reaching your WordPress site, the counter on WordPress.org leapt over 10K downloads. Though I didn't set any milestone, I'm very glad so many of you are using my plugin. When I first published SiteTree, 4 major releases ago, I did it without any expectation nor I ...
Since the release of SiteTree 1.4 — about a week ago — some users reported a variety of problems affecting the Google Sitemap feature. Most have been fixed with the latest two updates but one of them (an encoding error in the titles and the captions of images listed in the Sitemap) is still showing ...
These releases solve various issues with the Image Sitemap feature just introduced and other bugs reported by users (Thank you!). Note: this post has been updated on 14 January 2013. Among the problems fixed, there was a critical one that deleted the list of excluded posts and pages while upgrading from SiteTree 1.3 or later. ...
There isn't a better way to start a new year than creating something new or unique in its own way. Packed with over 1800 freshly written lines of code, SiteTree is ready to be downloaded or upgraded once again. SiteTree 1.4 is lighter, more user-friendly and you'll find the administration area better organised and more ...
Once you move away from the first couple thousand lines of code, debugging becomes surely one of the main tasks leading the development cycle. At this stage, to have something more versatile to use than error_log() and var_dump() is almost a need ... the truth is that I forgot an error_log() call in production code ...