ELOG Forum

Re: FCKEditor not working correctly on a Windows server.

3.1.0-c701f01

I know I'm a little late but is there a way to do this from elog? I've tried using the following line in the config but it doesn't seem to work in IE10. I figure if there is a way to modify the <head> before the page loads there could be hope.

Top text = <script>var meta = document.createElement('meta');meta.httpEquiv = "X-UA-Compatible";meta.content = "IE=edge";var head = document.getElementsByTagName('head')[0];head.insertBefore(meta, head.firstChild);</script>

Richard Stamper wrote:

If you are using IE as your browser, the problem may be with that rather than the server. By default IE 11 display intranet sites in a "Compatibility mode" which breaks the FCKEditor in Elog version 3. Fortunately this mode can be disabled, which is what I have had to advise users here to do.

Click on the "cogwheel" and select "Compatibility settings"
Deselect "Display intranet sites in Compatibility view"

Pictures attached

Marty Jansen wrote:

Sorry for the late reply. I have installed a slightly newer version of Elog, but the results are the same. I do get de the 3 editor bars, but the top 2 are greyed out and the bottom one doesn't do anything if clicked. I have commented out the lines that refer to the online equation editor, but that doesn't help much either. I think I let it rest. The old 2.9.xx version still works great, so we leave it at that.

Thanks anyway for the suggestions

Marty

Marty Jansen wrote:

Hi,

After working many years with previous versions of ELOG, I decided to update to the latest version.
I have installed ELOG version 3.1.0 on a WIndows 2012R2 server with IE 1. The editor is showing up, but everything is greyed out, execpt for some items on the bottom row. (Style, Lettertype...) and after I do load a preset text form with different colors, the page remains white. The tables and text in the form is showing up.

The previous version with the older editor was working great on the same server.

Any suggestions?

68438

Sat Oct 1 15:32:53 2016

Chris Smyth

chris.smyth@comcast.net

Enforcement of password complexity

2.7.1

Is there a way to enforce password complexity for users?

Either in this version of elog or the newest version?

68443

Wed Oct 26 16:39:38 2016

Datetime format with elog client

What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).

I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.

68444

Wed Oct 26 21:41:42 2016

David.Pilgram@epost.org.uk

UPDATE:

As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.

I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.

Alan Grant wrote:

What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).

68445

Wed Oct 26 22:15:46 2016

David Pilgram

3.1.2

Hi Alan,

I have no idea if this helps but the Date and Time formats in the config file internally interconnect, as I discovered in trying to define them separately. Define one, and the other is defined.

I only mention this as I spent some hours trying to sort out the issue, only to learn it was a "feature" that Stefan didn't want to correct as it may affect too many others. I can understand that, and made a different solution to what I wanted to do.

Alan Grant wrote:

UPDATE:

I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.

Alan Grant wrote:

What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).

68446

Thu Oct 27 04:16:10 2016

I really appreciate your reply David.

There's only one Datetime defined field that I'm working with so I'm not sure what you mean, if you don't mind elaborating? It sounds interesting.

The only thing I gather right now from what you're saying is that there's essentially two locations where a field can be defined - in the Config file, or via the format of the data itself in the client command - but I could be wrong.

David Pilgram wrote:

Hi Alan,

I have no idea if this helps but the Date and Time formats in the config file internally interconnect, as I discovered in trying to define them separately. Define one, and the other is defined.

Alan Grant wrote:

UPDATE:

I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.

Alan Grant wrote:

What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).

68447

Thu Oct 27 11:18:17 2016

Andreas Luedeke

andreas.luedeke@psi.ch

3.1.2