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 |
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. |
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 |
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 |
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 |
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. |
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 |
$long_name in Moptions, posted by Fergus Lynch on Mon Nov 20 16:23:37 2006
|
Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list.
Thanks
Fergus |
Re: Re: $long_name in Moptions, posted by Stefan Ritt on Mon Nov 20 22:20:22 2006
|
Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
Re: Re: $long_name in Moptions, posted by Fergus Lynch on Tue Nov 21 09:44:30 2006
|
Stefan Ritt wrote: |
Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
WowThat was quick, I'll implement this morning. Many thanks for introducing this, ELOG is such a good tool.
Many Thanks
Fergus |
Re: Re: $long_name in Moptions, posted by Fergus Lynch on Tue Nov 21 11:14:48 2006
|
Stefan Ritt wrote: |
Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
Hi Stefan, apologies if I am being a bit dense (!) When I download the latest windows binary it extracts to ELOG V2.6.2-1749. Where could I get revision 1758 >
Thanks in advance
Fergus |
Attributes according to users, posted by ather khan on Sat Nov 18 11:19:14 2006
|
Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.
thanks,
Ather |
Re: Attributes according to users, posted by Stefan Ritt on Sat Nov 18 17:13:22 2006
|
ather khan wrote: | Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.
|
You cannot restrict the modification if certain attributes, but you can restrict edits in general with the command
Allow edit = <name of admin>
You can also restrict the New, Delete, etc. commands to be only executable by the supervisor. |
add field type to automatically email CC, posted by Mark Bergman on Thu May 25 19:41:51 2006
|
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
------------------------------- |
Re: add field type to automatically email CC, posted by Stefan Ritt on Thu Nov 9 22:08:10 2006
|
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. |
Re: add field type to automatically email CC, posted by Arckonit on Wed Nov 15 18:50:02 2006
|
Stefan Ritt wrote: |
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. |
mmmm when i try your suggestion, it doesn't work :
error from the smtp server
Erreur lors de l'envoi d'un mél. via "172.20.0.2": Issue RCPT TO: command before DATA command
here is my configTheme = default
Comment = Logs des modification de scripts des 3 domaines
Attributes = Acteur, Action, Type, Nom du Scripts, Language, Domaine, Categorie, Commentaires,Notification
Options Action = Ajout, Modification, Suppression, Réseau, Autre, Hotfix
Options Type = Ouverture de session,Autre, deploiement
Options Language = VBS, AU3, Kix, Batch, Ksh, Perl
Options Domaine = VaubanHumanis, Humanis, Vauban
Extendable Options = Catégorie, Type, Action
Required Attributes = Acteur, Type, Lieu
Page Title = Modification Scripts - $subject
Reverse sort = 1
Quick filter = Date, Type
Suppress Email to users = 1
# Email all = someadminsuser@maildomain.com
Email all = $Notification
Options Status = 1-To Do{1}, 2-Open{2}, 3-Closed{3}, 4-Suspended{4}
you can remark the commented line
i would like to have one fixed list, so those users will be always alerted, and to be able to add and adress email in the notification attribute, but i really don't know how to do it
thx for any suggestions |
Re: add field type to automatically email CC, posted by Stefan Ritt on Wed Nov 15 19:33:17 2006
|
Arckonit wrote: | mmmm when i try your suggestion, it doesn't work :
error from the smtp server
Erreur lors de l'envoi d'un mél. via "172.20.0.2": Issue RCPT TO: command before DATA command |
You get this error if no valid receiver is specified. I tried your config file and it worked fine. You need however a recent version of elog (2.6.2-7). Probably you have to upgrade.
Arckonit wrote: | you can remark the commented line
i would like to have one fixed list, so those users will be always alerted, and to be able to add and adress email in the notification attribute, but i really don't know how to do it
thx for any suggestions |
You can do that with
Preset Notification = someone@mail.com, someoneelse@mail.com
So Notification gets preset with a pre-defined list, which you can edit before submission. |
Report printing, posted by Eric Krise on Mon Nov 13 18:10:42 2006
|
Is there a way to print a summary of all (or selected) log books on a scheduled basis, say like every morning @ 7:00 am? I would like a printed copy of our daily logs (24 hr period). Thanks Eric |
Re: Report printing, posted by Stefan Ritt on Mon Nov 13 20:22:02 2006
|
Eric Krise wrote: | Is there a way to print a summary of all (or selected) log books on a scheduled basis, say like every morning @ 7:00 am? I would like a printed copy of our daily logs (24 hr period). Thanks Eric |
You can obtain the last 24hr period with the parameter last=1. Following command will return this last day for the forum
http://midas.psi.ch/elogs/Forum/?printable=1&last=1
Now you need to set up some script which calls this once a day and then convinces the browser to print that page. But I have no idea how to perform this.
Another option is to print the xxxxxxa.log files of the elogd server directly. There is already one file per day, and the original reason for that is exactly what you ask for: You can print each day directly. Now you need a script which searched for the last day and prints that. |
|