Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 319 of 808  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    6457 Entries 
Goto page Previous  1, 2, 3 ... 318, 319, 320 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  67579   Fri Oct 11 16:18:05 2013 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.9.2-2455Re: Navigation previous and next button don't work

Hung Dao wrote:

Stefan Ritt wrote:

Hung Dao wrote:
I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox.

Have you tried on this forum? 

  I have tried this forum, it worked fine. So, it should not be a browser. The only different I have logbook that I have been working on ELOG v2.6.5 and I have installed a new version v2.9.2. I just wonder any different data format (2.6.5 vs. 2.9.2) could have caused a problem.

The data format has nothing to do with the functionality of browsing buttons. Except if you have an empty logbook, or a logbook with just one entry, then of course going forwared and backward will not make any sense. 

  67581   Fri Oct 11 19:20:22 2013 Reply Hung Daohungtdao@yahoo.comBug reportWindows2.9.2-2455Re: Navigation previous and next button don't work

Stefan Ritt wrote:

Hung Dao wrote:

Stefan Ritt wrote:

Hung Dao wrote:
I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox.

Have you tried on this forum? 

  I have tried this forum, it worked fine. So, it should not be a browser. The only different I have logbook that I have been working on ELOG v2.6.5 and I have installed a new version v2.9.2. I just wonder any different data format (2.6.5 vs. 2.9.2) could have caused a problem.

The data format has nothing to do with the functionality of browsing buttons. Except if you have an empty logbook, or a logbook with just one entry, then of course going forwared and backward will not make any sense. 

I have a group includes more than one logbooks. One has about 1600 entries and another new one has 5 entries. I have tried them both. When I retested with v2.6.5, the buttons are still functional. This problem also exists on Firefox plus giving me a message "This is the first entry" "This is the last entry" when I clicked a previous button and next button respectively. I need to use v2.9.2 since it has many improvements

  67591   Mon Oct 28 11:21:19 2013 Question Alexander Nozikaltavir@gmail.comQuestionLinux2.9.2-2455Attachment file names encoding
Hello,
I am trying to move elog from old FreeBSD system to a new Ubuntu server and stuck with attachment encoding problem. The elog entries as well as attachments ашду тфьуы are mostly in koi8-r or cp1251 encoding. While it is relatively easy to configure log entries to display correctly, I still can't manage to deal with attachments. In old elog all attachments with Cyrillic file names are "not found" by elog web interface while files are present in the directory (though previous admin could have done something with the encoding).

If I am creating a new elog with default koi8-r charset, then new cyrrilic attachments are uploaded and displayed normally but after download the file name encoding is broken. Does elog do something with attachment name encoding?
  67592   Tue Oct 29 12:04:44 2013 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionLinux2.9.2-2455Re: Attachment file names encoding

Alexander Nozik wrote:
Hello,
I am trying to move elog from old FreeBSD system to a new Ubuntu server and stuck with attachment encoding problem. The elog entries as well as attachments ашду тфьуы are mostly in koi8-r or cp1251 encoding. While it is relatively easy to configure log entries to display correctly, I still can't manage to deal with attachments. In old elog all attachments with Cyrillic file names are "not found" by elog web interface while files are present in the directory (though previous admin could have done something with the encoding).

If I am creating a new elog with default koi8-r charset, then new cyrrilic attachments are uploaded and displayed normally but after download the file name encoding is broken. Does elog do something with attachment name encoding?


You should be able to figure this out:
As an administrator you can have a look what are the real file names on the file system.
With your browser you can see what are the names of the attachment. Like in this forum, the entry https://midas.psi.ch/elogs/Forum/67571 has an attachment https://midas.psi.ch/elogs/Forum/131008_181353/import.xml
If the two match you don't have an encoding but some file system problem. If they don't match, then we are one step further in solving your problem Smile
Thought, the file name in the URL has to be URL encoded (see e.g. http://www.w3schools.com/tags/ref_urlencode.asp), which is of course different from the encoding of the file system.
  67593   Wed Oct 30 10:15:13 2013 Reply Alexander Nozikaltavir@gmail.comQuestionLinux2.9.2-2455Re: Attachment file names encoding
Thank you for reply.

I am not very experienced linux user so it could be a problem with the file system. Let me just describe what I do and what I see as a result.

I created a new elog just for the testing purpose, it has "Charset = koi8-r" line in the config file. Than I post a new entry to this elog with russian text and a file with russian file name from windows (so I expect that charset is cp1251). Now I open this entry. The text is fine and the filename is fine on the page (the same russian text I expect to see), but when I try to download it, the actual file name is broken and to restore it I need koi8-r -> cp1252 transformation. The file itself is readable.
If I look in the actual logbook directory, then in the entry file the file name is readable (entry file encoding is koi8-r), but the attachment file name contains many "?" and not readable by file system.

So first my question is what happened to the file name incoding in a logbook directory, and the second one: what should I do to make attachments download as they were uploaded?

Thank you in advance.
  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.

Goto page Previous  1, 2, 3 ... 318, 319, 320 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6