ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 552 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6460 Entries

Goto page Previous 1, 2, 3 ... 551, 552, 553 ... 806, 807, 808 Next

Thu Nov 30 22:07:31 2006

Stefan Ritt wrote:

Grant Jeffcote wrote:

Thanks, we use Internet Explorer in service but I tested using Mozilla (hence above).
I'd really like to be able change the limit to more than 256 characters, is this simply a configuration parameter or a code change?

It is a code change. I increased it to 10000 chars in revision 1766, it will be contained in the next release.

Thx Stefan, I can write a book in there now! ;o))

2104

Thu Nov 30 20:49:56 2006

Grant Jeffcote wrote:

It is a code change. I increased it to 10000 chars in revision 1766, it will be contained in the next release.

2103

Thu Nov 30 16:07:54 2006

Re: Email notification (bug tracking system)

Stefan Ritt wrote:

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.

Thank you very much Stefan,
that works fine for me!

Bertram

2102

Wed Nov 29 22:44:15 2006

Stefan Ritt wrote:

Grant Jeffcote wrote:

Stefan Ritt wrote:

Grant Jeffcote wrote:

What will the configuration line be?

If you have

MOptions item = value_1, value_2

you can do a

Tooltip value_1 = text

Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?

ELOG itself has a limit of 256 characters, but that can be changed easily. I found that Mozilla Firefox only showed 70 characters and then three dots ("..."), while Internet Explorer showed all 256 characters, wrapping words if necessary. So it strongly depends on the browser.

2101

Wed Nov 29 13:42:14 2006

Grant Jeffcote wrote:

Stefan Ritt wrote:

Grant Jeffcote wrote:

What will the configuration line be?

If you have

MOptions item = value_1, value_2

you can do a

Tooltip value_1 = text

Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?

2100

Tue Nov 28 22:12:13 2006

Stefan Ritt wrote:

Grant Jeffcote wrote:

What will the configuration line be?

If you have

MOptions item = value_1, value_2

you can do a

Tooltip value_1 = text

Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?

2099

Tue Nov 28 12:50:19 2006

Re: Resubmit-as-new-entry behaviour when synchronizing/mirroring

Andreas Warburton wrote:

Thanks for any comments or insights.

This problem was introduced a couple of months ago. It is now fixed in the new version 2.6.3.

2098

Tue Nov 28 12:48:47 2006

Version 2.6.3 released today

Dear ELOG users,

ELOG version 2.6.3 has been released today. It contains all the bug fixes, security fixes and a few new features collected since the last release which was actually almost half a year ago. The changelog contains all the details.

Due to the security fixes it is recommended to upgrade from any version prior to 2.6.3. Please note that the location of all password and log files has been moved from the main elog directory to the logbook directory. This means that after upgrading you have to move your password file manually, otherwise you cannot log in any more. This modification was requested because some ELOG installations (especially ones with top groups) can now have a read-only main directory.

Stefan Ritt

Goto page Previous 1, 2, 3 ... 551, 552, 553 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6