No. The date/time tag is there to actually document the time when the log was made. If you are late, you are late.

As an administrator of the logbook you could add an additional attribute, e.g. "when" of type datetime.

Each entry would then have the unchangeable entry time and an addtional time, e.g. of the event you are describing in the entry.

For more details look here: elog:67712

Sorry for that. The idea is that the -4 is the minor number between releases
(mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
-4 version several times when testing a new RPM building scheme, but I promise
to take more care in the future (:-)))

Having the CVS revision in the executable is however a good idea and I will
put it in.

> Stefan, would it be ok to add the "minor" revision level to the VERSION
> constant?  I've been doing this after I download source just so I can keep
> things straight, you keep cranking out versions ;->
> 
> EX: 
> #define VERSION "2.5.4-4"
> BECOMES
> #define VERSION "2.5.4-4-1.483" or something like that?
> 
> Just a thought.
> 
> Thanks

No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!

> Sorry for that. The idea is that the -4 is the minor number between releases
> (mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
> -4 version several times when testing a new RPM building scheme, but I promise
> to take more care in the future (:-)))
> 
> Having the CVS revision in the executable is however a good idea and I will
> put it in.
> 
> > Stefan, would it be ok to add the "minor" revision level to the VERSION
> > constant?  I've been doing this after I download source just so I can keep
> > things straight, you keep cranking out versions ;->
> > 
> > EX: 
> > #define VERSION "2.5.4-4"
> > BECOMES
> > #define VERSION "2.5.4-4-1.483" or something like that?
> > 
> > Just a thought.
> > 
> > Thanks

This comes from the openSSL library which elog includes. I tried myelf and found that a chained certificate is not correctly interpreted by the openSSL library. Most people anyhow don't use SSL inside elog, but run an Apache server in front of elog. This is anyhow better since Apache has an industry-strength security with regular updates. Much better than relying on OpenSSL.

Stefan

The first thing you can do with "Guest menu commands", where you enable only those commands which can't change or delete entries. The second thing you can only do if you put your entries into two separate logbooks, a public and a private one. 

The mxml package has been converted into a submodule in the git repository. At http://midas.psi.ch/elog/download.html you see that you need a "--recursive" flag to clone it. If you have already checked out the sources, you need a

git submodule update --init --recursive

/Stefan

I fixed this in revision #2204. The attachment names now stay the same. There is one tiny risk of screwing up, namely if you have the same attachment name in two different logbooks (accidentally also submitted at the same second and therefore the same time stamp). If you then copy these two entries to a third logbook, one attachment will overwrite the other one, but that risk is indeed really small. I actually had to re-write the link to the attachment inside the text body (even differently for ELCode and HTML encoding). So I'm not 100% sure I covered all cases, so just give it a try.