Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 38 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  2222   Fri Apr 27 08:56:10 2007 Reply Kevin McCartykmccarty@princeton.eduRequestLinux2.6.3-1764Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE?

Stefan Ritt wrote:

Kevin McCarty wrote:
I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE.


Very good idea. The horizontal line
is already implemented via [LINE] and the anchor tag will soon follow.


Wonderful, thanks!

-- Kevin McCarty
  2223   Fri Apr 27 13:06:59 2007 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.3-1764Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE?

Kevin McCarty wrote:
I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. This would be useful for long log messages in order to provide a table of contents and divide them into clear sections. If this support already exists, I'm afraid it is not obvious to me how to access it in ELCODE. If it does not yet exist, would you consider a patch for it?

As a related issue, to support <a name> usefully, it will also be necessary for ELCODE to support things like [url=#tag], which it currently converts to <a href = "http:///#tag"> instead the expected result of <a href = "#tag">.


I implemented anchor tags. You can write something like

[ANCHOR]top[/ANCHOR]

and you can then reference it either by directly entering

http://midas.psi.ch/elogs/Forum/2223#top

or by entering simply

elog:2223#top

To make your table of contents, you can put a complete URL tag like

[URL=http://midas.psi.ch/elogs/Forum/2223#top]Goto top[/URL]

or inside the same entry simply

[URL=#top]Goto top[/URL]

which will be shown as

Goto top

I have added these link again at the bottom of this entry so you can try it with this entry directly.

... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...
... empty space ...

elog:2223#top
  2306   Mon Aug 6 17:43:52 2007 Warning Steve Jonessteve.jones@freescale.comRequestAll2.6.2-1739Too many logbooks during user registration
Stefan, we require registration with elog. We have quite a number of logbooks and when someone requests a login account AND elects to register with all of the logbooks, the resulting URL is apparently too long for browsers to handle when the admins click on the link embedded in the email notification. For example, FireFox (latest ver) appears to truncate the URL *after* submission (the correct URL is there before submission).

My question: Is it possible to limit - or remove - the checkboxes that the user can select during registration? I realize that this is a browser issue but I doubt I can persuade those guys to fix FireFox.

Thanks.
  2307   Tue Aug 7 18:39:37 2007 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.6.2-1739Re: Too many logbooks during user registration

Steve Jones wrote:
Stefan, we require registration with elog. We have quite a number of logbooks and when someone requests a login account AND elects to register with all of the logbooks, the resulting URL is apparently too long for browsers to handle when the admins click on the link embedded in the email notification. For example, FireFox (latest ver) appears to truncate the URL *after* submission (the correct URL is there before submission).

My question: Is it possible to limit - or remove - the checkboxes that the user can select during registration? I realize that this is a browser issue but I doubt I can persuade those guys to fix FireFox.

Thanks.


I changed the current SVN version (#1909) to show only the list of logbooks if there are ten or less logbooks, in order not to make the URL too long. On the activation by the administrator, the list of subscribed logbooks appears as previously, but all are unchecked. So it's the task of the administrator to enable subscriptions or not.
  2316   Tue Sep 11 15:30:11 2007 Reply Steve Jonessteve.jones@freescale.comRequestAll2.6.2-1739Re: Too many logbooks during user registration

Stefan Ritt wrote:

Steve Jones wrote:
Stefan, we require registration with elog. We have quite a number of logbooks and when someone requests a login account AND elects to register with all of the logbooks, the resulting URL is apparently too long for browsers to handle when the admins click on the link embedded in the email notification. For example, FireFox (latest ver) appears to truncate the URL *after* submission (the correct URL is there before submission).

My question: Is it possible to limit - or remove - the checkboxes that the user can select during registration? I realize that this is a browser issue but I doubt I can persuade those guys to fix FireFox.

Thanks.


I changed the current SVN version (#1909) to show only the list of logbooks if there are ten or less logbooks, in order not to make the URL too long. On the activation by the administrator, the list of subscribed logbooks appears as previously, but all are unchecked. So it's the task of the administrator to enable subscriptions or not.



Quote:
So the list is shown to the one requesting the registration? Would it be possible to have an option that, when selected, simply did not list any logbooks? I can see a customer becoming confused if they did not see their logbook listed. Just turn off the selection completely. Otherwise, this will work but I fear will generate more questions as in "Why isn't logbook <blah> listed?"

Thanks!
  2317   Tue Sep 11 21:25:11 2007 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.6.2-1739Re: Too many logbooks during user registration

Steve Jones wrote:
So the list is shown to the one requesting the registration? Would it be possible to have an option that, when selected, simply did not list any logbooks? I can see a customer becoming confused if they did not see their logbook listed. Just turn off the selection completely. Otherwise, this will work but I fear will generate more questions as in "Why isn't logbook <blah> listed?"


I agree, that's inconsistent. So I removed the logbook list completely (SVN revision 1914) and added a note on the user notification that they should click 'config' to subscribe to any logbook.
  2320   Thu Oct 4 12:03:30 2007 Smile Fergus Lynchflynch@alternativenetworks.comRequest ELOG V2.6.Add date and time stamp to file upload
Hi,

Been using ELOG for a couple of years now and I am very impressed with its functionality.

I would like to request a new feature - add date and time stamp to file upload. We use ELOG (amongst other things!) as a change log and this would really allow allow more accurate records to be kept. For instance we upload router config files (to record changes)and having the exact upload date would be a big enhancement, especially when there are a lot of attachments.

Many Thanks in Advance
Fergus
  2321   Thu Oct 4 17:19:56 2007 Reply Stefan Rittstefan.ritt@psi.chRequest ELOG V2.6.Re: Add date and time stamp to file upload

Fergus Lynch wrote:
I would like to request a new feature - add date and time stamp to file upload. We use ELOG (amongst other things!) as a change log and this would really allow allow more accurate records to be kept. For instance we upload router config files (to record changes)and having the exact upload date would be a big enhancement, especially when there are a lot of attachments.


There is already a time and a date stamp. If you look in the logbook directory, you see attachments preceded with the date and time when they were submitted. You can see this date/time when you click on the attachment, such as in

http://midas.psi.ch/elogs/Config+Examples/040519_000348/elogd.cfg

where you will see it even in the URL (May 19th, 2004, 0:03:48) in the above case. I agree that this is not so obvious. If you make a proposal where this date/time should be displayed, I can easily add it.
ELOG V3.1.5-3fb85fa6