Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 414 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  2027   Tue Oct 31 22:07:06 2006 Reply Steve Jonessteve.jones@freescale.comQuestionLinux2.6.2-1739Re: calling a shell in the Options tag

Alexandre Lindote wrote:
Hi,

is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
I need to have something like this:

Options Update of = $shell(/home/alex/zeplin3/elog/z3elog-mirror/documents/ext_docs.sh MinGen)

the script returns a line with comma separated values...

Thanks

Alex


Steve Jones wrote:

Alex, have you tried it? Novel idea!

  2029   Wed Nov 1 09:53:05 2006 Reply Alexandre Lindotealex@lipc.fis.uc.ptQuestionLinux2.6.2-1739Re: calling a shell in the Options tag

Steve Jones wrote:

Alexandre Lindote wrote:
Hi,

is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
I need to have something like this:

Options Update of = $shell(/home/alex/zeplin3/elog/z3elog-mirror/documents/ext_docs.sh MinGen)

the script returns a line with comma separated values...

Thanks

Alex


Steve Jones wrote:

Alex, have you tried it? Novel idea!




Yes, I have. It doesn't seem to... Frown
I just get one option, which is the shell line itself.
Something like:

--- Please select ---
$shell(/home/alex/zeplin3/elog/z3elog-mirror/documents/ext_docs.sh MinGen)

Cheers

Alex
  2056   Thu Nov 9 20:59:01 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2-1739Re: calling a shell in the Options tag

Alexandre Lindote wrote:
Hi,

is it possible to run a shell script in an "Options" tag, as it is with the "Preset", "Subst", and so on?
I need to have something like this:

Options Update of = $shell(/home/alex/zeplin3/elog/z3elog-mirror/documents/ext_docs.sh MinGen)

the script returns a line with comma separated values...

Thanks

Alex


Interesting idea, but substitutions only work for config setting where the documentation explicitly states so. The complete list comes here:

  • Preset <attibute>
  • Preset on reply <attribute>
  • Preset on duplicate <attribute>
  • Subst <attribute>
  • Subst on reply <attribute>
  • Subst on edit <attribute>
  • Change <attribute>
  • Email <attribute> <value>
  • Use email from
  • Use Email heading
  • Use Email subject
  • Bottom text
  • Top text
  • Edit page title
  • Prepend on edit
  • Append on edit
  • Append on reply
  • Quote on reply
  • Preset text
  • Page title
  • RSS title
  • List page title

Doing shell execution for all configuration settings would slow down the server too much.
  2057   Thu Nov 9 21:03:03 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.2-1699Re: ELCode

Alexandre Lindote wrote:

Alexandre Lindote wrote:
Hi,

can you think of any obvious reason why the ELCode would not work in the logbooks I set up?


Ok, I think I found the problem... For some reason the elcode.js file was only in /usr/local/elog/scripts, but it was supposed to be in
/usr/local/elog/themes/default/ as well.
Creating a symlink between the two solved that problem. I can now do most things with the ELCode, but inserting images is still failing. I get this message from the firefox javascript console:

text.value has no properties (line 32 of elcode.js)

Any thoughts?

Alex


That's really strange. In the forum (http://midas.psi.ch/elogs/Forum), I have the elcode.js only in /usr/local/elog/scripts, and it works as you can try out yourself. Getting your javascript error might indicate that you have an old version of elcode.js combined with a newer executable of elogd. Try to update it.
  2059   Thu Nov 9 22:08:10 2006 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.1Re: add field type to automatically email CC

Mark Bergman wrote:
I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.

I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.


For example (snippet of fictional elogd.cfg):

-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
-------------------------------


Just do the following:
Attributes = Author, Category, Notification list
Email all = $Notification list

Whenever you enter a new entry, you put a list of email addresses into the Notification list, which is then used for sending email addresses. This list also stays there in replies or edits.
  2060   Thu Nov 9 22:40:06 2006 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.1Re: suggestion for "new user registration" page

Mark Bergman wrote:
Suggestions for improving the registration page:

Put a "submit" button after the password entry.

Possibly supress the local "bottom text", or allow the specification of a different file for the registration page.

After the user has registered, then show a page allowing them to subscribe for e-mail notifcation. That page should be organized the same way as the main page, with groups. Users should be allowed to subscribe to entire groups, or to expand each group to select or unsubscribe from individual logbooks.

Thanks,

Mark


I put the "save" button below the password entry and removed the "bottom text", I hope this helps a bit.
  2061   Thu Nov 9 22:53:27 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1-1622Re: Email notification (bug tracking system)

Bertram Metz wrote:
Hello,

I'd like to use ELOG like a bug tracking system. I've created an attribute with the name AssignedTo. The attribute type is set to userlist. The value of AssignedTo is set to the full name of the selected user. There is no simple relationship between the full name and the email address on our system. Is it possible to get the email address of a user from the full name?

Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Options Category = Bug Report{1}, Observation{2}, Other{3}
Type AssignedTo = userlist
Show Attributes = Author, Category, Hardware, Software, Subject, Keywords
{1} Show Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Required Attributes = Author, Hardware, Software, Category
Options Status = new, open, confirmed, closed
;the following line does not work, since $AssinedTo contains the full name of the user
Email Category Bug Report = $AssignedTo@company.com

Kind regards,
Bertram


I implemented the attribute type useremail for you. This can be used like:
Attributes = Author, Catorory, AssignedTo
Type AssignedTo = useremail
Email Category Bug Report = $AssignedTo

You will see only the email address of the people in the list, but since the email address usually contains the name this might be enough. A different system would have been too difficult to implement. The new feature is contained in SVN revision 1754.
  2063   Thu Nov 9 23:04:32 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1Re: Is it possible to require certain attributes for specific users (guests)?
> First of all, thanks for writing and maintaining eLog.
> 
> I've been using it for a few years, but I'm now introducing it in an environment that may have a lot of "Guest"
> accounts.
> 
> I'd like to have two "Required Attributes" when a guest enters a new entry; their name and e-mail address. These
> fields don't need to be required for registered accounts, since that information is available already.
> 
> Is there any way to have conditional statements act on the value of $short_name?
> 
> Thanks,
> 
> Mark

Actually there is one possibility:

Preset Author = $long_name
Required Attributes = Author

This will force the author to be supplied. If one is logged in, the login name will be put into the author field. If
there is guest access, the field will contain "anonymous", so hopefully each guest will change that to the real name...
ELOG V3.1.5-3fb85fa6