You don't need "elog" to run the logbook, the executable "elog" is only needed to create entries without the web interface. Stefan should adapt "elog.c" some day to be compatible with the default switches of modern, paranoid compilers; but for the moment you can ignore this.

If you use the newly created "elogd", does that reproduce the former problem?

Just put (char *) in front of all malloc(). I will include the fix in the next official version. 

/Stefan

 I have been able to compile Elogd successfully in Windows with Visual Studio 2010 but not with Elog.  Attached are errors, it complaint about buffer[i] type char * being assigned type void *.  If anyone has been successful compile the elog, please give me a hint.  Thanks.

> > In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
> > Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
> > in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text. 
> 
> That's strange. I just tried myself (by accident I have the same versions of Chrome and OSX) and it just worked fine. The fckedit code has not change a long time, so I guess it's not related to the exact version of 
> elogd. Anyhow I want to switch to ckedit when I get some time, which maybe fixes the problem. What happens if you try to write in this forum, do you have the same problem? Sometime the fcdedit code take 
> quite long time to load when accessed remotely. If your browser gives up, you might hat to click on "reload". In chrome there is also the "Developer tools" window, which shows you all HTTP requests and 
> responses on the network. Otherwise I run out of ideas what could be different for you compared to me.
> 
> Cheers,
> Stefan

Later on, I tried the prescription pointed to in that thread that says in scripts/fckeditor/editor/js/fckeditorcode_gecko.js to replace

FCKTools.FixDocumentParentWindow = function(A){ if (A.document) A.document.parentWindow=A; for (var i=0;i<A.frames.length;i++) FCKTools.FixDocumentParentWindow(A.frames[i]);};

with: 

FCKTools.FixDocumentParentWindow = function(A){try{ if (A.document) A.document.parentWindow=A;} catch(e){};for (var i=0;i<A.frames.length;i++) FCKTools.FixDocumentParentWindow(A.frames[i]);};

and after I got all my brackets straight, my pages were visible.  I'm still not sure when this turned up, since I use my elog every day (hour) and so I'd hardly miss it when I upgraded various things, although I don't watch Chrome updating itself that closely.

Have a good holiday!

> In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
> Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
> in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text. 

That's strange. I just tried myself (by accident I have the same versions of Chrome and OSX) and it just worked fine. The fckedit code has not change a long time, so I guess it's not related to the exact version of 
elogd. Anyhow I want to switch to ckedit when I get some time, which maybe fixes the problem. What happens if you try to write in this forum, do you have the same problem? Sometime the fcdedit code take 
quite long time to load when accessed remotely. If your browser gives up, you might hat to click on "reload". In chrome there is also the "Developer tools" window, which shows you all HTTP requests and 
responses on the network. Otherwise I run out of ideas what could be different for you compared to me.

Cheers,
Stefan

In the past couple of days, I seem to have developed a problem with making entries into elog's displayed with Chrome (the latest, 31.0.1650.63) on 
Mac OS (10.9.1, the latest).  The problem occurs with attempting to edit or enter HTML encoded pages with fckedit; although pages render correctly 
in list mode, if you try to edit or enter an entry, the page is blank, the cursor is missing, you can't see text or type new text.  I ran elogd -v by hand, 
and there were no obvious problems, and I looked at the developer consoles in Chrome, and the only place I see any hint of what the problem might 
be is the Javascript console which says this:

event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
Uncaught SecurityError: Blocked a frame with origin "http://localhost:8080" from accessing a frame with origin "chrome-
extension://pioclpoplcdbaefihamjohnefbikjilc".  The frame requesting access has a protocol of "http", the frame being accessed has a protocol of 
"chrome-extension". Protocols must match.
 fckeditorcode_gecko.js:36

It works ok in Safari, but it would be nice to use Chrome, and it was working ok until recently.  I don't think the problem occurred when I updated to 
Mac OS 10.9.1, but I don't keep careful track of the Chrome version.  It's not critical, but I pretty much exhausted what I knew how to debug.  I have 
close to the latest elog (2.9.2-2455), although I see the same phenomenon on this elog (.2.9.2-2475) and I think it's related to this thread:

http://productforums.google.com/forum/#!msg/maps/hQhwWA56NbA/2XL35dU7le4J

I tried the prescription in the October 22 entry, but it didn't seem to help, although I wasn't sure I had really tested it with compressed javascript and 
cache and what have you.

Hi Andreas,

Thank you so much for the reply and info; Much appreciated!  I turned up a CentOS 6 VM and the installation, using the RPM's provided on the 'downloads' page here, worked perfectly and was very straight-forward and easy.

The D/L page includes the Debian repositories (which is how I installed on Debian in the first place) but only installed v2.5.2.  I needed to get to the newest version (ELOG V2.9.2-2455) so I can setup authentication and SSH.  (And also so that when I am reading the manuals and documentation online, provided at this site, that is makes sense to the version I am running.)  I also want to add that it seems that I am able to bring over my older 2.5.2 logbooks to 2.9.2 without any problem.  To do that, I just rsync'd the logbooks from old to new.  They seem to work just fine under the newest version.

I'm good to go.  Anyone looking for an easy deployment of ELOG, especially in a production environment, I can attest that the RPM's provided here make it very simple to deploy on Cent6.

Thanks!