Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 769 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
    icon2.gif   Re: WYSIWYG Editor Not Showing in HTML Mode, posted by Pawel Nita on Mon May 5 13:50:12 2025 

Hi John,

Thanks for the message! I’ve downloaded CKEditor version 4.22, since newer versions are no longer fully open source and come with restrictive licensing.  I now have the full CKEditor 4.22 package locally, but I’m not quite sure what the next step is. Should I place it somewhere specific in the ELOG directory structure or modify one of the templates to enable it? Any pointers on how to connect it properly to ELOG would be very helpful.

 

John wrote:

Hi Pawel, I *think* we (you) need the 'ckeditor' program installed on your system for it to work. I am

Pawel Nita wrote:

Hi all,

I'm experiencing an issue on Kubuntu 24.04 where the WYSIWYG editor (in HTML mode) doesn't appear at all. This happens across multiple browsers (tested with Firefox and Chromium). The editor area is simply blank, without any visible toolbar or editable content area.

Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!

Thanks in advance,
Pawel

 

 

icon1.gif   passing %s to $shell interpreted differently in preset vs preset on reply, posted by Harry Martin on Wed Jun 18 01:20:47 2025 

I am finding that '%s' passed to a $shell(...) command must be escaped when calling from Preset on reply, but not when calling Preset new.  Example:

[tickler]
Comment = Automated Tickler List Experiment
Attributes = Blurb, TickleDate
Type TickleDate = date
Required Attributes = Blurb
Preset TickleDate = $shell(date -d 'now + 30 days' '+%s')
Preset on reply TickleDate = $shell(date -d 'now + 30 days' '+%%s')
Date Format = %Y-%m-%d

Note that I have to escape the Preset on Reply's shell command argument with double percent signs, but not on Preset new.  The configuration I have provided here does work and correctly overrides the output per the Date Format spec.  This scenario should be easy to reproduce.

It could be I am doing something incorrectly, but it seems to me that there is no reason why the calls should need to be handled differently.  I can live with this for the moment, but I do hope it is fixed in a later release so that $shell calls have consistent syntax and semantics.

 

    icon2.gif   Re: strage colors when only 'cmd=Search' is given as command, posted by Stefan Ritt on Mon Jul 1 10:31:31 2002 
> Try this URL
> 
> http://midas.psi.ch/elogdemo/Forum/?cmd=Search

Ok, has been fixed. Will be included in the next version.
    icon2.gif   Re: last?? links in threaded mode, posted by Stefan Ritt on Mon Jul 1 10:32:28 2002 
> The mode (i.e. summary, threaded, full) should be kept for the
> last??? and past??? links on a page.
> 
> For instance:
> 
> http://midas.psi.ch/elogdemo/Linux/last10?mode=threaded
> 
> The last20 link on this page should also be in threaded mode.

Has been fixed. Will be included in next version.
    icon2.gif   Re: trailing '-' are removed from a message!!!, posted by Stefan Ritt on Mon Jul 1 11:35:28 2002 
> Try to submit the following message:
> 
> *** cut here ***
> -------------------------------------------------
> -------------------------------------------------
> -------------------------------------------------
> -------------------------------------------------
> *** cut here ***
> 
> In fact after the next line there were 4 lines with '-', but
> they were not accepted by elog:

Ok, also fixed. Updated version is at 

http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c

Here is actually an example with '----' at the end:

-------------------------------------------------
-------------------------------------------------
-------------------------------------------------
-------------------------------------------------
    icon2.gif   Re: exit status of elog, posted by Stefan Ritt on Mon Jul 8 10:42:38 2002 
> The exit status of elog is always 1.  It should be zero for
> a successful submission.

Has been fixed in 2.0.4
    icon2.gif   Re: elog submit problem, posted by Stefan Ritt on Mon Jul 8 10:44:08 2002 
> If a message is submitted via the elog command then the reply string '> ' 
is only inserted in the first line if a reply is made.
> This message was submitted with the following commandline:
> elog -v -h midas.psi.ch -p 80 -s elogdemo -l Forum -a "Icon=icon4.gif" -
a "Author=Heiko Scheit"  -a "Author Email=h.scheit@mpi-hd.mpg.de" -
a "Subject=elog submit problem" "...Message-text..."
> Please press the reply button to see the problem.

Has been fixed in 2.0.4 (as you can see from this entry). Please make sure 
not to submit too long lines via "elog". For browser submissions, the line 
length is limited to 78 characters, but not for "elog" submissions.
    icon2.gif   Re: reverse sort and threaded mode does not display first entry, posted by Stefan Ritt on Mon Jul 8 10:45:37 2002 
> When the option 'Reverse sort = 1' is used then the first entry
> is not displayed (ID=1) when threaded mode is requested.
> 
> Probably you can see the problem using this link and switching 
> on reverse sort.  
> 
> http://midas.psi.ch/elogdemo/Linux/last20?mode=threaded

Has been fixed in 2.0.4, have a look at

http://midas.psi.ch/elogdemo/Linux/last20?mode=threaded&reverse=1
ELOG V3.1.5-3fb85fa6