Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 790 of 796  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  Draft   Tue Mar 21 14:25:26 2023 Reply Daniel SajdykHello,daniel.sajdyk@gmail.comQuestionLinuxV3.1.4-dc4af9b8Re: HTML Editor not working after enabling SSL

Hello,

I found that someone else had the same issue - https://dev.ckeditor.com/ticket/10874#no1

But I don't know why

Daniel Sajdyk wrote:

Hello,

After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long. 

After changing SSL to 0, everything work flawlessly.

Does anyone know what can cause this behaviour?

Best Regards
Daniel

 

  69782   Mon Apr 15 17:50:20 2024 Reply Stefan RittHastefan.ritt@psi.chBug reportWindowsELOG V3.1.3-793Re: Record date isn't set to current date when replying to elogs

Have you tried the config option "Preset on reply <attribute> = $date". On a reply, the <attribute> will be preset with the current date.

Stefan

Celeste Torkzaban wrote:

Hello,

I started using the record date feature in one logbook, since we plan to copy over old entries Joplin/Onenote. When starting a new entry, I see that the record date is automatically set to the current date, but when I reply to an elog, the record date is automatically set to the record date of the elog I'm replying to. Is there a way to fix this?

 

 

  69653   Tue Feb 28 19:22:50 2023 Reply Stefan RittFind stefan.ritt@psi.chInfoWindows3.1.4Re: Exporting the entries from ELOG

Find -> Export to...

Illam Pakkirisamy wrote:

Hi,

Is there a way to export the ELOG entries into a file like an Excel sheet or something.  I see import but not export.

Appreciate your help.

Thanks.

Illam

 

  69640   Thu Feb 2 10:23:45 2023 Reply Antonio BulgheroniCoulantonio.bulgheroni@gmail.comQuestionLinux3.1.4Re: CKeditor Settings Cant Be Changed

It means that you could replace the currently distributed CKeditor with a fresh vanilla installation of CKeditor? 

James Smallcombe wrote:

So it was just a clearing cache issue. elogd was telling the browser to use/not use CKeditor based on the aformentioned, and browser was then using the cached version. Fixed now.

And FYI for anyone who reads this when trying to modify CKeditor themselves, it seems elog needs the iFrame Editing Area plugin included.

Stefan Ritt wrote:

elogd checks for the "scripts/ckeditor/ckeditor.js" file to detect the presence of CKeditor.

James Smallcombe wrote:

I wanted to change some CKeditor settings so tried modifying elog/scripts/ckeditor to no avail.

I wiped elog/scripts/ and dropped a fresh download of CKeditor4, with only the basic extensions. But when I open the elog it still shows the full toolbar, with elog default style and with all extensions operational.

If I leave elog/scripts empty, I get "CKeditor NOT detected" when starting elogd and the HTML option is empty and shows nothing, all as expected.

Does anyone understand this? Is there some CKeditor configuration file elog is defering to that I've overlooked? I have tried system wide seaches just in case.

 

 

 

  58   Mon Jul 8 21:01:00 2002 Question Christian KorschanChristian.Korschan@CTBTO.ORGBug report  Compiling elog 2.0.4 on Solaris
Comiling elogd 2.0.4 under Solaris obviously fails with

gcc  -o elog elog.c -lsocket -lnsl
gcc  -o elogd elogd.c -lsocket -lnsl
elogd.c: In function `ss_file_find':
elogd.c:1372: `alphasort' undeclared (first use in this function)
elogd.c:1372: (Each undeclared identifier is reported only once
elogd.c:1372: for each function it appears in.)
make: *** [elogd] Error 1

because alphasort is an ucb'ism which does not exist under SYSV

... not very portable :-(
  82   Wed Jul 24 16:44:44 2002 Question Christian KorschanChristian.Korschan@CTBTO.ORGBug report  elog-2.0.5 core dumps under Solaris
Just compiled elog-2.0.5 under Solaris 8 and 9  without any warnings/errors
but the elogd binary just core dumps:

# /opt/ELOG/bin/elogd -c /opt/ELOG/elogd.cfg 
Indexing logbook "demo"...
Bus Error (core dumped)

.. tracing elogd shows:

[ lines snipped ]
2964:   brk(0x005B8A68)                                 = 0
2964:   ioctl(1, TCGETA, 0xFFBEE6BC)                    = 0
Indexing logbook "demo"...
2964:   write(1, " I n d e x i n g   l o g".., 27)      = 27
2964:       Incurred fault #5, FLTACCESS  %pc = 0x000164C0
2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
2964:       Received signal #10, SIGBUS [default]
2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
2964:           *** process killed ***
#

... any glue ?
  83   Wed Jul 24 17:24:31 2002 Idea Christian KorschanChristian.Korschan@CTBTO.ORGComment  Re: elog-2.0.5 core dumps under Solaris
> Just compiled elog-2.0.5 under Solaris 8 and 9  without any warnings/errors
> but the elogd binary just core dumps:
> 
> # /opt/ELOG/bin/elogd -c /opt/ELOG/elogd.cfg 
> Indexing logbook "demo"...
> Bus Error (core dumped)
> 
> .. tracing elogd shows:
> 
> [ lines snipped ]
> 2964:   brk(0x005B8A68)                                 = 0
> 2964:   ioctl(1, TCGETA, 0xFFBEE6BC)                    = 0
> Indexing logbook "demo"...
> 2964:   write(1, " I n d e x i n g   l o g".., 27)      = 27
> 2964:       Incurred fault #5, FLTACCESS  %pc = 0x000164C0
> 2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
> 2964:       Received signal #10, SIGBUS [default]
> 2964:         siginfo: SIGBUS BUS_ADRALN addr=0x2F757372
> 2964:           *** process killed ***
> #
> 
> ... any glue ?

Hmmm - stupid me used a broken patch  used to get rid of alphasort under 2.0.4
this entry and it's predecessor should be DELETED - sorry for the confusion :-(
  84   Wed Jul 24 17:29:00 2002 Reply Christian KorschanChristian.Korschan@CTBTO.ORGBug report  Re: Compiling elog 2.0.4 on Solaris
> > Comiling elogd 2.0.4 under Solaris obviously fails with
> > 
> > gcc  -o elog elog.c -lsocket -lnsl
> > gcc  -o elogd elogd.c -lsocket -lnsl
> > elogd.c: In function `ss_file_find':
> > elogd.c:1372: `alphasort' undeclared (first use in this function)
> > elogd.c:1372: (Each undeclared identifier is reported only once
> > elogd.c:1372: for each function it appears in.)
> > make: *** [elogd] Error 1
> > 
> > because alphasort is an ucb'ism which does not exist under SYSV
> > 
> > ... not very portable :-(
> 
> I was not aware of this. Actually, I don't need 'alphasort' so I removed it 
> from the source. The update is at
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
> 
> Please give it a try.

ok - i just continued with 2.0.5, but apparently it still has an UCB'ism
(scandir) that does not work under SYSV:

$ make
gcc -g -o elogd elogd.c -lsocket -lnsl
Undefined                       first referenced
 symbol                             in file
scandir                             /tmp/ccy0Z3iV.o
ld: fatal: Symbol referencing errors. No output written to elogd
collect2: ld returned 1 exit status
make: *** [elogd] Error 1
$ egrep scandir elogd.c
  n = scandir(path, &namelist, NULL, NULL);
$ 
ELOG V3.1.5-2eba886