Deny option and Guest commands, posted by Janusz Szuba on Mon Jul 19 18:41:29 2021
|
Hi,
I have a logbook with guest access and guest can also enter a new entry (in config: Guest List Menu commands = New, Find, Select, Login).
For other reason in a global section, I put |
|
Drop attachments here..., posted by Xuan Wu on Wed Jun 23 03:48:22 2021
|
| The function of "Drop attachments here..." is only for root user? I'd like it could be used by all users. |
Re: Drop attachments here..., posted by Sebastian Schenk on Mon Jun 28 14:53:44 2021
|
I can't confirm this behavoiur. In our instance, every user can use the attachment function of the elog.
Either through "Drag&Drop" or "Browse&Upload" in the entry editor.
What do you mean by "root" user? |
|
Re: Drop attachments here..., posted by Xuan Wu on Mon Jun 28 18:41:31 2021
|
I just used my own account to test the "Drag&Drop" function in this forum , and it failed. In our case, we need to upload
ten more images into logbook at once, it's more effective to use "Drag&Drop" than "Browse&Upload" feature for "Browse&Upload"
only can choose one attachment at once, but "Drag&Drop" can choose several attachments at once. The admin user can use this |
|
Re: Drop attachments here..., posted by Sebastian Schenk on Tue Jun 29 15:21:06 2021
|
In my testings I didn't found this behaviour, but my collegues also reported this issue.
So I searched for the difference between my test setup and the production logbooks.
I believe the "restrict edit = 1" config option may be responsible for this behaviour. |
|
Re: Drop attachments here..., posted by Sebastian Schenk on Tue Jun 29 20:13:36 2021
|
I could figure out the bug. A fix can be found in this commit.
https://bitbucket.org/merrx/elog/commits/c3e3c4af9666006558aaf26d8f4841800e69f9af
Sebastian |
|
Re: Drop attachments here..., posted by Stefan Ritt on Tue Jun 29 20:20:38 2021
|
| Looks good, I merged the pull request. |
|
Re: Drop attachments here..., posted by Sebastian Schenk on Wed Jun 30 13:50:08 2021
|
Thanks for the merge.
I found a more general solution, as there could be the posibility to have the author as "select" or "radio box" input in the
form, where the fix breaks. |
|
Re: Drop attachments here..., posted by Xuan Wu on Wed Jun 30 04:38:21 2021
|
Excellent, Thanks!
Sebastian
Schenk wrote:
I could figure out the bug. A fix can be found in this commit. |
|
Timezome problem, posted by Maxim on Wed Jun 23 15:28:00 2021
|
Good afternoon!
The elog does not see the time zone. It displays UTC + 0. When I transfer old entries to a new compiled log, they are displayed 3 hours earlier
(my time zone is UTC + 3). When creating a new record, it creates them in the UTC + 0. |
|
Problem with a self-compiled code., posted by Maxim on Mon May 31 14:51:39 2021
|
Dear, sir! There is a problem with a configuration file.
The code was compiled by Cygwin (gcc-core, gcc-g++, make, gdb, libssl-dev). After a compilation a reference to our own css-file was written
in configuration file and css-file was included in a folder “themes/default” of the project. |
|
Re: Problem with a self-compiled code., posted by Sebastian Schenk on Thu Jun 3 16:02:02 2021
|
Hello Maxim,
I just stumbled on a similar issue. Also with a self-compiled elogd on Ubuntu.
We also use a custom css and by clicking on the "New" or "Reply" or "Duplicate" the elog generates the entry editor. |
|
Re: Problem with a self-compiled code., posted by Maxim on Wed Jun 23 14:08:15 2021
|
Good afternoon Sebastian!
Thank you very much for your help.
Sebastian |
|
when using webserver authentication, how can I restrict the users that can edit any given elog?, posted by Christian Ospelkaus on Sat Jun 19 18:38:21 2021
|
Dear elog users & developers,
the subject line says it all: when using webserver authentication, how is it possible to restict access of users to any given elog? Only using
the apche rules? Admin user and Login user do not seem to be doing anything for me. I am using elog as packaged by debian for buster, using an apache ssl |
|
Re: when using webserver authentication, how can I restrict the users that can edit any given elog?, posted by Christian Ospelkaus on Sun Jun 20 14:38:06 2021
|
Dear all,
I figured it out. Current global config is (using kerberos instead)
[global] |
How to format a column in list display?, posted by Andreas Luedeke on Fri Apr 23 20:08:10 2021 
|
There is the nice conditional formatting feature for List display:
Cell Style <attribute> <value>
= <style>
I would like to use it without conditions: some attributes should always be formatted in a specific way.
Specifically I want a generated attribute (combined from other attributes) to be display in monospace font.
The |
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: |
|
Bug Report with CSS includes (was Re: How to format a column in list display?), posted by Sebastian Schenk on Mon Jun 14 18:51:59 2021
|
Hi Andreas,
the bug you have found was already reported in an earlier issue, together with the same solution you have found.
https://elog.psi.ch/elogs/Forum/69368 |
|
Request: make $text available for "subst", posted by Andreas Luedeke on Mon Mar 22 14:56:12 2021
|
Hi Stefan,
I've just tried to read the $text with subst into another field and failed.
It looks like $text is only available for the execution of shell scripts in the "execute new|edit|delete = <script>" command. |
|
Re: Request: make $text available for "subst", posted by Stefan Ritt on Mon Mar 22 15:10:12 2021
|
$text is the full body text and can go over many lines. Since attributes are restricted to single lines, it's not possible to substitute them with
the body text.
Stefan |
|
Re: Request: make $text available for "subst", posted by Andreas Luedeke on Mon Mar 22 19:59:13 2021
|
While the input widget of text attributes is a single line, they can easily be multi-line in the display - when you use HTML at least.
And of course the user can parse the text field and generate a single line, if he wants to.
If you leave it to me, I'll create wonderful applications to that feature :-) |
|
Re: Request: make $text available for "subst", posted by Stefan Ritt on Wed Mar 24 10:06:26 2021
|
Sure, attributes can be shown multi-line, but they cannot be stored in the elog internal database. The database is a very old design and only allows
for single line attributes. Just look at a YYMMDDa.log file and you will see that. I would have to change the database format to somethign more advanced
like XML, but that would take me a couple of weeks or months. |
|
Re: Request: make $text available for "subst", posted by Andreas Luedeke on Wed Mar 24 22:09:56 2021
|
Hi Stefan,
no problem: if I just strip all newlines from the $text field (in HTML you use <br> anyway, the newline has no function apart from whitespace),
and my multiline attribute is fine to go. |
|
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. |
|
Re: Request: make $text available for "subst", posted by Sebastian Schenk on Tue Mar 23 13:42:27 2021
|
I am not Stefan, but maybe I can add to this issue.
Personally I think it is not a good way to dump all the information into the text field and try to let the server parse it.
This could be archived more simply by using e.g. the python elog scripts or using the elog command tool to directly submit well structured elog |
Additional forbidden attributes, posted by Sebastian Schenk on Mon Jun 14 16:15:10 2021
|
Hello Stefan,
I stubbled on a issue with our elog.
We introduced an attribute "mode" to one of the elogs and it breaks the "Find" function as this attribute is already used for |