Problems with german_UTF8 language, posted by Andreas Luedeke on Mon Aug 21 11:22:09 2017 
|
Hi Stefan,
since recently (a few weeks) ELOG confuses the language translations.
Individual language strings are translated into garbage; most other strings are fine.
Currently I see the string "please select" translated into "ressed" (see attached picture), instead of what's written correctly in the language file "bitte auswählen".
But with every restart the corrupted strings vary: other strings are affected and other garbage strings are shown - some of them unreadable binary code (see Attachment 2).
I have the same version running in English: I see no problems there.
Kind regards
Andreas |
Bug with Drafts and Language German, posted by Andreas Luedeke on Mon Aug 21 11:45:06 2017
|
Hi Stefan,
when one creates a new entry, and a draft entry exists for the logbook, then a menu appears (see attachment).
If one select "Neuen Eintrag anlegen" then it should ignore the draft and create a new entry.
This feat is done by adding a "&ignore=1" to the "new" command: "<URL>/?cmd=New&ignore=1".
The problem is, that it should not be "cmd=New&..." but "cmd=Neu", since the commands are part of the translation.
Due to this, no new entry can be created as long as a draft exists; at least not in any language other than english.
This problem apparently existed since the beginning of drafts, but it only created problems at our site recently.
Kind Regards
Andreas
PS: Here's a patch that works:
diff elogd.c elogd.c-orig
9575,9576c9575,9576
< rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='?cmd=%s&ignore=1';\">\n", loc("Create new entry"),
< loc("New"));
---
> rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='%s';\">\n", loc("Create new entry"),
> "?cmd=New&ignore=1"); |
Re: Bug with Drafts and Language German, posted by Andreas Luedeke on Mon Aug 21 12:16:05 2017
|
I've quickly checked: there are a couple more commands in the source code that are not language encoded. I guess some of them needs correction.
> egrep -n "cmd=[A-Za-z]" elogd.c
10293: rsprintf(" r.open('GET', '?jcmd=Unlock&edit_id=%d', true);\n", message_id);
11784: ("<label for=\"ELCode\"><a target=\"_blank\" href=\"?cmd=HelpELCode\">ELCode</a> </label>\n");
13663: "\r\n%s URL : %s?cmd=Config&cfg_user=%s&unm=%s\r\n", loc("Logbook"),
14562: redirect(lbs, "?cmd=Config");
14625: sprintf(str, "../%s/?cmd=Config", getparam("lbname"));
14678: sprintf(str, "../%s/?cmd=Config", lbn);
15703: combine_url(lbs, host, "?cmd=GetMD5", url, sizeof(url), &ssl);
16378: strcat(str, "?cmd=GetConfig"); // request complete config file
16380: strcat(str, "?cmd=Download"); // request config section of logbook
16570: strcat(str, "?cmd=GetPwdFile"); // request password file
17575: rsprintf("<br><b><a href=\"../%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
17577: rsprintf("<br><b><a href=\"%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
17579: rsprintf("<br><b><a href=\"../%s/?cmd=Synchronize&confirm=1\">", lbs->name_enc);
18959: if (strstr(ref, "cmd=Search&"))
18960: strlcpy(strstr(ref, "cmd=Search&"), strstr(ref, "cmd=Search&") + 11, sizeof(str));
26728: rsprintf("<a href=\"?cmd=Synchronize\">%s</a></td>\n", loc("Synchronize all logbooks"));
| Andreas Luedeke wrote: |
|
Hi Stefan,
when one creates a new entry, and a draft entry exists for the logbook, then a menu appears (see attachment).
If one select "Neuen Eintrag anlegen" then it should ignore the draft and create a new entry.
This feat is done by adding a "&ignore=1" to the "new" command: "<URL>/?cmd=New&ignore=1".
The problem is, that it should not be "cmd=New&..." but "cmd=Neu", since the commands are part of the translation.
Due to this, no new entry can be created as long as a draft exists; at least not in any language other than english.
This problem apparently existed since the beginning of drafts, but it only created problems at our site recently.
Kind Regards
Andreas
PS: Here's a patch that works:
diff elogd.c elogd.c-orig
9575,9576c9575,9576
< rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='?cmd=%s&ignore=1';\">\n", loc("Create new entry"),
< loc("New"));
---
> rsprintf("<input type=button value=\"%s\" onClick=\"window.location.href='%s';\">\n", loc("Create new entry"),
> "?cmd=New&ignore=1");
|
|
|
Re: Problems with german_UTF8 language, posted by Andreas Luedeke on Wed Aug 23 15:11:32 2017
|
Just an update: I've re-compiled, reinstalled and restarted elogd for other reasons and now the corrupted strings are all gone. Everthing looks fine now.
But I never worry when a problem goes away before I could understand it: I'm confident that I will have plenty of time later, when the problem magically re-appears - likely I'll be called on a Friday night :-)
| Andreas Luedeke wrote: |
|
Hi Stefan,
since recently (a few weeks) ELOG confuses the language translations.
Individual language strings are translated into garbage; most other strings are fine.
Currently I see the string "please select" translated into "ressed" (see attached picture), instead of what's written correctly in the language file "bitte auswählen".
But with every restart the corrupted strings vary: other strings are affected and other garbage strings are shown - some of them unreadable binary code (see Attachment 2).
I have the same version running in English: I see no problems there.
Kind regards
Andreas
|
|
|
drop-down list not working, posted by Sara Vanini on Mon Nov 13 12:58:41 2017
|
Hi,
after ubuntu 16 system upgrade, elog version (3.1.1-1-1) on firefox version 56.0+build6-0ubuntu0.16.04.2 , the drop-down menus (Styles, Font, Size, etc) don't work anymore.
How can I fix it?
Many thanks!
Sara |
Entries disappear after editing, posted by Peter K on Sat Jan 27 03:37:11 2018
|
Dear elog community,
We have a problem with elog V3.1.2-bd75964.
Sometimes entries disappear from the list after editing.
I found them in the .log files with attributes
Locked by:
Draft:
But they are not in the list anymore!
The only solution by now is manually remove these two attributes from the file,
but this is terrible.
How can I fix this?
Thanks,
Peter.
|
|
Re: Entries disappear after editing, posted by Stefan Ritt on Mon Jan 29 09:14:35 2018
|
Drafts are message which somebody started to edit, but did not complete, like leaving the page without saving. If you don't like this, you can set "save drafts = 0".
The locking has a similar background. If you have locking on (vis "Use lock = 1"), then one person can "lock" a message, and other then cannot edit the same message. If you don't want that, switch locking off.
Best,
Stefan
| Peter K wrote: |
|
Dear elog community,
We have a problem with elog V3.1.2-bd75964.
Sometimes entries disappear from the list after editing.
I found them in the .log files with attributes
Locked by:
Draft:
But they are not in the list anymore!
The only solution by now is manually remove these two attributes from the file,
but this is terrible.
How can I fix this?
Thanks,
Peter.
|
|
|
Re: Entries disappear after editing, posted by Peter K on Tue Jan 30 14:26:24 2018
|
Thanks for fast response!
I LIKE locking and saving drafts.
The only problem is that the locked message disappeared from the list.
This does not happen every time one left the editor, but sometimes.
I can send you the problematic message as it was disappeared, before I deleted Locked by and Draft attributes.
I can't imagine why it is not shown in the list.
| Stefan Ritt wrote: |
|
Drafts are message which somebody started to edit, but did not complete, like leaving the page without saving. If you don't like this, you can set "save drafts = 0".
The locking has a similar background. If you have locking on (vis "Use lock = 1"), then one person can "lock" a message, and other then cannot edit the same message. If you don't want that, switch locking off.
Best,
Stefan
| Peter K wrote: |
|
Dear elog community,
We have a problem with elog V3.1.2-bd75964.
Sometimes entries disappear from the list after editing.
I found them in the .log files with attributes
Locked by:
Draft:
But they are not in the list anymore!
The only solution by now is manually remove these two attributes from the file,
but this is terrible.
How can I fix this?
Thanks,
Peter.
|
|
|
|