Quote:
Originally Posted by cyana
Thanks for your reply!
I'm running into another problem now - not sure but it seems to have to do with new setting options of 3.2 233 - it appears that no download links are generated in the books pages, also new ebooks are not uploaded anymore. I'm not aware of any setting changes I made, I simply installed 3.2 over 3.1.
|
You may have come across a bug where you cannot successfully do more than one generate run without reloading calibre2opds. The second (and subsequent) attempts to generate have the symptoms you describe. It is due to a performance optimisation that can incorrectly cache information between generate runs. You have to exit/restart calibre2opds between the generate runs to avoid this. A note about this has been added to the download links for calibre2opds.
Quote:
|
I recall that in 3.1 you must not set the option 'Do not generate OPDS downloads' even when 'Do not generate HTML downloads' is unchecked it will lead to this result. However, in 3.2 it seems that when you choose not to generate an OPDS catalog, the 'Do not generate OPDS downloads' - option is checked automatically and unchangeable resulting in missing html-download links (?)
|
I'll check this out. It sounds as if there is something wrong in the GUI code that tries to track the allowed combinations. I need to look at the internal logic. It may be that there should not be separate entries for OPDS and HTML downloads - just a single one saying whether download links are wanted. Because of the way HTML is generated from the XML that makes up an OPDS catalog (which still happens internally even when you do not want am OPDS catalog at the end) it may not be possible to successfully specify separate download settings.
EDIT: I have checked the code and the structure now
DOES allow for HTML downloads to be enabled or disabled when OPDS catalogs are disabled. The option that is not allowed is to have an OPDS catalog with downloads disabled
AND an HTML catalog with them enabled. I will update the GUI code so that this is the restriction that is enforced.
Keep the bug reports flowing! The number of people who are actively involved in calibre2opds during development cycles has dropped which means that it seems more of these type of errors get missed during testing. Despite that the program should still be improving I hope
.
EDIT: I have raised issues on the
Calibre2opds issue register for the points you have raised. Perhaps you might check these to see if I have missed anything or got any of the details wrong?
I should shortly be able to make a build available that although it will be labelled as a 3.3 beta it will primarily be the 3.2 release with reported bugs fixed as although 3.3 development has started the new facilities are not yet ready.