Quote:
Originally Posted by itimpi
Calibre2opds works purely off the Calibre data base, so steps 1-4 are all irrelevant as far as getting custom fields listed in a Calibre2opds catalog is concerned
I must admit when I last tested it I used the field names without the leading # - I need to check if including the # is still working. Have you checked the calibre2opds log file to see if any warning/error messages about the custom fields are there? What are the types if the custom fields?
I would recommend that you try the latest 3.5 release and see if the problem still persists as it would be much easier for me to troubleshoot that release. If you get nowhere and are prepared to let me have a copy of your calibre metadata.db file plus the profile file you are trying to use (so I have your parameter settings) then I can try and reproduce the issue. The best way to supply such information is by raising an issue at the calibre2opds bug tracker and attach the files there (they can be marked private if necessary). |
Thank you! Re. the custom field: I've tried both with and without leading # but it still didn't work.
As you recommended, I'll try version 3.5 to see if the problem still persists for me.
Thanks again.