Re: today date in template, posted by Konstantin Olchanski on Tue Apr 9 04:50:28 2024
|
> This is a nice idea, but currently no text substations in templates are implemented. It only works in attributes right now.
but can it be done by javascript injection? load a custom .js or .html file, in this file run javascript code to root down the DOM tree until you
|
Re: today date in template, posted by David Pilgram on Tue Apr 9 13:40:44 2024
|
This was given to me by Andreas L,
In my elog.cfg file, I have the following:
|
Re: today date in template, posted by David Pilgram on Tue Apr 9 13:49:51 2024
|
This was given to me by Andreas Luedeke of this parish.
In my elog.cfg file, I have the following:
|
http status 200 returned for "file not found", posted by Konstantin Olchanski on Fri Mar 18 00:36:37 2022
|
"file not found" should return http code 404. elogd returns code 200 together
with a page containing text "404 not found". This pollutes the browser cache
with wrong content (in this case, we are trying to load a css file, and the browser
|
Adding entries without being logged in stopped working with attachments, posted by Andreas Luedeke on Sat Aug 28 21:32:09 2021
|
Hi Stefan (et al),
we have several logbooks that allow to add new entries without logging in first.
That still works, as long as these entries don't have any attachments. |
edit elog config via elog web interface, posted by Tim Schelfhout on Mon Sep 4 11:22:05 2017
|
Hello,
Is it possible to edit the entire elog config file via the elog frontend? I see the config button
on some screens but it only allows me to change user and password?? |
javascript?, posted by Tim Schelfhout on Mon Sep 4 11:56:47 2017
|
Is there anyone out there who can help me get started using javascript in elog ? Is there an example somewhere ... i suppose you put the code in
the
scripts folder? |
Re: edit elog config via elog web interface, posted by Andreas Luedeke on Mon Sep 4 13:08:35 2017
|
On the right side of "Change password" you should find "Change config file".
But you'll only see this, if the user has admin priviledges defined in the config file: "Admin user = <user>"
|