Your comments

Dave,


Don't change the java location setting. Keep it as written in the other thread, valid for all synology (not the same than what is displayed on the GUI however, indeed)


Did you adapted the location of your ubooquity binary?

What says ubooquity logs? 


Cheers

Tom, by the way, the howto should be updated, it is even not valid anymore. Thanks

Perfect Elouan! Thanks!

I applied on my new Synology DS216Play and it worked.


Maybe to be highlighted for beginner profiles:

- PID_FILE: to be adapted to where you created the ubooquity.pid file (which you have to create yourself)

- PCKG_BIN: your proposal is based on former tuto in help section. If you don't (need to) ssh anymore in your synology, then there is no way to add the Ubooquity jar elsewhere than volume1 ;-) => adapt to where you stored the jar

- WORK_DIR: also to be adapted to where you want ubooquity to store all preferences/system/cache files. It is recommended to be another folder than the one storing your comics (to not mix comics & ubooquity system files)


Note: I was initially tricked by the JAVA_BIN, believing I should adapt to the address provided in the java packet settings. Not, you need to keep the one in Elouan script. 


Hi,


To me it sounds like you are not looking in the right direction.

Could you please explain your need behind your wish?


If you want customs metadata, then modify the xml according to your needs.

There is more change for non-standard metadata to be one day considered by Tom. Tom to adapt his code to cope with a unusual txt file to embed this seems very unprovable to me.


FYI, open any cbz you have previously created and look for the file ComicInfo.xml

Its format looks like this:


<?xml version="1.0"?>

  <Title>TITLE</Title>

  <Series>SERIE</Series>

  <Number>TOME</Number>

  <Summary>SUMMARY</Summary>

  <Year>YEAR</Year>

  <Month>MONTH</Month>

  <PageCount>PAGES</PageCount>

</ComicInfo>


which is just an extract of what you can add as metadata type.

I had to fix so many already, which I downloaded as-is... :-(

Yep,


Today, when upgrading from 1.x to 2.x, there is no migration taking care of the db & settings.

You need to restart everything from scratch, which may lead to your symptoms from my perspective.


Try starting again from a clean working directory (no old db or settings there e.g.)


If like me you find it not convenient, then give a hint to Tom by liking my proposal at the end of post http://ubooquity.userecho.com/topics/489-database-backup-rebuild/#comment-3026 ;-)