Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 211 of 796  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject
  68035   Thu Jun 25 15:16:51 2015 Reply Ben Shepherdben.shepherd@stfc.ac.ukBug reportLinux3.1.0-2411f95Re: CKEditor won't load under IE Compatibility Mode

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;
	}
}
Stefan Ritt wrote:

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

Ben Shepherd wrote:

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

 

 

 

Attachment 1: 01-logbook-sel-page-no-viewport.png
01-logbook-sel-page-no-viewport.png
Attachment 2: 02-list-page-no-viewport.png
02-list-page-no-viewport.png
Attachment 3: 03-list-page-viewport.png
03-list-page-viewport.png
Attachment 4: 04-list-page-viewport-css.png
04-list-page-viewport-css.png
  Draft   Thu Jun 25 14:55:16 2015 Reply Ben Shepherdben.shepherd@stfc.ac.ukBug reportLinux3.1.0-2411f95Re: CKEditor won't load under IE Compatibility Mode

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;
	}
}
Stefan Ritt wrote:

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

Ben Shepherd wrote:

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

 

 

 

Attachment 1: 01-logbook-sel-page-no-viewport.png
01-logbook-sel-page-no-viewport.png
Attachment 2: 02-list-page-no-viewport.png
02-list-page-no-viewport.png
  68033   Thu Jun 25 12:52:06 2015 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.0-2411f95Re: CKEditor won't load under IE Compatibility Mode

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

Ben Shepherd wrote:

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

 

 

  68032   Thu Jun 25 12:32:48 2015 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowslatestRe: Need to move ELOG to other host

Simply copy over your elogd.cfg file and all files under "logbooks". If you only see former logbooks, you grabbed probably the wrong elogd.cfg file.

Mario Gaertner wrote:

Hi there,

our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?

Many thanks Mario

 

  68031   Wed Jun 24 19:27:49 2015 Angy Mario Gaertnerm.gaertner@estrel.comQuestionWindowslatestNeed to move ELOG to other host

Hi there,

our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?

Many thanks Mario

  Draft   Wed Jun 24 19:22:10 2015  Mario Gaertnerm.gaertner@estrel.comQuestionWindowslatestNeed to move ELOG to other host

Hi there,

our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?

Many thanks Mario

  68029   Wed Jun 24 15:18:30 2015 Warning Ben Shepherdben.shepherd@stfc.ac.ukBug reportLinux3.1.0-2411f95CKEditor won't load under IE Compatibility Mode

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

 

  68028   Thu Jun 18 15:46:28 2015 Reply Hanno Perreyhanno.perrey@nuclear.lu.seBug reportOtherELOG V3.1.1-5eaRe: Upload of images fails from mobile platforms when using ELOG under SSL

Hej Stefan,

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

Cheers,

Hanno

Stefan Ritt wrote:

That's strange. Might have to do with the SSL library elog uses. I just tried this forum (actually the "Demo"), and it worked fine through SSL, but I use an Apache proxy server for elog implementing the SSL protocol, which might be slightly different.

Hanno Perrey wrote:

Hej,

I discovered a problem uploading images taken with the cameras of mobile devices to new elog entries directly from said devices. When selecting the image and choosing "Upload", either the blue page loading indicator gets stuck at around 10% (mobile Safari, iOS 8.3, iPhone 4 and iPad mini) or the error message "failed secure connection; connection reset while page was being loaded" ("Fehler: gesicherte Verbindung fehlgeschlagen. Verbindung zum Server wurde zurueckgesetzt waehrend die Seite geladen wurde") appears shortly after (Android 5.02, Firefox 37.0.2, Motorola G).

From the desktop browser (Firefox 38.0.5, OSX 10.10) there is no problem uploading images at all.

So far, this problem is very reproducible, but only when using ELOG with SSL enabled. Without SSL, the problem disappears on all platforms.

The ELOG daemon runs under Linux (Fedora 18) and I have also tried using the latest development version of ELOG.

Running ELOG with debug messages the only output after the page has been loaded is:

TCP connection #0 on socket 4 closed
TCP connection #0 on socket 4 closed

After these, there is no further output and the mobile devices do not indicate any progress either even after many mi.

The minimal config file I have been using is:

[global]
; network
port = 443
SSL = 1
URL = https://my.server.somewhere/
; paths
Logbook dir = /usr/local/elog/logbooks
Resource dir = /usr/local/elog
Logfile = /tmp/elog.log


[demo]
Attributes = Author, Type, Category, Subject
Required Attributes = Author, Type
Options Type = Status, Modification, Problem Report, Problem Details, Problem Fixed, Other
Options Category = Facility, Experiment, IT, Other
List Page Title = $logbook - $subject

As mentioned before, removing the first three lines fixes the problem (the URL line points to my actual server of course).

I would appreciate any pointers on how to debug this further! The functionality of posting images directly from mobile devices is quite important for the planed deployment of ELOG and I would very much prefer to have SSL enabled when doing so.

 

Thanks and cheers,

Hanno

 

 

ELOG V3.1.5-fe60aaf