Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 166 of 238  Not logged in ELOG logo
icon7.gif   Group definition under top group, posted by Exaos Lee on Sat Jan 13 17:47:45 2007 
Hi, I think, if we can put the "Group xxx = xxx" under some "global xxxx" sections, the configure file will be more clean. Don't you think so? In fact, if the "Group XXX" sections are put under "global XXX" section, the "Top Group XXX" can be ignored. I also found that some options (e.g. "Logbook dir =") under "global" don't work under "global XXX".
Maybe the configure file can be defined more flexible, such as this way:
[global]
Port = 8080
Top configuration = yes

[global Group1]
Group config = group1.cfg

[global Group2]
Group config = group2.cfg
The "group1.cfg" looks like this:
[global]
Top configuration = no
Password file = group1.pwd
Group Linux PCs = Red Hat, Debian, Gentoo
Group Windows PCs = 98, ME, XP, Vista
Group Vista = Home, Pro, Media Center

[Red Hat]
...
icon2.gif   Chinese language files updated, posted by Exaos Lee on Wed Jan 10 22:54:56 2007 eloglang-zh_CN.tgz
As the attachment.
Sorry for no update long time.
icon5.gif   Preset reply date to nothing, posted by herman on Mon Dec 11 18:02:12 2006 
How do I preset the reply date to an empty box(es)?

In 2.5.x it worked as

Preset on reply Plan Date = ""

gave me an empty date, which is what I wanted. Now in 2.6.3 I get some date in there (...1969) and have to
manually set it to empty again ?

Thanks
    icon2.gif   Re: Preset reply date to nothing, posted by Stefan Ritt on Tue Dec 12 15:45:48 2006 
> How do I preset the reply date to an empty box(es)?
> 
> In 2.5.x it worked as
> 
> Preset on reply Plan Date = ""
> 
> gave me an empty date, which is what I wanted. Now in 2.6.3 I get some date in there (...1969) and have to
> manually set it to empty again ?
> 
> Thanks

I fixed that in SVN revision 1777 again, so it will be included in the next release.
icon5.gif   Email notification (bug tracking system), posted by Bertram Metz on Fri May 5 14:49:19 2006 
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
    icon2.gif   Re: Email notification (bug tracking system), posted by Stefan Ritt on Thu Nov 9 22:53:27 2006 

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.
       icon7.gif   Re: Email notification (bug tracking system), posted by Bertram Metz on Thu Nov 30 16:07:54 2006 

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
icon5.gif   Resubmit-as-new-entry behaviour when synchronizing/mirroring, posted by Andreas Warburton on Fri Nov 24 23:08:33 2006 
Hello,

I am running two ELOG installations: one on my Windows laptop; the other on a Debian linux web server. I have mirroring set up between the two installations. This has worked well for over a year. I am hoping that someone can help me regarding the following odd behaviour.

1. I edit (create) an entry on my Windows laptop. This entry gets mirrored or synchronized to the Linux machine.

2. I can view the entry fine both on the Windows side and on the Linux side.

3. I then edit the entry on the Linux side. After saving, the revised entry is visible on the Linux side.

4. I then have the same entry number available on both installations, but the two have different content due to my edit.

5. If I then synchronize, the original (unedited) entry is preserved along with the new entry, so both the Windows and Linux installations now have TWO entries each, representing the unedited and edited versions. The time stamps are identical, but the edited version is given a new ID number.

As a check, I explicitly added the line "Resubmit default = 0", which I know refers to editing and not synchronization, to my config file. The weird thing is that the synchronize/mirror operation seems to be acting with a "Resubmit default = 2" kind of behaviour.

Has anyone observed this happening?

Thanks for any comments or insights.

Cheers,
Andreas
    icon2.gif   Re: Resubmit-as-new-entry behaviour when synchronizing/mirroring, posted by Stefan Ritt on Tue Nov 28 12:50:19 2006 

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.
icon3.gif   Version 2.6.3 released today, posted by Stefan Ritt on Tue Nov 28 12:48:47 2006 
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
icon5.gif   How to do a preset on MOptions attributes ?, posted by Stephane LE on Fri Nov 24 11:01:22 2006 
Hi,

I'm new to elog and I was wondering if it is possible to do some presets on MOptions attributes when displaying a new form ? I've read the elogd config page but couldn't find how to do it.

Thanks for your help,

stephane
    icon2.gif   Re: How to do a preset on MOptions attributes ?, posted by Stephane LE on Fri Nov 24 14:40:42 2006 
easy...

Preset MyAttribute = choice1 | choice2 | choice3
icon7.gif   Securing Elog with SSL and Apache, posted by damon nettles on Fri Nov 26 17:13:27 2004 
there is a guide on the contributions logbook at

elog:Contributions/11

for securing Elog using SSL and Apache.
    icon2.gif   Re: Securing Elog with SSL and Apache, posted by Rob Mahurin on Wed Nov 22 02:55:48 2006 
Hi,

I am an apache ignoramus who has been trying to follow these instructions on a Debian 3.1 box.  I got hung up for
the following reason.  I had to explicitly enable some apache features, which was a simple matter of making the
following symlinks in /etc/apache2/mods-enabled: 

	proxy.conf -> ../mods-available/proxy.conf
	proxy.load -> ../mods-available/proxy.load
	rewrite.load -> ../mods-available/rewrite.load
	headers.load -> ../mods-available/headers.load
	ssl.conf -> ../mods-available/ssl.conf
	ssl.load -> ../mods-available/ssl.load

Easy enough.  The default proxy.conf has sensible-looking warnings about not running your server as an open proxy.
 However, I wasn't able to tweak it to encrypted port forwarding from :443 to :8079.

What I've done that works is to add a local proxy section to the /etc/apache2/conf.d/elogredirect.conf by Damon
Nettles:

	<VirtualHost *:443>
		### ... everything else

		<Proxy *>
			Allow from all
		</Proxy>
	</VirtualHost>

I think, since this is in a subsection, that it only affects that virtual host.  But it'd be nice if someone who
actually understands this language would reassure me that I'm not setting myself up for some security hole.  At
any rate it took me long enough to figure this out that I thought I'd post a note in public, and this seems like
the forum to do so.

Thanks.

Rob
ELOG V3.1.5-3fb85fa6