[Dev-Nightly] Rest of config is swiping after /woo register

[HappyHarm]

When you use /woo register to key the key for the first time it saves the key to the config but swipes the rest of the config http://prntscr.com/9s20s2

[ethsmith]

I looked at the code and I know exactly what's do it.

[ethsmith]

I will try to get on a PC in 15 if I can and fix it

[ethsmith]

I will have it fixed today after i'm out of class.

[HappyHarm]

See that you did some commits in the dev-nightly with the config? Is the issue solved?

[ethsmith]

@HappyHarm should be I gotta jar download in releases section.

[HappyHarm]

Need to compile it with java 7 for myself. Will do that somewhere this afternoon.

[JayWood]

I've ran the command numerous times this morning, cannot duplicate.

[ethsmith]

@JayWood I fixed it in the commit I made a few days ago

[HappyHarm]

Just tried the newest build and it looks like it's still not fixed

[ethsmith]

@HappyHarm it's weird, for some reason people that used the alpha builds say this still happens (mmuziek tried so many times that I guess it flushed the cached data and started working correctly for him) I am trying to find a Java command that deletes cached data or build info for earlier jars

[ethsmith]

It may be the fact that the code says that 'key' only instead of pointing at 'WooMinecraft.web.key' it's a location statement and I'm sure I changed it to be 'WooMinecraft.web.key' and @JayWood changed the code in the register command back to just 'key' but I'm not sure why

[ethsmith]

I am working on a few things and will push them to dev nightly later today

[HappyHarm]

Ok then, thanks for the quick response :)

[JayWood]

@TekkitCommando WooMinecraft.web.key was the nested config, and the config is no longer nested.

[ethsmith]

@JayWood Ah ok, that's how I know the data is cached on my server then cuz it is still nested for me even with the new jar.

[JayWood]

@TekkitCommando I believe the issue may be with saveConfig here:

Maybe we have to get the entire config, and then write it?

[ethsmith]

@JayWood I don't see why you would, it worked fine before. plugin.saveConfig() should work fine and setting the key shouldn't effect the other config options. I don't see you having to do plugin.getConfig().saveConfig(); but I mean you could try

[JayWood]

@TekkitCommando I can't do anything until after work today, it's currently 9AM, so nothing from me until 5PM [ GMT -5 ]

Admittedly I didn't test that command my bad I'm used to having a full QA team at my side 😄 If you have time give it a go, if not I'll have a look after work.

[ethsmith]

@JayWood I don't think that .getConfig().saveConfig() will even work actually xD I will give it a try :P Oh yeah a job, I need to get one of those things. Maybe I will find a job in Python development or PHP/Java after I finish my classes lol

[ethsmith]

@JayWood I tested my theory of using getConfig and saveConfig and it was a fail :/

[JayWood]

@TekkitCommando @HappyHarm is this still a thing?

[ethsmith]

I am not sure, my computer is not working correctly, I bought some parts to fix it and then I will get the latest jar and test this. Sorry for the inactivity, like I said I bought some parts so maybe I will have the JDK installed today and be back to code again :D

[HappyHarm]

Idk my hosting got cleared a week ago and didn't got time to re-setup everything. Maybe I can test it this evening, if I forgot remember me about it :P

[HappyHarm]

Yep issue is still here. Sorry for the delay, forgot it as expected :P

[ethsmith]

I will restructure the config code today if i get the time :)

[ethsmith]

@JayWood This was fixed right?

[JayWood]

No, purely added a todo to look into it.

[ethsmith]

@JayWood 0-0 Ok I will fix it real quick.

[JayWood]

@TekkitCommando - this is now fixed. Though has yet to be merged into master.

[ethsmith]

@JayWood I ended up changing the code that should have fixed it but my freakin git would not work for the life of me. :P

[JayWood]

@TekkitCommando if that happens again it'd be great if you can at least gist up the file and link it in the task, I'd be glad to copy it in. It's better than letting tasks go stagnant for months I'd say.

[ethsmith]

No it was like 3 days ago. My git was working a couple weeks ago.

[ethsmith]

It's working again now.