Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 569 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6457 Entries 
Goto page Previous  1, 2, 3 ... 568, 569, 570 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject
  66735   Tue Mar 9 00:48:28 2010 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionWindows2.6.1-1642Re: Wrong author when replying a reply
Just to say that this bug was fixed some time ago - I don't remember when (a senior moment).  
I know because I reported it to Stefan (along with the rest of the universe), as it was appearing 
on this forum when it was running on that particular SVN version. 

If you update to the latest version of elog, all will be fine.

David.
(helping Stefan, since I usually give him such a hard time).
  66742   Thu Mar 11 15:38:32 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.1-1642Re: Wrong author when replying a reply

Mads Jessen wrote:

When replying on a reply, the author is set to the author on the original reply? Othervice it workes great!

part of code:
...
Preset Author = $long_name
Locked Attributes = Author
Subst on reply author = $long_name
...

I use:

Preset Author = $long_name
Preset on reply Author = $long_name
 
  1643   Mon Jan 30 16:26:08 2006 Warning T. Ribbrockemgaron@gmx.netBug reportLinux2.6.1-1637Numbered lists get closed by </ul>
I just ran into the following problem (and was able to reproduce it in the "demo" logbook on this site):

  • Create a new entry
  • Create a numbered list:
    [LIST=1]
[*] 1st entry
[*] 2nd entry
[/LIST]
  • In the resulting HTML code, the closing statement of that list translates to </ul> instead of </ol>, causing the list to remain open and all following text to be intented by the list indentation. This gets worse when several such lists are used in one document. I'll include an example below.

Numbered list follows:

  1. one
  2. two
  3. three

This text is indented, as the list was not closed properly.

  1. four
  2. five
  3. six

And now we have double indention...
  1659   Tue Feb 7 12:58:10 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.1-1637Re: Numbered lists get closed by </ul>

T. Ribbrock wrote:
I just ran into the following problem (and was able to reproduce it in the "demo" logbook on this site):

  • Create a new entry
  • Create a numbered list:
    [LIST=1]
[*] 1st entry
[*] 2nd entry
[/LIST]
  • In the resulting HTML code, the closing statement of that list translates to </ul> instead of </ol>, causing the list to remain open and all following text to be intented by the list indentation. This gets worse when several such lists are used in one document. I'll include an example below.

Numbered list follows:

  1. one
  2. two
  3. three

This text is indented, as the list was not closed properly.

  1. four
  2. five
  3. six

And now we have double indention...


I can't see any double indention there...

But seriously Wink I fixed that problem and updated this elog server already. It's in SVN revison 1653. The code now correctly chooses the proper </ul> or </ol>. What will not work however are nested lists, like an ordered list inside an unordere list, but that's anyhow very uncommon.
  1668   Thu Feb 9 00:37:29 2006 Entry Alan Stonealstone@fnal.govQuestionLinux2.6.1-1622menu commands - user list does not match config list
I am attempting to configure the Elog for use at the CMS Remote Operations Center
at Fermilab. I included the following option:

Menu commands = List, New, Reply, Duplicate, Find, Last day, Config, Admin, Login, Logout, Help

but the available list (after restarting the elog daemon) gives me:

CMS ROC Logbook, Page 1 of 1 Logged in as "Alan Stone" ELOG Home
New | Find | Select | CSV Import | Config | Logout | Help

Did I miss a step in the syntax instructions?

Thanks, Alan
  1669   Thu Feb 9 09:04:05 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1-1622Re: menu commands - user list does not match config list

Alan Stone wrote:
I am attempting to configure the Elog for use at the CMS Remote Operations Center
at Fermilab. I included the following option:

Menu commands = List, New, Reply, Duplicate, Find, Last day, Config, Admin, Login, Logout, Help

but the available list (after restarting the elog daemon) gives me:

CMS ROC Logbook, Page 1 of 1 Logged in as "Alan Stone" ELOG Home
New | Find | Select | CSV Import | Config | Logout | Help

Did I miss a step in the syntax instructions?


Yap. There are two menus, one for the listing page which contains only line per entry, and one for the individual entry page. You changed the one for the individual entry page, which you will see when you slick on any entry. To change the listing page manu, do a List Menu commands = ...
  1739   Wed Mar 1 19:51:05 2006 Warning Alexandre Gauthiersupernaut@underwares.orgBug reportLinux2.6.1-1622Inline images URL not working
Hello

I'm running elog on the blackdog embedded device so I can carry it around while doing my consultant work.

Whenever I try to insert an inline picture by using the 
elog: /1
paths with ELCode, the link becomes "logbookname2/1" (Where logbookname is the name of my logbook) and hence, doesn't work. I recall that it worked once. The image did not display, but the URL seemed correct...

Any ideas?

EDIT: i inserted a space in the elog URL above because regardless of the code brackets, it would still get interpreted.
  1741   Thu Mar 2 07:15:27 2006 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.6.1-1622Re: Inline images URL not working

Alexandre Gauthier wrote:
Whenever I try to insert an inline picture by using the 
elog:1741/1
paths with ELCode, the link becomes "logbookname2/1" (Where logbookname is the name of my logbook) and hence, doesn't work. I recall that it worked once. The image did not display, but the URL seemed correct...


The problem has been fixed in version 2.6.1-3, so just upgrade.


Alexandre Gauthier wrote:
EDIT: i inserted a space in the elog URL above because regardless of the code brackets, it would still get interpreted.


You have to put a "\" in front of everything which should not get converted into a link, so elog:1741/1 does not get interpreted.
Goto page Previous  1, 2, 3 ... 568, 569, 570 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6