Find cannot find values with brackets, posted by Sebastian Schenk on Fri Jun 14 11:29:30 2019
|
For demonstration, I created https://elog.psi.ch/elogs/Linux+Demo/8
The Find search for category aaa(bb) does not give results.
A quick filter corrects the value to aaa\(bb) and delivers results. |
Re: Find cannot find values with brackets, posted by Stefan Ritt on Fri Jun 14 12:43:04 2019
|
I‘m happy to merge the PR after a quick test next week.
Stefan
Sebastian |
Unable to add entries with command line elog.exe with SSL, posted by Antonio Bulgheroni on Fri Jun 28 17:00:10 2019
|
Dear all,
we have a running elog installation using SSL (with the self-signed certificate). Generally we use the web interface, but we have been asked
if it was possible to automatically insert elog entries via command line. |
|
restrict edit time, posted by Sebastian Schenk on Mon Jul 15 17:35:48 2019
|
Hello,
I have experienced some inconveniences with the restrict edit time option.
First, it is not possible for admin users to edit an entry after the edit time. |
|
Re: Unable to add entries with command line elog.exe with SSL, posted by Antonio Bulgheroni on Mon Aug 12 13:11:54 2019
|
Any news for my problem?
Your help is very much appreaciated!
thanks :) |
|
Re: Unable to add entries with command line elog.exe with SSL, posted by Andreas Luedeke on Wed Aug 14 13:25:15 2019
|
I am using SSL with ELOG and it works fine with the "elog" executable. I am no expert on SSL, but I can provide my two cent what you could
try, maybe it helps:
SSL desires to run on the port 443 - I have no idea if you can force it to run on an arbitrary port, it might be possible. But does it |
|
Re: Unable to add entries with command line elog.exe with SSL, posted by Antonio Bulgheroni on Wed Aug 14 18:36:17 2019
|
Dear Andreas,
thanks for your message.
Here are the answers to your questions. |
|
Re: Unable to add entries with command line elog.exe with SSL, posted by Antonio Bulgheroni on Thu Aug 15 09:45:37 2019
|
As promised, here is the results of the additional debugging.
Changing to port 443 doesn't help. I keep having exactly the same behaviour, it is to say: |