All the new features, changes and fixes have been completed for 301tool 1.1.2 as of this evening. I will be finalizing testing, which includes making sure all the upgrade paths work as intended (1.0.0, 1.1.0, and 1.1.1). If all goes well, it looks like I may be releasing this update sometime this coming weekend.
Update (6/13/10): There’s one bug with pagination that I just noticed that will take a little time to correct.
Update (6/20/10): The pagination issue has been resolved. I ended up rewriting the code that determines what pages are shown in the pagination area. I will be resuming the planned testing regimen. As all work I do on 301tool is only in my spare time, the release date should still be considered as “soon” (namely, in a few weekends).
Update (6/22/10): Testing is complete! I’ll be prepping & packaging 301tool 1.1.2 for release very soon.
Update (6/23/10): I found a problem with the way session expiration was being handled, so the release has gone back to release candidate status until the fix has been fully tested.
Update (6/27/10): During testing on a webserver, it looks like when fopen is disabled, the update checker does not check the update file on the 301tool.com domain, as the XML file reader function is based off of fopen. I’ll have to switch that over to use cURL considering many other hosts are probably configured in a similar fashion. The change was quick. It works with cURL and falls back to fopen if cURL is not available.
Update (7/3/10): I should be wrapping up testing very shortly (this time), as I’m satisfied with the changes in 1.1.2.
Update (7/5/10): 301tool 1.1.2 has been released!!