Understood, Thanks very much for your help.

Drafts are not shown in the list page, but you can browse directly to them, if you know their idea. They are also shown if you hit "new". Then a box comes up "You have unfished drafts, do you want to edit them?". This is the new draft feature introduced recently and a feature of elog.

But I guess you have a more general problem. You run two elogd severs, and you transfer information between the two servers via Dropbox. Elog is not made for that. Elog is a web server, so you don't have to transfer data via a could service (except maybe for backup). You can access your one and only elog instance from everywhere. Everything else will give you trouble.

Hi, I have noticed that if an entry is not submitted it is saved in a sub-folder (name is current ID number) eg http://localhost:8090/mike/23, while draft it doesn't appear in list page but you can browse directly to it.

When you update an entry on one server instance, if you then browse to the entry ID on the 2nd server instance it is draft. If you edit then submit the entry then appears in list page on 2nd server instance.

Thanks again.

Ah, I see another problem. The pre 3.1 version had all logbook files in one directory, and the 3.1 puts the files in one subdirectoy per year. On transition from 3.0 to 3.1, an automatic conversion is made, but only once. If you later add files into the root logbook directory, they will not be seen. So you have to move them manually into the right subdirectory.

Thanks very much for your comments. I will take a look at the mirror server functionality.

I have only been running one elogd at a time, restarting elogd (on Windows 10) doesn't seem to pick up the changes made on Windows 8.1 PC (stopped elogd after changes made and log file updated)

Mike

Updating CKeditor did work, thanks for the tip.

> > > > > Was just wondering about the status of the multi-line attributes in Elog, are 
> > > > > they implemented in elog yet? If not is that something you are planning to do 
> > > > > in the future?
> > > > 
> > > > In order to have multi-line attributes, the whole format of the logbooks has to be
> > > > changed. I plan to use XML for the logbook format in the future. We would not have
> > > > any more one file per day, but one big file per logbook. I have already some XML
> > > > functionality in elog, but this one requires a major rewrite of the whole code. On
> > > > the other hand, searching etc. will become much faster afterwards. I plan to start
> > > > this development soon, but it might take quite some time, so don't expect it
> > > > before summer or fall.
> > > > 
> > > > Best regards,
> > > > 
> > > >   Stefan
> > > 
> > > Thanks for your help, thats useful to know.
> > > 
> > > Paul
> > 
> > Hi Stefan,
> > 
> > any update on the multi-line request?
> 
> Nope. Too many other things to do during my "day job".
> 
> Stefan

Thank you, your eLog is already a very good instrument!