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.

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

Yes replacing the CKeditor folder with a vanila download works without issue, provided you clean the cache.
For what I originally wanted to do (modifiying the toolbar) I could have just run elog/scripts/ckeditor/samples/toolbarconfigurator/index.html and edited the config file, but a clean cache is needed (on Chrome, Firefox and Edge).

I don't get your point. If you add the meta tag wiht the viewport, then the IE7 mode will load the CKEditor? The CKEditor home page says that IE7 is not supported any more, so I wonder if this simple tag might help. Can you turn off the compatibility mode on a per-URL basis?

If I try on my smatphone, the display is correct, so why you need the viewport tag? Can you shouw me examples?

If you have nice CSS features which are helpful for everybody, please send them to me and I can include it in the distribution, but only after you convince me that it works (almost) everywhere.

Best,
Stefan

The viewport thing and the IE7 mode thing are separate issues.

OK, maybe it's a CKEditor thing then. I thought it might be. It seems pretty stupid that the default setting in IE is to emulate an older browser - although I guess a lot of people have very outdated intranet sites. Anyway, we have a fix here so I don't think you need to do anything. Just thought you might want to know.

The viewport tag issue - see attachments. The first two are the log selection page and the list page, both without the viewport tag. Obviously you can zoom in, but this is how they appear by default, as (apparently) Chrome tries to render the whole page width. The third one is how the list page appears when the viewport tag is added, and the fourth is with my custom CSS to put the columns on separate lines. It's probably very bad CSS, so I'm certain that it's not robust or cross-platform, but it works for me :)

/* make things look a bit nicer on smaller screens */
@media (max-width: 700px) {
	table.listframe td, table.listframe th {
		display: none;
	}

	/* show id, date, personnel, summary in separate lines */
	table.listframe td:nth-of-type(-n+2), table.listframe td:nth-of-type(4), table.listframe td:nth-last-of-type(2) {
		display: block;
		border: 0px;
	}
}

The viewport thing and the IE7 mode thing are separate issues.

OK, maybe it's a CKEditor thing then. I thought it might be. It seems pretty stupid that the default setting in IE is to emulate an older browser - although I guess a lot of people have very outdated intranet sites. Anyway, we have a fix here so I don't think you need to do anything. Just thought you might want to know.

The viewport tag issue - see attachments. The first two are the log selection page and the list page, both without the viewport tag. Obviously you can zoom in, but this is how they appear by default, as (apparently) Chrome tries to render the whole page width. The third one is how the list page appears when the viewport tag is added, and the fourth is with my custom CSS to put the columns on separate lines. It's probably very bad CSS, so I'm certain that it's not robust or cross-platform, but it works for me :)

/* make things look a bit nicer on smaller screens */
@media (max-width: 700px) {
	table.listframe td, table.listframe th {
		display: none;
	}

	/* show id, date, personnel, summary in separate lines */
	table.listframe td:nth-of-type(-n+2), table.listframe td:nth-of-type(4), table.listframe td:nth-last-of-type(2) {
		display: block;
		border: 0px;
	}
}

I have had to play around with viewports for other reasons than elog, but I do have a couple of comments to make.  Obviously the meta tag viewpoint has to be added in.  Also, elog was written for large screens (no-one thought anything else was possible when elog was started), and it is relatively recent that mobile devices have become a significant percentage of views of web pages.  Google is downgrading websites that are not mobile-friendly - that is, not starting with the viewport meta tag.  So there may have to be a fair re-arrangement of the default layout of elog for it to remain sensible on mobile devices. 

The attached css file (I made minor edits to someone else's - and they were freely giving it away), allows tabs running along the top of the page (below the title) for navigation.  So it would be nice if the elog tabs could operate in the same way when being used on a mobile device.  If select on one, it can become a drop down menu to select other tabs under that general top layer (I don't think that function is in the attached css file).  I've put a sample of such tabs (not drop down) in header.html attached.  Though I'm sure everyone else can write far better css and html code.

As I'm not a heavy mobile user, and often do need the whole screen to view matters, it would be nice if all of this could be optional in the elog.cfg file.

/* make things look a bit nicer on smaller screens */
@media (max-width: 700px) {
	table.listframe td, table.listframe th {
		display: none;
	}

	/* show id, date, personnel, summary in separate lines */
	table.listframe td:nth-of-type(-n+2), table.listframe td:nth-of-type(4), table.listframe td:nth-last-of-type(2) {
		display: block;
		border: 0px;
	}
}

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