Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 281 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  1982   Wed Oct 11 16:08:04 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2-1714Re: Turn off smileys?

Yoshio Imai wrote:
Other suggestion: What about going the other way round and making this
\?)
the smiley and this
?)
the usual question in brackets? If there was a special sequence to announce the unusual case (i.e. the smiley), I think less people would complain about having unwanted conversions ...


I thought also about that, but people who are use to bulletin boards or instant messaging have the common knowledge that a ;) gives a smiley, not a \;). While it would work with the smiley button, which could insert anything, the "other" half of the people who are used to the standard smileys would complain. So I hope that ?-) is acceptable by both sides.
  1450   Thu Oct 13 08:32:20 2005 Reply Stefan Rittstefan.ritt@psi.ch Windows2.5.4Re: Trying to remove "mailto:" from the email address

Matt Kimball wrote:
We are using ver 2.5.4. As users enter new requests into the system, they would like email notifications. I have added the $user_email into a "notifications" section that we created. The email address that gets entered is "mailto:user@domain.com". Is there a way to remove the "mailto:"? Attached is my config file.


The "mailto:" is there for good reason. After you submit the entry, elogd converts the "mailto:" into
<a href="mailto:user@domain.com">user@domain.com</a>

so the browser shows the email address as a link. If you click it, the browser automatically opens your email client with the email address already in the "To:" field. The same works in the main text body. So if I put "mailto:stefan.ritt@psi.ch", it gets converted automatially to "stefan.ritt@psi.ch", a feature many people rely on.

Now from your request it looks to me like you want email notifications, so you put
Email System CareWare = ..., $user_email

In that case the "mailto:" gets automatically stripped during the email notification, so the user_email gets entered and will be used correctly for the notification.
  67210   Wed Mar 14 14:38:10 2012 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.0-2418Re: Truncation of the displayed text in Summary view of the list of entries

Olivier Callot wrote:

In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.

That's a feature

In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose. 

  67212   Wed Mar 14 15:08:17 2012 Angy Olivier Callotolivier.callot@cern.chBug reportLinux2.9.0-2418Re: Truncation of the displayed text in Summary view of the list of entries

Stefan Ritt wrote:

Olivier Callot wrote:

In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.

That's a feature

In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose. 

 Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway.

  67214   Wed Mar 14 16:04:04 2012 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.0-2418Re: Truncation of the displayed text in Summary view of the list of entries

Olivier Callot wrote:

Stefan Ritt wrote:

Olivier Callot wrote:

In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.

That's a feature

In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose. 

 Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway.

Ok, I fixed that in revision 2442. 

  68311   Thu Apr 28 22:54:08 2016 Reply Adam Fairbrotherafairbrother@sd73.bc.caBug reportLinuxV3.1.1-0767eb0Re: Trouble with Find and Conditional attributes

This may be due to how I have my config file setup

Example:

Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
 

Adam Fairbrother wrote:

I seem to be having some trouble with Find when using conditional attributes.

when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.

I am able to use the conditional options as expected when creating a new logbook.

 

I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources)

 

  68314   Fri Apr 29 20:37:04 2016 Reply Adam Fairbrotherafairbrother@sd73.bc.caBug reportLinuxV3.1.1-0767eb0Re: Trouble with Find and Conditional attributes

Uppon closer inspection, removing the option to preset the secondary attribute as a Option list dosn't do anything for the find page.

This:

Attributes = A, B
Options A = One{1}, Two{2}
{1} Options B = 1, 2
{2} Options B = 3, 4

Still fails to set attribute B to a option list on  the find page. 

Adam Fairbrother wrote:

This may be due to how I have my config file setup

Example:

Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
 

Adam Fairbrother wrote:

I seem to be having some trouble with Find when using conditional attributes.

when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.

I am able to use the conditional options as expected when creating a new logbook.

 

I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources)

 

 

  67836   Tue Mar 24 19:08:34 2015 Reply Pedro Acostaacostacespedes@gmail.com thisBug reportWindows3.0.0Re: Trouble to install ELOG V3.0.0-72a8401 in XP SP3

Maybe, nobody uses XP SP3 but i get Win32 invalid aplication error.  Not work!

Pedro Acosta wrote:

Hi,

It´s not possible to install the last version V3.0.0-72a8401 over XP SP3, the previous version works well.  For Windows Vista Home Basic SP2 work fine the last version. 

I´m not sure if this the correct site to post this.

 

Regards

Pedro Acosta

 

 

ELOG V3.1.5-3fb85fa6