CC V5.1.2 beta release channel

[chaley]

CC V5.1.2 has been released to the beta channel.

Change log:

• Support for new calibre customizable identifier links (calibre / Preferences / Look & Feel / Rules to convert calibre identifiers into links). CC's support requires calibre 2.56.
• Don't launch the reader app if the book file is gone. Instead show a popup message
• Better tests for cloud database integrity, to avoid crashes
• Add more logging to check for unusual events such as failed book file deletions
• Log when news is automatically deleted
• Updated language: Russian
• [BUG FIX]Ensure that the sort order is respected when returning to the book list from the check for missing books

[Purple Lady]

I just got an error on my Galaxy S6 trying to connect to Dropbox that would only go away by restoring the previous version using Titanium Backup. A message about using custom columns was displayed and as I was trying to read it an error popped up. It just said something like an error occurred but no details. I tried to connect again and got the same error. Even after I went into settings and forced close I got the error so I saved the log file for you.

After I restored from Titanium and updated again it worked fine. I'll send you the error log I saved.

[chaley]

Originally Posted by Purple Lady

I just got an error on my Galaxy S6 trying to connect to Dropbox that would only go away by restoring the previous version using Titanium Backup. A message about using custom columns was displayed and as I was trying to read it an error popped up. It just said something like an error occurred but no details. I tried to connect again and got the same error. Even after I went into settings and forced close I got the error so I saved the log file for you.

After I restored from Titanium and updated again it worked fine. I'll send you the error log I saved.

According to that debug log the calibre DB was either gone or totally corrupt. CC thought it was there, but it wasn't.

I have seen indications before that something like this can happen. I store the database in CC's private folder on the SD card if there is one, otherwise in main memory. I wonder if there is some situation during an upgrade where that folder is emptied. It seems that is what happened to you.

When I check if the DB is up-to-date I check stored version numbers. I don't check the actual DB file. Clearly I should, and I will add that. EDIT: I *do* check that the file exists. Perhaps I should check if its contents have changed.

[chaley]

@Purple Lady: FWIW a messed up file system on the SD card could account for this. I am thinking about your disappearing books ...

[Purple Lady]

Originally Posted by chaley

@Purple Lady: FWIW a messed up file system on the SD card could account for this. I am thinking about your disappearing books ...

Different devices. This was my phone with no SD card, and the other was my tablet with an SD card.

[Purple Lady]

Originally Posted by chaley

According to that debug log the calibre DB was either gone or totally corrupt. CC thought it was there, but it wasn't.

I have seen indications before that something like this can happen. I store the database in CC's private folder on the SD card if there is one, otherwise in main memory. I wonder if there is some situation during an upgrade where that folder is emptied. It seems that is what happened to you.

When I check if the DB is up-to-date I check stored version numbers. I don't check the actual DB file. Clearly I should, and I will add that. EDIT: I *do* check that the file exists. Perhaps I should check if its contents have changed.

If it was a situation when an upgrade is done it must be a very odd one since after I restored the previous Titanium backup the upgrade was fine. I restored from last Friday night, but I don't use it on my phone very often so there wouldn't have been much difference.

[chaley]

Change log (24/April/2016):

• Fix problem introduced in Beta 1 that causes cloud connections to fail when connecting to a new provider or after resetting the cloud connection.
• Better checks for a corrupted cloud database

[chaley]

Change log:

• Make languages a searchable field
• Update languages: Spanish
• Use updated Google tools to generate the release

I fully expect that this release will go to the general public in a few days.

[nqk]

Originally Posted by chaley

Change log:

• Make languages a searchable field

I fully expect that this release will go to the general public in a few days.

Please add "series" too. I'd intended to remind you earlier, but I thought you would review the list of searchable fields anyway.

[chaley]

Originally Posted by nqk

Please add "series" too. I'd intended to remind you earlier, but I thought you would review the list of searchable fields anyway.

Series is already there, as is series_index.

Edit: here are some screen captures

[nqk]

Ah, yes. But.... I intended to search for "Perry" as in Perry Mason

series:Perry returns 0
series:"Perry" returns 0
series:"Perry Mason" returns 0
series:"=Perry Mason" returns the right number.

So it means that I have to remember the exact string in series.

[chaley]

Originally Posted by nqk

Ah, yes. But.... I intended to search for "Perry" as in Perry Mason

series:Perry returns 0
series:"Perry" returns 0
series:"Perry Mason" returns 0
series:"=Perry Mason" returns the right number.

So it means that I have to remember the exact string in series.

It works fine for me. Here are two screen captures that show it.


Ahh ... there might be an issue with letter case with the "contains" search, which is the default. I will check that.

[chaley]

Originally Posted by nqk

Ah, yes. But.... I intended to search for "Perry" as in Perry Mason

series:Perry returns 0
series:"Perry" returns 0
series:"Perry Mason" returns 0
series:"=Perry Mason" returns the right number.

So it means that I have to remember the exact string in series.

Yes indeed there is a letter case problem. The equal and regexp searches ignore case, but the contains search does not. The value is forced to lowercase before the test, so if the test value ("Perry") in your case contains an uppercase letter (which it does) then it will not match.

I will fix it in some upcoming release. The work-around is to enter lowercase letters into the search box ("perry" instead of "Perry")