Fix for new Plugin Manager Enhancement

Well it seems I committed what I've described in the past as a "cardinal sin" when using the onTap framework. That is, I created a distribution that included a file that would be modified during or after installation.

The reason why this is a cardinal sin when using the onTap framework is precisely because of what I ran into today. I had made a couple of what I thought were minor changes to some code, but was having a problem with some other code and even though I didn't think they were related, I decided to "roll back" the changes just in case. It turns out they actually weren't related, so the small changes I made stayed in the code. However because my method of rollback involved unzipping the framework core archive (ontap32.zip) into my working directory, it overwrote the new XML file that the Plugin Manager uses to store version information for the previously installed plugins... And of course, like magic that meant it was suddenly interpreting two plugins as uninstalled when they were in fact installed.

Thing is, it's supposed to be safe to extract a newer version of the framework into your working directory. Because one of the framework's guiding principals is "never edit someone else's file", that should apply to the framework core equally as much as to those of us working with is. So just as I should never edit one of your files (and you should never edit one of mine), the framework should never overwrite your data files either.

So long story short there's a new copy of the framework core archive up on RIAForge that's now minus the Plugin Manager's new XML file so that when you update it won't be overwritten. However there's no real urgency for anyone to update the core at this point. Unless your copy is already tragically old. ;)