I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash. 

Internet Explorer fails to display correctly some aspects of pages generated by elog when the zoom functionality is used (Ctrl + and Ctrl -).  This is really a bug in the IE renderer rather than elog, but since IE can be persuaded to do better relatively easily it might be worth making some minor changes to make elog more robust when used with the buggy Microsoft browser.

The problem I encountered was initially with the multiple checkboxes for an Moptions attribute, but I noticed later it also affects the logbook tabs at the top of the screen.  If you start creating a submission to this forum in IE (7 or earlier, at least) you can see the problem; when zooming, the text labels and  the checkboxes do not scale together so start overlapping, and the same happens with the logbook tabs and the text links on them.  The problem is apparently to do with a proprietary IE concept called "layout" - see http://www.satzansatz.de/cssd/onhavinglayout.html for details - and IE struggles when some elements do not have the hasLayout property set to "true".

The fix is to coerce elements to have the hasLayout element set to "true" by giving them some benign CSS property.  The best I can find is to set "display: inline-block" for some of the key elements, and this can be done by modifying default.css rather than the elogd.c code.

Adding

span {
  display: inline-block;
}

to default.css (e.g. just after the default style definition for the "td" element) and adding

  display: inline-block;

to the style sets for the .sltab and .ltab classes (generic, not those specific to the "a" element) seems to prevent IE doing bad things with the display when zooming without messing up the display in Firefox.  I have not tested this comprehensively or in any other browsers, but I thought it might be worth passing on.

Cheers,

Richard Stamper

Hello Stephan,

the fckeditor is not running.

I have installed elog 2.7.7 rev. 2246 on windows xp.

I have not changed the default config after the installation:

Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

I have started the elog server manually to see if the editor will start, below you will find the output:

elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246
Indexing logbooks ... done
Server listening on port 8080 ...

How can I activate the editor?

Thanks,

Michael

 

I have found the problem:

the fckeditor folder contains not all necessary files after installation of Elog version 2.7.7.

I have downloaded the fckeditior manually from:

http://www.fckeditor.net/.

and replaced the faulty one with the new one.

Now the editor is running fine and I see the menu bar when I choose Encoding HTML:

elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246
FCKedit detected
Indexing logbooks ... done
Server listening on port 8080 ...

Stefan could you please ckeck if some files are missing in the fckeditor folder within the elog version 2.7.7 rev. 2246.

Thanks

 You can also try to use a different browser.

Soren

Hello,

is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?

Regards

Michael

A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?

Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else. 

 Thanks for your fast answer.