Error when attempted to submit an entry, posted by Hung Dao on Wed Nov 13 16:11:18 2013 
|
| One of my users reported that he received this error when attempted to submit an editing entry. Basically he is only one to edit this entry. When go ahead to press the button, the entry is updated successfully. What cause and how to prevent this error not to populate? Thanks |
Re: Error when attempted to submit an entry, posted by Stefan Ritt on Wed Nov 13 16:31:28 2013
|
| Hung Dao wrote: |
| One of my users reported that he received this error when attempted to submit an editing entry. Basically he is only one to edit this entry. When go ahead to press the button, the entry is updated successfully. What cause and how to prevent this error not to populate? Thanks |
Please read the documentation in https://midas.psi.ch/elog/config.html und the option "Use Lock". If you don't need locking, just turn it off. |
|
Unwanted characters showing when using Bottom Text Login to a html file, posted by Hung Dao on Wed Nov 13 23:46:38 2013
|
| When using Bottom Text Login to a html file showing some unwanted characters. Also, the ELOG Version is longer displayed.
Bottom Text Login = example.htm
Attached are bottomtextlogin.jpg which shows the characters on the left and example.htm which I used. |
|
Re: Unwanted characters showing when using Bottom Text Login to a html file, posted by Andreas Luedeke on Thu Nov 14 11:31:23 2013
|
| Hung Dao wrote: |
| When using Bottom Text Login to a html file showing some unwanted characters. Also, the ELOG Version is longer displayed. Bottom Text Login = example.htm Attached are bottomtextlogin.jpg which shows the characters on the left and example.htm which I used. |
I have a possible explanation for this problem, but it is just guess work. If I'm right, then just download the latest ELOG version and it will work properly again.
- You've downloaded an elog version from git, which still contained the line 12 in elogd.c: char svn_revision[] = "$Id$";
- Since you did checkout from git, the $Id$ was not substituted.
- ELOG trys to extract the version by this: rsprintf
("<center><a class=\"bottomlink\" title=\"%s\" href=\"https://midas.psi.ch/elog/\">ELOG V%s-%d</a></center>",
loc("Goto ELOG home page"), VERSION, atoi(svn_revision + 13));
- svn_revision + 13 is pointing into the void. Still I would have expected that you get a number as a result.
My advice: download again and retry.
⇄
English (auto-detected) » English
|
|
Re: Unwanted characters showing when using Bottom Text Login to a html file, posted by Hung Dao on Thu Nov 14 20:06:44 2013
|
| Andreas Luedeke wrote: |
|
| Hung Dao wrote: |
| When using Bottom Text Login to a html file showing some unwanted characters. Also, the ELOG Version is longer displayed. Bottom Text Login = example.htm Attached are bottomtextlogin.jpg which shows the characters on the left and example.htm which I used. |
I have a possible explanation for this problem, but it is just guess work. If I'm right, then just download the latest ELOG version and it will work properly again.
- You've downloaded an elog version from git, which still contained the line 12 in elogd.c: char svn_revision[] = "$Id$";
- Since you did checkout from git, the $Id$ was not substituted.
- ELOG trys to extract the version by this: rsprintf
("<center><a class=\"bottomlink\" title=\"%s\" href=\"https://midas.psi.ch/elog/\">ELOG V%s-%d</a></center>",
loc("Goto ELOG home page"), VERSION, atoi(svn_revision + 13));
- svn_revision + 13 is pointing into the void. Still I would have expected that you get a number as a result.
My advice: download again and retry.
⇄
English (auto-detected) » English
|
I have downloaded a latest version. It has displayed the new version as ELOG V2.9.2-bac715d where seems defined in GIT_REVISION as I guess. Then I set Bottom Text Login to a html file, it still shows those unwanted characters. |
|
Re: Unwanted characters showing when using Bottom Text Login to a html file, posted by Andreas Luedeke on Fri Nov 15 08:34:05 2013
|
| Hung Dao wrote: |
|
| Andreas Luedeke wrote: |
|
| Hung Dao wrote: |
| When using Bottom Text Login to a html file showing some unwanted characters. Also, the ELOG Version is longer displayed. Bottom Text Login = example.htm Attached are bottomtextlogin.jpg which shows the characters on the left and example.htm which I used. |
I have a possible explanation for this problem, but it is just guess work. If I'm right, then just download the latest ELOG version and it will work properly again.
- You've downloaded an elog version from git, which still contained the line 12 in elogd.c: char svn_revision[] = "$Id$";
- Since you did checkout from git, the $Id$ was not substituted.
- ELOG trys to extract the version by this: rsprintf
("<center><a class=\"bottomlink\" title=\"%s\" href=\"https://midas.psi.ch/elog/\">ELOG V%s-%d</a></center>",
loc("Goto ELOG home page"), VERSION, atoi(svn_revision + 13));
- svn_revision + 13 is pointing into the void. Still I would have expected that you get a number as a result.
My advice: download again and retry.
⇄
English (auto-detected) » English
|
I have downloaded a latest version. It has displayed the new version as ELOG V2.9.2-bac715d where seems defined in GIT_REVISION as I guess. Then I set Bottom Text Login to a html file, it still shows those unwanted characters.
|
⇄
English (auto-detected) » English
Okay, why don't you just remove the unwanted characters from the html file? Because the attached file contains exactly those characters. |
|
Re: Unwanted characters showing when using Bottom Text Login to a html file, posted by Hung Dao on Fri Nov 15 23:02:03 2013
|
| Andreas Luedeke wrote: |
|
| Hung Dao wrote: |
|
| Andreas Luedeke wrote: |
|
| Hung Dao wrote: |
| When using Bottom Text Login to a html file showing some unwanted characters. Also, the ELOG Version is longer displayed. Bottom Text Login = example.htm Attached are bottomtextlogin.jpg which shows the characters on the left and example.htm which I used. |
I have a possible explanation for this problem, but it is just guess work. If I'm right, then just download the latest ELOG version and it will work properly again.
- You've downloaded an elog version from git, which still contained the line 12 in elogd.c: char svn_revision[] = "$Id$";
- Since you did checkout from git, the $Id$ was not substituted.
- ELOG trys to extract the version by this: rsprintf
("<center><a class=\"bottomlink\" title=\"%s\" href=\"https://midas.psi.ch/elog/\">ELOG V%s-%d</a></center>",
loc("Goto ELOG home page"), VERSION, atoi(svn_revision + 13));
- svn_revision + 13 is pointing into the void. Still I would have expected that you get a number as a result.
My advice: download again and retry.
⇄
English (auto-detected) » English
|
I have downloaded a latest version. It has displayed the new version as ELOG V2.9.2-bac715d where seems defined in GIT_REVISION as I guess. Then I set Bottom Text Login to a html file, it still shows those unwanted characters.
|
⇄
English (auto-detected) » English
Okay, why don't you just remove the unwanted characters from the html file? Because the attached file contains exactly those characters.
|
Yes, unwanted characters are in my file. In fact, they are not visible under some editor. So, I have found a reference from this site http://www.ventrino.com/blog/60/2008/07/three-little-characters-i%C2%BB%C2%BF-designed-to-make-your-life-hell/ about how to remove them. Basically, file's properties has to set to either ASCII or Encode as UTF-8 without BOM. Thanks. |
Crash report involving propagate and replies, posted by Stephen on Tue Nov 26 16:24:39 2013
|
Using Elog 2.9.2
Elog crashes when making 10 replies, I narrowed the crash down to the Propagate Attributes setting.
I have an attribute "Status" that can be toggled between "Open" and "Closed" and that propagates all replies. On the 10th reply the application crashed, this is repeatable 100% of the time. Without the propagate option everything works fine.
Attached is my config file parsed down.
Is there a way around this, or is there a way on reply to change the attribute of the log note you replied to from open to closed without using the propagate option? |
|