Restrict edit time = 0 behavior intended?, posted by Chris Körner on Mon Nov 15 11:35:55 2021
|
Hi,
I have set the options "Restrict edit time = 24" and "Admin restrict edit time = 0" in [global]. This way can only edit entries
for 24 hours while the admin can forever. I now want a single logbook where all users have unlimited time to edit entries. However, setting "Restrict |
Re: Restrict edit time = 0 behavior intended?, posted by Chris Körner on Mon Nov 15 11:48:25 2021
|
Actually this is related to post 68993 from Sebastian Schenk in Jul 2019. Are there any new workarounds
I may have missed?
Chris |
|
Re: Restrict edit time = 0 behavior intended?, posted by Sebastian Schenk on Mon Nov 15 14:02:42 2021
|
Hi Chris,
my old entry was related to the admin options of edit time.
The option "Admin restrict edit time" was implemented later, see ab8b98c |
|
Re: Restrict edit time = 0 behavior intended?, posted by Chris Körner on Tue Nov 16 15:14:42 2021
|
Hi Sebastian,
thanks for the reply. It is just a bit confusing that these similar settings behave so differently. For me it is no big deal to set the
time for every logbook independently instead of [global], but it leaves more room for configuration errors. |
$attribute replacement fails occasionally, posted by Chris Körner on Sat Nov 27 21:48:41 2021
|
Hi,
In our setup we have multiple logbooks. I want a convenient way to search all logbooks for an attribute (in our case with the name Sample-ID)
by just clicking it in the list display of any logbook.Therefore, in the [global] section I put "List Change Sample-ID = <a href="https://ourelog.com/$logbook/?all=1&Sample-ID=$Sample-ID"</a>. |
Re: $attribute replacement fails occasionally, posted by Chris Körner on Sat Dec 4 13:03:32 2021 
|
This problen drives me crazy. Under some circumstances the List Change <attribute> function does not replace $attribute. It happens at random circumstances
when I use the Find function to search all logbooks. In the resulting list, it fails reproducibly for certain entries of certain logbooks. But I cannot
find what is special about those lokbooks or entries. In different Find requests it works perfectly fine. |
|
make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Tue Feb 8 00:52:47 2022
|
For the record, compiler messages from elog tip of branch elog/master.
Most of the stuff is the usual same-old that we mostly fixed in midas:
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Stefan Ritt on Tue Feb 8 09:14:25 2022
|
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:36:10: note: ‘__builtin___sprintf_chk’ output 2 or more bytes (assuming 4097) into a
> destination of size 4096
|