Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 419 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 ... 418, 419, 420 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  2218   Thu Apr 26 16:43:45 2007 Question Kevin McCartykmccarty@princeton.eduRequestLinux2.6.3-1764Is there (planned) support for <A NAME> and <HR /> in ELCODE?
Hello,

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">.

(Please send me replies also by email at kmccarty AT princeton DOT edu, as I don't check this forum often.)

Thanks for writing ELOG; our group has been using it very productively on our server for the last few weeks.

best regards,

-- Kevin McCarty
  2221   Fri Apr 27 08:38:58 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.


Very good idea. The horizontal line
is already implemented via [LINE] and the anchor tag will soon follow.
  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
  2225   Mon Apr 30 20:52:51 2007 Entry Alan Stonealstone@fnal.govQuestionLinux2.6.5-1857Upgraded from 2.6.1 to 2.6.5, but cannot login now & top.html is not displayed
We followed the simple download instructions. Our existing logbook entries
are still visible. Nothing was lost or touched in our /usr/local/elog directory.
Is there some step we missed?
Alan
  2226   Mon Apr 30 21:01:49 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.5-1857Re: Upgraded from 2.6.1 to 2.6.5, but cannot login now & top.html is not displayed

Alan Stone wrote:
We followed the simple download instructions. Our existing logbook entries
are still visible. Nothing was lost or touched in our /usr/local/elog directory.
Is there some step we missed?
Alan


Have you tried to delete your cookies in the browser and try again?

The location of top.html has been changed from the ELOG root down into the loogbook directory. If you want to keep it in the original location, you have to specify the full path. See the documentation for where to put the file for "Top text".
  2227   Tue May 1 16:54:12 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinuxELOG V2.6.Re: Change default for suppressing email notification and/or targeting entries manually

Alan Stone wrote:
I would also like the option to add additional email addresses on the fly.


There is a simple way to accomplish this. Define a new attribute, let's call it "cc". Then add to your config file following statement:
Email all = $cc

In you entry form, you can now enter comma-separated email addresses in the CC filed, to which a notification will be sent.
  2236   Thu May 31 23:33:28 2007 Entry Mark Bergmanmark.bergman@uphs.upenn.eduQuestionLinuxV2.6.5-186how to supress checkboxes of all logbooks at registration?
Is there a way to suppress the listing of all logbooks on the New User Registration page? We've got 100 logbooks (one for each server, cluster node, or major software package). The long list makes it difficult for users to find the bottom of the registration page, and no user needs to subscribe for automatic e-mail notification for every logbook.

Thanks,

Mark
Goto page Previous  1, 2, 3 ... 418, 419, 420 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6