Hi Stefano,
I've tested it: it does not work.
Neither in edit nor in list view the HTML encoded characters show correctly.
Only in the "Quick filter" menu they show as they should!
But then selecting them in the quick filter will not find any entries :-(

So the short answer: 
avoid characters with a special meaning for regular-expressions in attribute values, in particular if you want to use quick filters.

Cheers
Andreas

> Hi Stefano,
> you could try to html encode the "+" and "-" sign in the option list
> Options Half = +x, -x, both
> Allow HTML = 1
> 
> But of course then you would need to change all existing entries.
> 
> It is just an idea; I did not try this out, it might not work anyway.
> 
> Cheers
> Andreas
> 
> > Dear experts,
> >    I have an elog with an attribute with fixed values, like this:
> > 
> > Attributes = Half
> > Options Half = +x, -x, both
> > 
> > It works fine, but I would like to find (or quick filter) all entries with Half=+x .
> > 
> > If I go to the search form, I can select +x from the dropdown menu for Half, but the search returns no result, even if I do have a number of entries with Half=+x. Likewise if I try to do the same with Quick filter.
> > 
> > I believe that this is due to the fact that the search uses regex, and "+" is reserved. I've tried to perform a search by entering manually and escaped "\+x", and it works as intended.
> > 
> > https://.../?mode=summary&reverse=0&reverse=1&npp=20&Half=%5E%5C%2Bx%24
> > 
> > However, since this attribute has a list of fixed values, it is not possible to entry manually something different "\+x" than what is defined in the config, that is "+x".
> > 
> > Is there a solution for this problem?
> > 
> > I would rather not change the attributes options (to, say, positive/negative), since that would mean changing manually a non negligible number of entries.
> > 
> > thanks,
> >   Stefano

Hello everybody,

we had to setup a new server for our elog some time ago because the old one crashed. We are now running version ELOG V3.1.1-0767eb0.

In the previous installation we had these nice buttons for file upload, time stamp and equation editor, which are also available here in the online version.

I already found that in the installation directory ("/usr/local/elog/") there exists a directory "scripts" containing a file "ckeditor-config.js", which also contains the lines:
"config.extraPlugins = 'timestamp,dndfiles,eqneditor,fileupload';" and "{ name: 'insert', items: [ 'Image', 'Table', 'HorizontalRule', 'Smiley', 'SpecialChar', 'PageBreak', 'FileUpload', 'Timestamp', 'EqnEditor' ] },"

These plugins seem to be available in the subdirectory "scripts/ckeditor/plugins/". But why are they not loaded? Is it just a version issue? Or something else?

It would be nice to get a hint.

Best regards,

Roland

Have you selected "HTML" encoding (below the main message box). The HTML editor is not activated if you have "plain" text encoding. Did you try the default elogd.cfg file? If you modified the config file and did a mistake there, the program can for example not properly find all directories. Also makse sure you did a full install with "make install", not just update the executable.

Stefan

Dear Stefan,

thanks for your hints. Meanwhile we already solved the problem. I think it was caused by the recovery from a backup version after the server crash ... and the retirement of the person who did the previous installation.

We found the following things to be faulty:

1. Somebody linked the "elog/scripts/ckeditor"-directory to "../../javascript/ckeditor" (maybe an independent installation of ckeditor). Due to this the relative path in "ckeditor/config.js" to "../ckeditor-config.js" could not be correctly resolved to be "elog/scripts/ckeditor-config.js". Now we put the absolute path.
2. Furthermore the owner of all files in the elog directory was set to root:root with read access only for root. We changed them now to root:elog and gave read acess for everybody.

Now everything works as expected.

I'm sorry for inconvenience,

Thanks and best regards,

Roland

We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
of this line and either the printout is cut off at the right side, or the whole content is scaled down to very
tiny scale, which makes it unreadable.

Is there a way to enforce line breaks in plain text entries?

> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> very tiny scale, which makes it unreadable.
> 
> Is there a way to enforce line breaks in plain text entries?

Obviously there is: this logbook does add line breaks?!?

Maybe it is only a problem with entries made by the "elog" command?
I'll find it out and re-post.

Cheers
Andreas

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Okay, I found two ways to add very long lines:
- if the very long line does not contain a space then this will screw the printout.
- if the line has been added as plain text using the elog command, there will be no line breaks added.

It would be nice if the elog command would have an option to break lines to a maximum line length.
But for the moment I'll just modify the applications that make use of the elog command.

> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
> > width of this line and either the printout is cut off at the right side, or the whole content is scaled down to
> > very tiny scale, which makes it unreadable.
> > 
> > Is there a way to enforce line breaks in plain text entries?
> 
> Obviously there is: this logbook does add line breaks?!?
> 
> Maybe it is only a problem with entries made by the "elog" command?
> I'll find it out and re-post.
> 
> Cheers
> Andreas

Yepp, this is a (missing) feature of the elog command. Can you pre-process your messages outside of it, or do I have to add code to elog to do that?

Stefan