Fixed Plugins not being able to saveConfig

Discussion in 'Rust Discussion' started by NexusBR, Feb 7, 2015.

  1. NexusBR

    NexusBR

    I just want to confirm if someone else are having problem with SaveConfig after the update 2.0.266?

    It creates the default config but does not save a updated one.
     
    NexusBR, Feb 7, 2015
    #1
  2. Wulf

    Wulf Community Admin

    There seems to be an issue with it from what I've tested. We're looking into it to see what happened.
    [DOUBLEPOST=1423347143][/DOUBLEPOST]Edit: They actually appear to be working just fine. My plugins are adding to and saving updates just fine.
     
    Wulf, Feb 7, 2015
    #2
  3. NexusBR

    NexusBR

    I just tested my the modified versions that you posted.
    And none are saving config.
    Or anyone that i modified.
    None of my plugins are saving the updated self.Config.Variable to the files.
    The config files are not being modified.

    Did you really checked if the file configs changed?

    I'm using Windows 8.1, i don't know if that really matters.
     
    NexusBR, Feb 7, 2015
    #3
  4. Wulf

    Wulf Community Admin

    Yes, I checked with 5 of my plugins.

    Code:
    self:SaveConfig()
     
    Wulf, Feb 7, 2015
    #4
  5. NexusBR

    NexusBR

    I just changed the self.Plugin on the commands.

    No errors.
    And still none of my plugins are saving as was before 266
     
    NexusBR, Feb 7, 2015
    #5
  6. Wulf

    Wulf Community Admin

    I'll look into it more. Do you have any code snippets as examples of what you are using?
     
    Wulf, Feb 7, 2015
    #6
  7. NexusBR

    NexusBR

    Does this "Added DynamicConfigFile path restriction to prevent placing config files anywhere" could have anything todo?
     
    NexusBR, Feb 7, 2015
    #7
  8. Wulf

    Wulf Community Admin

    If your plugin is trying to save outside of the config directly, yes, otherwise it shouldn't.
     
    Wulf, Feb 7, 2015
    #8
  9. NexusBR

    NexusBR

    The most simple plugin that you can test is the Admin Door Unlocker, http://oxidemod.org/attachments/admin-door-unlocker-lua.6152/ that you posted.
    [DOUBLEPOST=1423349574][/DOUBLEPOST]
    I'm using the default "self:SaveConfig()" on all my plugins
    [DOUBLEPOST=1423349661][/DOUBLEPOST]Download admin door unlocker and run on console: adu.toggle and see if the config file changes.
    I tested tons of times with all my plugins and none worked.

    Maybe this is a Windows 8.1 issue with the new update, I don't really know, But it was working before the last update, That is for sure.
     
    NexusBR, Feb 7, 2015
    #9
  10. Wulf

    Wulf Community Admin

    It's not working for me with your plugin, but all of mine are. I do handle my configs a bit differently than your ones though.
     
    Wulf, Feb 7, 2015
    #10
  11. NexusBR

    NexusBR

    Because was an error with the last update.
    Try change the line 122 from self:Log("[" .. self.Config.Settings.ChatName .. "] " .. message ) to print("[" .. self.Config.Settings.ChatName .. "] " .. message )
    [DOUBLEPOST=1423350475][/DOUBLEPOST]I just tested on a server running an older version of Oxide.
    And it saved the file normally.
     
    NexusBR, Feb 7, 2015
    #11
  12. Wulf

    Wulf Community Admin

    I don't see how your error relates to this.
     
    Wulf, Feb 7, 2015
    #12
  13. NexusBR

    NexusBR

    Anyways, i did downgraded Oxide to the previous version and the files saved just fine.
     
    NexusBR, Feb 7, 2015
    #13
  14. Wulf

    Wulf Community Admin

    It seems to be an odd case. Some of my plugins are saving fine, some aren't. It may be that commit after all. I'll test without it and see. Thanks for the report. :)
    [DOUBLEPOST=1423352804][/DOUBLEPOST]Fixed in upcoming snapshot and release.
     
    Wulf, Feb 7, 2015
    #14
  15. NexusBR

    NexusBR

    Thanks now is working fine! ;)
     
    NexusBR, Feb 8, 2015
    #15
  16. Wulf

    Wulf Community Admin

    Good to hear, thanks for confirming!
     
    Wulf, Feb 8, 2015
    #16
  17. NexusBR

    NexusBR

    I tested again with the newest update, And are still working.
    If "Added support back for null JSON type, as it turns out it wasn't causing any issues." is not the problem what was?
     
    NexusBR, Feb 8, 2015
    #17
  18. Wulf

    Wulf Community Admin

    It was apparently the lack of self.Object causing the issue. @Hatemail did more testing and figured that out. We'll have to get a proper API going soon to get rid of that reliance.
     
    Wulf, Feb 8, 2015
    #18