Completely Broken Now?

After I installed this last update, it appears to be completely screwed up now.

There are a ton of plugins it says are at version 1.0.0, which is not true, so it is showing updates for like 20 plugins.

Not Found contains a plugin that it used to find.

Not Loaded seems to be fixed/accurate now.

And before the update, for the past 12 hours it was showing nothing for Not Found, even though there should have been 4. But that was version 4.2.8.

19 hours ago, dustyhansen said:

After I installed this last update, it appears to be completely screwed up now.

There are a ton of plugins it says are at version 1.0.0, which is not true, so it is showing updates for like 20 plugins.

Not Found contains a plugin that it used to find.

Not Loaded seems to be fixed/accurate now.

And before the update, for the past 12 hours it was showing nothing for Not Found, even though there should have been 4. But that was version 4.2.8.

Since I don't have access to the uploaded plugins, I don't know their version and author, so I fill in the config only their name, you can upload them so that updatechecker fills in the correct version and author, or put the correct versions in the config file, but even if you update the uploaded plugin, updatechecker still won't recognize its new version itself, it could do this before, but I removed this function because the plugin authors do not adhere to the same design and I can't find out where in the file the version is indicated with 100% so that this does not cause bugs. You can add these plugins to ignore so that their version is not checked.

3 hours ago, tofurahie said:

Since I don't have access to the uploaded plugins, I don't know their version and author, so I fill in the config only their name, you can upload them so that updatechecker fills in the correct version and author, or put the correct versions in the config file, but even if you update the uploaded plugin, updatechecker still won't recognize its new version itself, it could do this before, but I removed this function because the plugin authors do not adhere to the same design and I can't find out where in the file the version is indicated with 100% so that this does not cause bugs. You can add these plugins to ignore so that their version is not checked.

No offense, but I kinda feel like you made the plugin useless now.

If it can no longer update version numbers, then what is the point? How is it seeing the version number for my other 130+ plugins but not these 20? I don't understand.

I'm not going to put 20 plugins on ignore because of your change. If it no longer updates version numbers then I don't see the use of this plugin.

20 hours ago, dustyhansen said:

No offense, but I kinda feel like you made the plugin useless now.

If it can no longer update version numbers, then what is the point? How is it seeing the version number for my other 130+ plugins but not these 20? I don't understand.

I'm not going to put 20 plugins on ignore because of your change. If it no longer updates version numbers then I don't see the use of this plugin.

it's only for those plugins who are unloaded, unloaded plugins doesn't listed in oxide list, so i roughly scan them from their directory

Changed Status from Pending to Closed

Changed Fixed In to Next Version