Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 349 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6456 Entries 
Goto page Previous  1, 2, 3 ... 348, 349, 350 ... 805, 806, 807   Next  
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  67623   Fri Nov 15 23:02:03 2013 Reply Hung Daohungtdao@yahoo.comQuestionWindows2.9.2Re: Unwanted characters showing when using Bottom Text Login to a html file

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.

  67624   Tue Nov 26 00:06:02 2013 Question Tom Ctcheek@tulane.eduQuestionLinux2.9.2-2455Problem with space in name of eLog not seeing %20 and "+"

My elog is named "Whatever Elog" so the URL generated is /Whatever+Elog . This works fine but when in the interface certain buttons generate this URL : /Whatever%20Elog  ...this URL fails.  It seems that elog does not recognize these ( + and %20 ) as the same which I believe they should be as part of HTTP request.

  67625   Tue Nov 26 08:17:34 2013 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.9.2-2455Re: Problem with space in name of eLog not seeing %20 and "+"

Tom C wrote:

My elog is named "Whatever Elog" so the URL generated is /Whatever+Elog . This works fine but when in the interface certain buttons generate this URL : /Whatever%20Elog  ...this URL fails.  It seems that elog does not recognize these ( + and %20 ) as the same which I believe they should be as part of HTTP request.

Can you be a bit more specific which buttons you mean? The demo logbook https://midas.psi.ch/elogs/Linux+Demo/ has also a space and I cannot see any problem there.

  67626   Tue Nov 26 11:25:48 2013 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2455Re: Problem with space in name of eLog not seeing %20 and "+"

Stefan Ritt wrote:

Tom C wrote:

My elog is named "Whatever Elog" so the URL generated is /Whatever+Elog . This works fine but when in the interface certain buttons generate this URL : /Whatever%20Elog  ...this URL fails.  It seems that elog does not recognize these ( + and %20 ) as the same which I believe they should be as part of HTTP request.

Can you be a bit more specific which buttons you mean? The demo logbook https://midas.psi.ch/elogs/Linux+Demo/ has also a space and I cannot see any problem there.

 Years ago I had a similar issue, although I cannot remember the exact details now.  The consequence is that I don't leave any spaces in the log book names.  However, I did find that '&' was fine, and the ampersand and %26 are interchangeable in a logbook page, so one logbook is ECP&SIW, and using ampersand or '%26' work interchangably when making llinks from other logbooks to ECP&SIW  (that is elog:ECP&SIW or elog:ECP%26SIW work equally well)..    This is not true of elog.cfg, where only the actual character should be used.  This may be true for some other urlencoded characters.

It may be of note that %20 and '+' are not the same urlencode and character - %20 is a space, '+' is %2B, and a brief bit of playing around shows that elog is not so tolerant of those characters as it is with & and %26, and I crashed mine several times but I was only playing, nothing serious was lost.

  67627   Tue Nov 26 11:28:39 2013 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.9.2-2455Re: Problem with space in name of eLog not seeing %20 and "+"

David Pilgram wrote:

Stefan Ritt wrote:

Tom C wrote:

My elog is named "Whatever Elog" so the URL generated is /Whatever+Elog . This works fine but when in the interface certain buttons generate this URL : /Whatever%20Elog  ...this URL fails.  It seems that elog does not recognize these ( + and %20 ) as the same which I believe they should be as part of HTTP request.

Can you be a bit more specific which buttons you mean? The demo logbook https://midas.psi.ch/elogs/Linux+Demo/ has also a space and I cannot see any problem there.

 Years ago I had a similar issue, although I cannot remember the exact details now.  The consequence is that I don't leave any spaces in the log book names.  However, I did find that '&' was fine, and the ampersand and %26 are interchangeable in a logbook page, so one logbook is ECP&SIW, and using ampersand or '%26' work interchangably when making llinks from other logbooks to ECP&SIW  (that is elog:ECP&SIW or elog:ECP%26SIW work equally well)..    This is not true of elog.cfg, where only the actual character should be used.  This may be true for some other urlencoded characters.

It may be of note that %20 and '+' are not the same urlencode and character - %20 is a space, '+' is %2B, and a brief bit of playing around shows that elog is not so tolerant of those characters as it is with & and %26, and I crashed mine several times but I was only playing, nothing serious was lost.

 Having written the above and posted it, I see the links for ECP&SIW I wrote here don't work the same as in my local logbook.  I did check!  Result is treat the above posting with caution.  Although this is not the first time when something works fine on my local logbook but not here on the Mother of all elogs.  Different flavour of linux?

  67635   Thu Dec 12 15:10:43 2013 Question Paulo Moragapnmoraga@gmail.comQuestionWindowsV2.9.2-245Multiple tab

Hi noob question I was looking for a config but i cant make it, how to i make multitab logbook like this page?

 

Like in Discussion there are forum,config examples,contribution and vulnerabilities under it

 

Thanks

 

Attachment 1: multitab.JPG
multitab.JPG
  67636   Thu Dec 12 16:03:07 2013 Reply Paulo Moragapnmoraga@gmail.comQuestionWindowsV2.9.2-245Re: Multiple tab

Paulo Moraga wrote:

Hi noob question I was looking for a config but i cant make it, how to i make multitab logbook like this page?

 

Like in Discussion there are forum,config examples,contribution and vulnerabilities under it

 

Thanks

 

 NVM found it Thanks

  67637   Sat Dec 14 00:22:52 2013 Question Ryan Blakesleerb@blakesys.netQuestionLinux2.9.2How to property install?

 Hello,

I have followed the very simple steps on the Download page for checking out and compiling from GIT.  That works perfect and there is no issue.  

The problem I have is-- it is not clear to me where to put the 'elog' dir that I have after I 'make' and 'make install'.  Or, is there an installer script afterwards that I run? I'm installing on Debian 7 and trying to upgrade from 2.5.2 (which was installed using apt-get.)

Goto page Previous  1, 2, 3 ... 348, 349, 350 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6