> 1. shellonsubmit command : give the possibility to execute external 
> program from elog by sending specific parameter (user/logbook/message ID)
> 
> 2. elog log file in xml format : give a better view on what happens with 
> users see attachments easy to push the files to excel or sql database.

I'm happy to include these functions in the source code, please send them 
to me.

> 3. synchronisation to mySql or SQL server through perl routine and the 
> shellonsubmit command
> this will push any new/edit/delete command in sql server so we keep a 
> full historic off all transaction in ELOG

Can you please put this perl routine into the "Contributions" section

> 4. sms gateway : from elog entry we send sms message throught internet 
> gateway (perl routine)

Same as above.

> other projet : 
> we use a logbook from our external phone call
> 
> from our telephone connected to RS232 and/or TAPI interface we keep the 
> phone number and try to find the name from sql server : if found 
> we want to push an automatic entry in elog and fill specific field like 
> name/contact/last phone call....
> 
> I will ask to Stephan Ritt what's the best way to include our routine in 
> his standard source ?

As I said, put the perl programs into the "Contributions" logbook, send the 
C source code modifications to me.

> could we create a specific logbook for the wishlist
> in elog/contribution may be some parameters for the actual status of the 
> project ? 

Good idea, will do so.

Tomas send you by mail the source files and documentation in English



> > 1. shellonsubmit command : give the possibility to execute external 
> > program from elog by sending specific parameter (user/logbook/message ID)
> > 
> > 2. elog log file in xml format : give a better view on what happens with 
> > users see attachments easy to push the files to excel or sql database.
> 
> I'm happy to include these functions in the source code, please send them 
> to me.
> 
> > 3. synchronisation to mySql or SQL server through perl routine and the 
> > shellonsubmit command
> > this will push any new/edit/delete command in sql server so we keep a 
> > full historic off all transaction in ELOG
> 
> Can you please put this perl routine into the "Contributions" section
> 
> > 4. sms gateway : from elog entry we send sms message throught internet 
> > gateway (perl routine)
> 
> Same as above.
> 
> > other projet : 
> > we use a logbook from our external phone call
> > 
> > from our telephone connected to RS232 and/or TAPI interface we keep the 
> > phone number and try to find the name from sql server : if found 
> > we want to push an automatic entry in elog and fill specific field like 
> > name/contact/last phone call....
> > 
> > I will ask to Stephan Ritt what's the best way to include our routine in 
> > his standard source ?
> 
> As I said, put the perl programs into the "Contributions" logbook, send 
the 
> C source code modifications to me.
> 
> > could we create a specific logbook for the wishlist
> > in elog/contribution may be some parameters for the actual status of the 
> > project ? 
> 
> Good idea, will do so.

Besides the commen Andrea made I would like to add that you can convince elog to show all files if you simply restart it, then it will re-scan all files. But as Andreas said, if two elogd instances write to the same directory, you will get a mess with double IDs of entries.

Stefan

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

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.

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.

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.