UpdateChecker

Moved

Total Downloads: 21,403 - First Release: Oct 24, 2014 - Last Update: Feb 1, 2018

5/5, 48 likes
  1. Wulf

    Wulf Community Admin

    Keep in mind that the need for the ResourceId will be going away as we shift plugins to GitHub.
     
  2. Pretty pointless post then if you ask me ;) Thanks for mentioning that Wulf
     
  3. error, if i want set grant group admin updater.use ...
     
  4. wrong permission use updater.check
     
  5. This plugin doesn't fetch any latest info for plugins anymore, I ran 'updates' in console and it came up with no list of plugins that needed to be updated, but then I go to oxidemod and it tells me a different story..
     
  6. This plugin works but not 100% because a lot of new plugins doesn't have resourceid on cs file
    You can change it manually with the number you have on the URL adress:

    Code:
    http://oxidemod.org/plugins/updater.681/
    But I think, this plugin need to be fixed
     
  7. There is nothing to fix. Other plugin authors just have to set the resource id if they want to support updater. There is no other way for it work. It has to be identified somehow.
     
  8. okie, ty
     
  9. Hi Laser,

    Thanks for your reply

    This plugin return "unable to find last version of plugin" in console too, this is because they missed an information too or it's the plugin ?
     
  10. That means that it could either not reach the plugin page, or that it failed to read the version from it.
     
  11. Thanks you
     
  12. The plugin was not able to retreive the latest versions, either because the plugin does no longer exist on oxidemod, or because your server could not load the oxidemod page (server or website down).
     
  13. well I am getting this error message now and for sure these plugins still exist
    Updater] Couldn't get the latest version of plugin Better Chat
    [Updater] Couldn't get the latest version of plugin BuildRevert
    [Updater] Couldn't get the latest version of plugin AutoDoors
    [Updater] Couldn't get the latest version of plugin BotSpawn
    [Updater] Couldn't get the latest version of plugin ConnectMessages
    [Updater] Couldn't get the latest version of plugin ConnectionDB
    [Updater] Couldn't get the latest version of plugin Kits
    [Updater] Couldn't get the latest version of plugin CupboardRadius
    [Updater] Couldn't get the latest version of plugin FancyDrop
    [Updater] Couldn't get the latest version of plugin Godmode
    [Updater] Couldn't get the latest version of plugin HelpText
    [Updater] Couldn't get the latest version of plugin HeliControl
    [Updater] Couldn't get the latest version of plugin InfoPanel
    [Updater] Couldn't get the latest version of plugin CustomAnimalSpawns
    [Updater] Couldn't get the latest version of plugin Player corpse duration modifier
    [Updater] Couldn't get the latest version of plugin ImageLibrary
    [Updater] Couldn't get the latest version of plugin TwigsDecay
     
  14. Read above.
     
  15. i already read the post above mine and had already checked that at the time that updater could not find the plugins page i was able to.
    If it was unable to read the version from the plugin page it is not doing what it is supposed to do is it ? subsequently you get posts here,
     
  16. Code:
    [Updater] Couldn't get the latest version of plugin Rust:IO for Oxide
    [Updater] Couldn't check for updates of following plugins as they have no ResourceID set: Blueprint Manager, Economics, MonumentFinder, SDonate
    [Updater]
    Following plugins are outdated:# Copy Paste | Installed: 3.4.1 - Latest: 3.4.5 | http://oxidemod.org/plugins/716/# Stack Size Controller | Installed: 1.9.6 - Latest: 1.9.8 | http://oxidemod.org/plugins/2320/
     
  17. I am just adding to the list of people getting the ("[Updater] Couldn't get the latest version of plugin xxxxxxx ") on everything.
    Worked fine before this months wipe/update.
     
  18. Wulf

    Wulf Community Admin

    Means that those plugins do not have a ResourceId set. Not an issue with this plugin, it means that those plugins have no identifying info set. :p
     
  19. Actually, if I remember correctly, that has a seperate message. The above message means that the oxidemod page was not reachable or the version could not be parsed.