Backup before update!

[MtK]

yes, the title is pretty general, but also obvious.
the problem is that when updating a plugin you are asked if you are sure, but you are not warned that you will lose all your plugin data/info/setting/etc.

so... backup before you update any plugin.
oh, and also devs, could you make a nicer/appropriate warning?

 

[dlavigne]

oh, and also devs, could you make a nicer/appropriate warning?

That one will require a feature request at bugs.freenas.org. Please post the issue number here.

 

[cyberjock]

Updates shouldn't be wiping out data. Since you gave no indicator of the actual plugin I can't tell you if this is expected, a bug, etc.

 

[nvader]

I have updated plex several times and it doesn't wipe out the config, but i just updated sabnzbd and sickbeard and both configs were wiped out and i have to start over. I didn't back them up because i thought that since they fixed plex so you can just press "update" and you'd be good. but i assumed wrong. hope in the future they will correct this.

 

[MtK]

Updates shouldn't be wiping out data. Since you gave no indicator of the actual plugin I can't tell you if this is expected, a bug, etc.

both CP & SB where updated and data was wiped (settings included)

 

[raidflex]

Not sure why people are not just using the internal update for SB or CP. It works perfectly fine and in fact CP updates itself automatically if you choose.

 

[MtK]

I just updated CP plugin, and the same thing happen.
now I need to set everything (plugin settings & even jail storage) again.

 

[Joshua Parker Ruehlig]

Your settings probably weren't deleted. At one point with SAB&CP I used /usr/pbi/PORTNAME-amd64/etc/PORTNAME as the data-directory but then moved to using /var/db/PORTNAME because it speeds up updating.

If you want your old settings, you can just move the folder.

 

[MtK]

Well, it's and update.
If things are changing, a warning would be nice...

 

[Joshua Parker Ruehlig]

Well, it's and update.
If things are changing, a warning would be nice...

I put it in the obnoxiously long support thread for these plugins a few months ago when it happened.