Quote:
Originally Posted by kaufman
I just noticed a small bug/inconsistency that I am astounded that I hadn't noticed already.
When you backup the settings it CC creates a filename called
CC_settings_backup_Year-Month-Date
But, it isn't actually month, its month-1. So my settings file from this morning is called
CC_settings_backup_2014-07-04
|
To emulate Kovid a bit, from the change log for V3.4.2:
[BUG FIX]Fix incorrect month in auto-generated backup file name
I found the problem myself about 30 minutes after publishing V3.4.1. In the Java calendar API, year, day-of-month and day-of-week are one-based but month-of-year is zero-based. Sigh...
Here is the V3.4.2 change log as of now. Unless something else comes in that delays the process, I intend to release it to the prerelease group on Wed.
- Remove the newly-added goto FAQ menu item. Instead, add a FAQ button to the "failed to connect" dialogs
- Change text in settings to warn users about CC doing a slow DB upgrade when grouped on lookup names or read info lookup names are changed.
- [BUG FIX]Do not allow connection to calibre during a DB upgrade. Prevents possible corruption of metadata.
- [BUG FIX]Do not reset the book list to the top if read info changes
- [BUG FIX]Make restore settings do a DB upgrade if necessary
- [BUG FIX]Fix problems with syncing read information across multiple libraries
- [BUG FIX]Fix "Send book to app"
- [BUG FIX]Fix incorrect month in auto-generated backup file name
- [BUG FIX]Show a better error message when device runs out of space while writing book files