Does there is a way to no the $message_id when creating a new submission, posted by Lagarde on Thu May 9 13:34:55 2019
|
Hello,
I would like to know if it's possible to know the message_id of when creating a new entry in elog ?
I would like to do something like this Preset text = $message_id |
Re: Does there is a way to no the $message_id when creating a new submission, posted by Stefan Ritt on Thu May 9 16:42:13 2019
|
No, the message ID gets assigned only when you submit the entry.
Stefan
Lagarde |
Last default = <n>, posted by Alan Grant on Mon Apr 29 02:41:15 2019
|
According to the doc on the setting "Last default = <n>" it is intended to restrict Quick Filter searches to the last (n) days of entries,
however when I add "Last default = 28" to config it still returns entries far older then 28 days when using the filter search. Am I misunderstanding,
or implementing it wrong? We must restrict searches through QF to reduce load. |
|
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: Last default = <n>, posted by Stefan Ritt on Wed May 1 11:06:04 2019
|
It works for me. Have you tried other values (1, 3, 7, ..)? The key is that the quick filter changes to "Last month". If it does not, there
must be some trivial error, like type in elogd.cfg, you modify the wrong logbook, have a very old version of elog etc.
Stefan |
|
Re: Last default = <n>, posted by Stefan Ritt on Wed May 1 11:08:10 2019
|
You say "Show Last Default = 31". This options applies only to the "Find" page, the option "Last Default = 31" works for
the quick filter. Probably you have to change "Show Last Default" to "Last Default".
Stefan |
Re: Last default = <n>, posted by Alan Grant on Wed May 1 15:28:41 2019 
|
I was just referring to "Show last default" (under Find) as a parallel example of how I assume "Last default" should
function on the List page.
I also tried values 3 and 7 but "All entries" still displays in the "List period" box. A restart of elogd makes no difference. |
|
Re: Last default = <n>, posted by Stefan Ritt on Fri May 3 15:50:39 2019
|
I just tried your elogd.cfg, and it works fine for me. So no idea what is wrong in your case.
Stefan |
|
Re: Last default = <n>, posted by Alan Grant on Fri May 3 16:02:33 2019
|
Ok thanks for taking the time to try it out. I definitely still show "All entries" in any case, so I will continue to try to resolve on
my end and if I find the cause or solution I will share back on the forum.
First though, I noticed you ran 3.1.4 whereas I'm still on 3.1.2. I'm also on Windows Server 2016 and IE 11. Do you think any |
|
Re: Last default = <n>, posted by Stefan Ritt on Fri May 3 16:22:23 2019
|
Yes I always run the current version from bitbucket. I haven't touched that code for "last default" since a long time, so I don't expect
the verison to make a difference. Unfortuantely I have not Windows Server or IE for testing.
Alan |
|
Re: Last default = <n>, posted by Alan Grant on Fri May 3 16:29:00 2019
|
Thanks again.
I noticed in the Change Log for 3.1.4 that there's a reference to something done with "Last default" in Sept 2018 so I think
I will try to set up a Linux instance and try out 3.1.4. Regards. |
|
Re: Last default = <n>, posted by Stefan Ritt on Fri May 3 16:48:47 2019
|
Indeed you're right (my memory is fading, argh). Please try 3.1.4.
Stefan
Alan |
elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Tue Apr 23 14:06:36 2019
|
Dear all.
I am running elog
elogd 3.1.4 , revision ead6bbc6 |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Tue Apr 23 14:26:51 2019
|
This kind of behavior we typically see if some elog entry is corrupt. After a few hours you might access this corrupt entry by accident, and then the
server stops. If you see however this behavior on a fresh logbook with no corrupt entries, then the problem must lie somewhere else.
Do you see the same problem running under linux? |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Thu Apr 25 11:16:06 2019
|
Thanks for the prompt feedback.
a) I confirm that the problems shows up also when running interactively the elog through elogd -p 8080
b) I am trying to catch the exit using lldb on the mac machine. I will be able to give you some feedback on that I hope in the next week (not |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Thu Apr 25 11:27:21 2019
|
What you recommend is enough. Just make sure to compile elogd with the flags mentioned before, and when you get the segment violation, do a stack trace
inside the debugger to learn where the fault happend. Maybe also print the contents of some variables at the current location.
Stefan |
|
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: 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 |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Thu May 2 09:47:41 2019
|
Thanks a lot for providing a quick fix!
The elog is now happily running since two days without problems :)
I will get back to you in case anything else shows up. |
|
How to sort on any field?, posted by John on Tue Apr 30 05:52:44 2019
|
Hi, I was wondering if this is possible. I've tried to sort on anything other than the first few fields and although the screen refreshes like it
is 'doing something', it does NOT sort. Sometimes it will take me to the last page of my data, but still no sorting. I use Debian Linux verson
of Elog. There have been no other issues. I need to figure out how to do this without parsing it to another program first. Thanks again for this wonderful |
|
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: How to sort on any field?, posted by John on Tue Apr 30 19:07:17 2019
|
Hi Andrea and thank you soo much for your kind and prompt reply! I believe the issue will be solved as I have the information I need to proceed.
I was just wanting to verify that sorting indeed is alloud on ALL fields. I cannot send the exact config as it is a work project, but I can replicate
with fake fields and data if necessary in the future. I believe my errors are because I am either using field names which are 'special' to the |
|
exclude access to a number of users in one logbook, posted by Nikolas Patronis on Wed Apr 24 09:15:26 2019
|
| How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL? |
|
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 |
|
elog program does not respect "Allow edit" list, posted by Heinz Junkes on Mon Mar 11 11:18:02 2019
|
| submissions via the elog - program can overwrite entries even if the user has no edit rights |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 09:43:02 2019
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz |
|
Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Wed Apr 24 10:15:23 2019
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list. |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 10:21:58 2019
|
Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have
forbidden further editing.
Heinz |
|
Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Wed Apr 24 10:29:00 2019
|
There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.
Stefan
Heinz |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 11:03:26 2019
|
Sorry,
I meant "read only" by using "Restrict edit time" settings. e.g.
Restrict edit time = 24 |
|
Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Wed Apr 24 11:30:37 2019
|
So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post
a minimel elogd.cfg file with which I can reproduce the problem?
Stefan |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 11:56:24 2019
|
I ask my users where they had the problems and then create a demo for testing.
Thanks Heinz
Stefan |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Fri Apr 26 11:24:21 2019
|
Stefan, will send the info off this forum.
Heinz
Heinz |
|
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 |
|
Can't subscribe email to logbooks in different top groups, posted by Ben Loer on Thu Apr 11 20:31:55 2019
|
We're running elogd behind an apache proxy server, with Authentication = Webserver. We have top groups configured, but a single shared password file.
If a user is looking at a particular logbook and goes to the Config link, they are presented with a list of checkboxes for email subscription
to logbooks in that top group. Clicking "Save" will remove all email subscriptions from all other top groups. |
|
Re: Can't subscribe email to logbooks in different top groups, posted by Stefan Ritt on Fri Apr 12 15:43:42 2019
|
Top groups should use separate password files, otherwise things can mess up.
Stefan
Ben |
|
How to edit Elog landing pages., posted by John on Thu Mar 14 06:38:12 2019
|
Hi and thanx for such a wonderful program! I was wondering how I might edit, change or add to the landing pages. In other words the first pages that
show up (or any for that matter) when you login to a book. I can view the code ok in my browser using that function, but when I search for the actual page
and it's locale, I cannot find it. Is it created on the fly by the server? If so, how can I change them.. as I want to add for instance javascripts |
|
Re: How to edit Elog landing pages., posted by John on Sun Mar 17 00:40:42 2019
|
Well I answered part of my own question already.. I can have a start page different from what is default, and I can edit the orginal one by simply copying
it and modifiying it to my hearts desire. I still have isues after making menu selections from that page tho, when the program (server) takes
me to a site called for example: ../forum/index.html?cmd=Config. I cannot find out how to prevent or modify this behaviour. I am supposing tho, that |
|
Re: How to edit Elog landing pages., posted by Stefan Ritt on Thu Apr 4 12:53:09 2019
|
Per default, all pages are created dynamically by elogd directly from its C code. So nothing to change easily except hacking the code. There is one exception
which is the start page you found already. To change any other page, you have to modify the C code. There is one more (dirty) trick: You can sneak in JavaScript
code on every page via the "bottom text" option. This code can then modify the DOM tree and changes pages, but you need to program this in JavaScript. |
Re: How to edit Elog landing pages., posted by John on Thu Apr 4 20:30:29 2019
|
Wow Stefan thanks for your kind reply. This gives me a reason to finally pickup JavaScript, which I am finding both easy and fun, esepcially with
all the modules/coding out there already, which makes things easier to do while learning it! I will let you know as I progress on my 'top secret'
hack of your masterpiece ;) |