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.
I have added a screenshot. The yellow button is created by this command in [global] for all logbooks. It makes no difference to define it in all [logbook] sections. I would really appreciate help to debug this.
List Change Sample-ID = <a href="page?mode=summary&reverse=1&all=1&Sample-ID=$Sample-ID$&sort=Date" class="id_div">$Sample-ID</a>
| Chris Körner wrote: |
|
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>. This transforms the attribute in list display into a hyperlink to the search results page. So far this works fine. In the results page, of course the option also applies, meaning the attribute is replaced by the link as well. But here something odd happens and the replacement does not work. The intended behavior is to replace $logbook in the link with the name of the logbook. Sometimes, however, the replacement yields something like "logbook" (missing $ and thus not replacing anything) or even weirder something like "60logbook". I have no idea what causes this.
|
|
wrong server HTTP status code when login failed, posted by Chris Körner on Thu Oct 21 14:57:14 2021
|
Hi,
I am trying to access elog through a python client (https://github.com/paulscherrerinstitute/py_elog) and found a strage strange behavior which may be related server side problem. The python script generates get/post messages via the python requests library. This works fine so far and I can view and post messages. However, if a wrong user/password is provided, the server still returns HTTP status code "200 OK", although login failed. Instead, it should return something like "401 Unauthorized". This behavior later causes problems since the python client thinks login was successful. After experimenting around I think this could be caused by a server side misconfiguration. Any ideas?
I am not sure if this imformation is important: We use LDAP as user/password provider for elog. |
Where do I find information on setting up the text area as a template?, posted by Chris Jennings on Thu Aug 23 14:30:56 2012
|
I would like to set up the text are as a template. The documentation indicates this can be done however I am unable to find reference to how it is accomplished. |
|
Sort by date prior to 2002, posted by Chris Jennings on Tue Sep 16 17:59:27 2014
|
I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?
Thanks in advance,
Chris |
|
Re: Sort by date prior to 2002, posted by Chris Jennings on Tue Sep 16 18:05:41 2014
|
| Chris Jennings wrote: |
|
I have an attribute formatted as a date (but not labeled as date) and is sorted as second priority. The sort works fine until I enter a date older than Jan 1st 2002. When I do this it is sorted as the latest. Is this a bug or simply not designed to use dates this old?
Thanks in advance,
Chris
|
Sorry, my mistake. The cutoff date is anything before September 9th 2001 does not sort. |
|
Creating logbook by copying an existing one crashes elog, posted by Chris Howe on Thu Jul 28 15:33:21 2005
|
Hi,
Trying to create a new logbook from an existing one causes elog to crash.
output from DrMingw:
elogd.exe caused an Access Violation at location 00448c6e in module elogd.exe
Writing to location 6e206c65.
Registers:
eax=00240798 ebx=00000020 ecx=6e206c61 edx=00250088 esi=00000000 edi=69726500
eip=00448c6e esp=01c1a1d0 ebp=01c1a1f0 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000297
Call stack:
00448C6E elogd.exe:00448C6E
00445F17 elogd.exe:00445F17
as the service restarts elog the browser then displays:
"Cannot open file elog.pwd: No such file or directory
Please use your browser's back button to go back"
If you try and create a new logbook from scratch (i.e. not a copy) then the browser displays:
"Cannot open file elog.pwd: No such file or directory
Please use your browser's back button to go back"
In both cases the new logbook is created.
any ideas?
Chris |
|
Literal comma in elogd.conf entries where "," is an item separator?, posted by Chris Green on Mon Jul 25 19:24:47 2005
|
Hi,
Could you tell me if there is a way to escape characters in elogd.conf? Particularly, I want to have a drop-down "Keyword" attribute where one of the options is "Spelling, grammar and typos.". This invariably gets split into "Spelling" and "grammar and typos". I've tried "\,", ",,", "%," and "%27", to no avail.
Can I get there from here, or do I have to go someplace else?
Thanks,
Chris. |
|
Re: Literal comma in elogd.conf entries where "," is an item separator?, posted by Chris Green on Mon Jul 25 21:41:00 2005
|
Sorry for being dense. Thanks for this,
Chris. |