Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Fri Apr 26 17:22:46 2019
|
Ok, I found the issue. The "Restrict edit time" is only checked when one clicks on "Edit" in the browser. The elog command line tool
does not really an edit, but just submits an entry with an (old) ID. I added a check also for that case so now it should work. The commit is in git.
Stefan |
|
Re: Last default = <n>, posted by Stefan Ritt on Mon Apr 29 13:12:56 2019
|
Indeed the description of the "Last default = <n>" option is not clear. I just updated that. If you have a quick filter "Date",
then you have different options there like "Last day", "Last 3 days", "Last week", "Last month", "Last 3 months",
"Last 6 months", "Last year". Each of these options has an underlying number of days, which are 1, 3, 7, 31, 92, 182, 364. In the "Last |
|
Re: Last default = <n>, posted by Alan Grant on Mon Apr 29 17:48:13 2019
|
I just changed to Last default = 31 and even restarted elogd.exe but it still finds a given string older than 31 days. Also the default Select Period
box value next to the QF's remains at All Entries. My understanding is it shoud behave like Find, where Show Last Default = 31 should default
the display to Month, and also only search within the last month of entries. |
|
Re: exclude access to a number of users in one logbook, posted by Stefan Ritt on Tue Apr 30 09:34:52 2019
|
You have a look here: elog:68936
Nikolas
Patronis wrote:
How can I exclude the access of a number of users in one (out of |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 30 12:47:46 2019
|
I was finally able to catch the crash.
I paste below the info provided by lldb..
It seems that it has something to do with the 'first' logbook that contains 115 entries and is displayed in 6 pages. |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 30 14:07:52 2019
|
Actually it is a little bit more difficult than that.
I have restarted elogd and got a crash but this time it seems related to a different logbook...
Below the stack trace.. |
|
Re: How to sort on any field?, posted by Andreas Luedeke on Tue Apr 30 14:20:34 2019
|
Sorting does work fine, if you do it correctly. From your post I cannot even guess what you've tried - let alone tell you what you did wrong.
Please post your config, some example entries and a description of what you've tried, what you expected to happen and what actually happened.
Screenshots are often very useful as well. |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Wed May 1 10:59:59 2019
|
Ok, that helped. It looks to me that the strlcpy() function from MacOSC does not like overlapping stings as parameters. Funny that this does not happen
on my Mac (Mojave 10.14.4). I fixed the two cases you reported (lines 18712 and 19021) and committed the changes to bitbucket, from where you can pull
and test it again (see https://elog.psi.ch/elog/download.html for instructions). If it happens |