Re: Body of new messages not getting saved when submitted, posted by Harry Martin on Mon Nov 22 19:45:08 2021
|
After downgrading ckeditor, my elog installation is working again. Thanks for your help.
Harry
Martin wrote:
(disregard my recent post here about missing package -- that wasn't |
|
Re: Display edit time, posted by Stefan Ritt on Wed Nov 24 08:38:33 2021
|
Creat an attribute "last edit" and set it to the last edit time. Something like this:
Attributes = ...., Last edit
Preset Last edit = $date |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Wed Dec 1 13:05:14 2021
|
Please issue the elog command with an added "-v" flag and post the output here.
Stefan
Jose |
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. |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 08:28:19 2021
|
Hi Stefan,
Here is the, I believe, relevant part of the output:
------------------------------------------------- |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Andreas Luedeke on Tue Dec 7 11:56:37 2021
|
If you need HTTPS then you must specify the "-s" option.
You could have looked into the help of the elog command:
> elog -h |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Jose Caballero on Tue Dec 7 14:25:37 2021
|
This is what I get with -s:
---------------------------------
Successfully connected to host elog-1.matrix.com, port 80 |
|
Re: Unclear how to use the command line tool /usr/bin/elog, posted by Stefan Ritt on Tue Dec 7 14:46:16 2021
|
If you use HTTPS, you have to connect to port 443 of your server, using the "-p" option.
Furthermore, you run under an Apache server, right? How do you do the redirecting to elogd? I guess you specified a subdir in the URL named /LogBook
to redirect to elogd. The you use another part of the URL to select the logbook, which again might be "LogBook". Is that correct? So your full |