On Wed, Dec 2, 2009 at 1:08 AM, Markus <[email protected]> wrote: > Did you upload the RSS plugin? > > action.changes says: 09/20/09: rss.php
My last changes to the plugin look like they were Nov 3. I just uploaded the latest I have to the server, so if I didn't before it is there now. I actually store mine in two places--the download directory and the active server directory. This is to block someone from uploading a hacked plugin over something running live on my sites. So it's possible I only uploaded it to the one directory and not the other. But it is working for me now... > I would provide two feeds: one for BoltWire releases and one for > plugin updates. I think it's worth the time as every software site > should have this – for good reason. This is a good idea. Not sure how to generate a feed for BoltWire releases as it's all just put on one page. Not generated dynamically. So there's no search list to use. As for the plugins, that should be easier, but I'm not sure what content to generate. The list on the site simply lists the plugin name and lastmodified date. No way to easily extract release information. In fact, I don't generally even put release information on the plugin pages. I'm doing good if I can just keep them running. But if I find some time, I'll look into it. At least having a page where the information is readily accessible is not too much harder to get to than a rss feed. > Two more thoughts about your action.changes: > 1) What about linking the plugin column list entries to the plugin > page? It's the Internet... :) Good idea. I'll do that now. > 2) A plugin that compares installed plugins (and the installed > BoltWire version) with the versions listed on boltwire.com would be > nice. Unfortunately, I don't have the time at the moment. Well, a feed > would certainly do it for now. Yes, we've discussed that before and it would be a good idea. There are some complications, namely how best to do it, but it is possible. Again the issue is time. Probably what we would need to do is to add a version number to every plugin on BoltWire (150+). Then find some way to extract that (daily I suppose) from all the plugins available on BoltWire to generate some kind of data file. Then the script would download the data file, grab all the plugin variables, compare the two and output some report based on that information. We could do it based on last modified dates, and that might work fine, but if you edited a local plugin script for some reason you might get false output. Unless you always ran the checker script before making changes. Yes, that might be a good way to do it... It would probably be the easiest way. If I find some time I'll try and throw something together, just for kicks. Might be kind of fun. Just no promises on when I might get around to it!!! Cheers Dan -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
