kiwidude,
I apologize if you feel I was dinging you for this; It certainly wasn't/isn't my intent.
Rather I was, and still am recommending that a list be kept/updated (as is already the case for some) which has the previous version (or if need be, on Calibre's Sourceforge project page, where previous versions of Calibre can be found, create a plugins sub-directory where one can find an older version of a plugin)
However, your point is taken as to doing a back-up of the Calibre library and config directory before updating. Having done several updates this year alone, and not having had a problem in the past, I didn't think it would be necessary - but in future will be done.
Quote:
Originally Posted by kiwidude
Each plugin author is free to do what they want (except add more than one zip file to their first post as it breaks Plugin Updater!) but speaking for myself it just isn't going to happen.
Going backwards in calibre versions is *rarely* a good idea, particularly given the frequency of database changes, it certainly isn't supported. Instead the recommendation as always is to have backups. The same should apply to your calibre configuration directory where your plugins are installed - had you taken a backup of that directory yourself you would have less of an issue.
For the same reasons going backwards in calibre is a bad idea, going backwards in calibre plugins can be a bad idea too (unless you restore from backup your matching pair of calibre database and calibre plugins folder). Speaking for myself my plugins frequently have migration code inside them to move configuration forward be it file or database-based - installing an older version of the plugin will break that and most likely cause you to lose your settings.
It's just a bad idea imo. I can sympathise, but (a) the need to revert after a new calibre release is infrequent, and more importantly (b) it would require a whole lot of time and effort that I for one am not going to put in. I spend enough of my life developing and supporting the plugins as is without adding more overhead.
|