ELOG Version 3.1.0 announcement, posted by Stefan Ritt on Thu Apr 2 15:44:33 2015
|
This is an announcement for the ELOG version 3.1.0 being released just now. Among several bug fixes and an improved Drag & Drop interface for attachments,
it contains a long awaited "autosave" feature.
Let's assume that you write an ELOG entry, and keep the window open for a longer time (like to write some shift notes over several hours). |
Re: ELOG Version 3.1.0 announcement, posted by Banata Wachid Ridwan on Wed Apr 15 04:02:41 2015
|
congrats, any detail changelog? I assume in software packages?
is it save just install and overwrite the old version?
Stefan |
|
Re: ELOG Version 3.1.0 announcement, posted by Stefan Ritt on Wed Apr 15 09:01:04 2015
|
The changelog is here: http://midas.psi.ch/elog/download/ChangeLog
It is save to install the new version over the old one.
|
|
Different way CSS files are handled, posted by Stefan Ritt on Fri Jun 5 14:24:34 2015
|
Hi,
I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css,
which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, |
|
Re: Different way CSS files are handled, posted by Andreas Luedeke on Fri Jun 5 19:01:05 2015
|
Hi Stefan,
there is a little problem with the Makefile (on SL5 and SL6): the following line:
@$(INSTALL) -m 0644 themes/default/* $(ELOGDIR)/themes/default/ |
|
Re: Different way CSS files are handled, posted by Stefan Ritt on Tue Jun 9 09:39:14 2015
|
Ok, fixed again.
Andreas
Luedeke wrote:
Hi Stefan, |
Is ELOG sending out cookies?, posted by David Pilgram on Wed Jun 10 14:25:16 2015
|
On my linux box, every time I select a thread, or start a new entry etc, I see that one or many cookies are sent.
On a terminal, I get the message
Received unknown cookie "CalciumDisplayParams" |
|
Re: Is ELOG sending out cookies?, posted by Stefan Ritt on Wed Jun 10 15:35:14 2015
|
Cookies are sent from your browser. ELOG has no influence on what the browser sends where. Probably you run your calender at the same machine where ELOG
is running, so all the cookies your calender app stores in your browser are sent to ELOG as well. ELOG just complains about something it does not know,
but otherwise this message can be simply ignored. Of course you can delete your cookies in your browser, but after the next call to your calendar app they |