Hej Stefan,

thanks for the suggestion -- through a Apache proxy the upload does indeed work without problems.

Cheers,

Hanno

I just upgraded to 3.1.0 after many years using 2.9.2. Our eLogs are absolutely crucial for the operation of our accelerators, so first of all I'd like to say: thanks a lot for everything you've done! It's a rock-solid application that works really well.

The issue I'm having is a minor one. Some of our users are using Internet Explorer 11, which has a Compatibility Mode option that is enabled by default for intranet sites (of which our eLog is one). This mode emulates IE7, and this causes the CKEditor rich text box to fail to load. I can tell our users to disable the CM setting on their browsers, but it may be that a simple server-side fix is possible as well.

It would be nice if the eLog pages could have a <meta name="viewport" content="width=device-width, initial-scale=1.0"> tag, so that it displays nicely on smaller screens. I've been adding this myself in some Javascript code (see elogHelper.js on the above-linked website), but it doesn't appear on every page (the logbook selection page, for instance). I also made some modifications to the CSS so that the list display collapses down when the browser window is very narrow.

The new autosave functionality is really good. I hacked something together to do this for our log a while ago, but it's nice that it's inbuilt now.

Thanks again!

Ben

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;
	}
}

In the emails generated by anyone making an entry in this log book, every apostrophe is followed by a semi-colon.  So the text "I don't think..."  appears in the email as "I don';t think...", and possibly that comment will appear in the email as "I don';;t think...." - not sure on the last bit.  It has been around in the past few versions of elog, but don't recall precisely when this started occurring.  It was fine back in February, with v2.9.2 (presumably) running.

Older versions of elogd have a problem with sending long attachements - the send() syscall is not protected against interrupt by SIGALARM. This seems to be fixed in non-SSL builds of current elog (version 3+), 
but for SSL builds, the error handling for the SSL_write() function looks incorrect. In addition, from OpenSSL documentation it is not clear if SSL_write() can handle signal interrupts at all.
K.O.