Hi everyone!
Sorry for the long silence, it has been a busy time. But I have some developments with Twools and wondered if any of you would be happy to test?
The RSS feeds have never been totally valid RSS feeds, but most RSS readers have read them without issues. Some, however refuse. So, I’ve worked on making Twools produce completely valid RSS feeds. Part of the issue was the way Twitter outputs the date and time of tweets very strangely. Also, technically the
So, I’ve fixed the date/time issue and I’ve moved the screen name to a
But, most importantly, I’ve improved caching!
Before, Twools cached the response from the Twitter API. This meant that Twools saved the response to the cache as a json file. If the cached file already existed it would still have to work on the file each time the feed was reloaded. This caused a lot of overhead and was quite slow. I’ve now made Twools cache the resultant RSS feed which improves things quite considerably.
If you could test it, please do. Firstly, locate the generateRSS.php file (which should be in /wp-content/plugins/twools/home/incs/) and rename it to generateRSS.old. Then upload this file in its place:
https://dl.dropboxusercontent.com/u/95261/generateRSS.php
Finally, some of you were looking at a way to display all the current “burned” feeds- or the feeds in the cache. If you’re looking at doing that, then could you try uploading the following file to your /wp-content/plugins/twools/home/ folder:
https://dl.dropboxusercontent.com/u/95261/cachedfeeds.php
Then load it in your browser. It should be something like http://yourwebsite.com/wp-content/plugin/twools/home/cachedfeeds.php
This will show you all your current cached feeds.
Let me know what you think!
I hope to make a few other changes before I push this out for version v.0.12.0 including fixing the Twitter DM cleaner.
