Bug Report with CSS includes (was Re: How to format a column in list display?), posted by Andreas Luedeke on Mon Jun 14 17:25:02 2021
|
Okay, found some solution for my problem:
List Change Pikett = <div class="pikett">$Pikett</div>
CSS=pikett.css
And file themes/default/pikett.css contains: |
|
Re: Request: make $text available for "subst", posted by Andreas Luedeke on Mon Jun 14 18:06:06 2021
|
I should tell that I found a simpler way to achieve the same:
I suppress the "text" field and use a single line text input field instead.
The single line input in "free text" modes just contains "<br>" : I would have had to use those in the text field anyway. |
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. |
Re: How to access PSI Elog data from other web clients , posted by Andreas Luedeke on Thu Oct 21 00:42:42 2021
|
There is a python API to access ELOG via HTTP: https://github.com/paulscherrerinstitute/py_elog
Lin
Wang wrote:
We want to develop separate mobile web pages for the web applications |
|
Redirect in Execute new needs space after ">", posted by Andreas Luedeke on Thu Oct 21 11:00:46 2021
|
EDIT: forget the tip below. Instead just call script files: inline scripting in the ELOG config shows very strange behavior. Doing the same in external
scripts works reliable.
|
|
How about string constants in config files?, posted by Andreas Luedeke on Thu Oct 21 11:15:20 2021
|
My config files are often large and use some shell scripting. In these shell scripting part I interact with files and execute scripts in specific folder.
It would be nice to have the ability to define for example a file path once and reuse it in different parts of the config file. It would help to
make config files cleaner. For example: |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Tue Dec 7 11:56:37 2021
|
If you need HTTPS then you must specify the "-s" option.
You could have looked into the help of the elog command:
> elog -h |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Tue Dec 7 18:24:42 2021
|
But this is real progress! Now elog successfully connected, and all your data was transmitted, but elogd refused your content.
A possible explanation is that one required attribute of this logbook was not provided in your elog command, or that one value of an
attribute does not match any allowed value for that attribute. |