| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68773
|
Tue Apr 3 09:39:07 2018 |
 | David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | 3.1.2 | Re: Create past Elog entry. | Hi Michael,
Elog purists, look away now.
There is an "official" way to do this, which is to have fields for entry date (so can be in the past), but the yymmdda.log file will be of the date and time you make the entry. This is in the offical documentation.
If you are not bothered by the ID number being out of sequence (and elog does not really mind, although it occasionally throws a hissy fit/throws its toys out of the pram, which a restart sorts out), but you are one who wants the date of the entry in the log file to also be in the past, skipping the entry date fields issue, it's perfectly do-able. So long as you can access the yymmdda.log files.
What I, and some others, do is to create a new entry now (for ease, the first entry of the day, but that's not critical), then go to the log files, and with an editor open today's file, find the entry, and edit the day, date and if necessary time; I always set the time as post 22:00, as code for an edited late entry. I also then cut-and-paste the entry into the log file for the day it should have been entered in (creating it if necessary, in linux make sure the permissions are correct, specifically the user).
If you have attachments, and want those also to reflect the date, you'll need to edit the Attachments section of the elog entry headers (format is obvious), and also rename the attachment files in the directory.
I've not tried an ID number being other than an integer, I guess it would not work. ID numbers not being in sequence with the date doesn't seem to matter. Messing with ID numbers can have a number of consequences, such as elog running away, burning CPU time etc (looking for a previous entry that does not exist), or rogue listings of a entry ID no./# 0 (looking for a later entry that does not exist).
One caveat; I use Linux, and on elog 2.9.2. Later elogs and Windows may have a different reaction to what I've written above.
Elog purists can now look again.
| Michael Hibbard wrote: |
|
Hello, Sorry if this has been addressed elsewhere, but I could not find info.
I am wanting to submit a new elog entry (that should have been) for a past date, to predate log entrys currently in my system.
I assume I must manually create a new .log file. What ID# should I assign to this entry? Should I sub-increment (i.e 33.1)? I presume the correct think to to would be to automate ID# increments in all sucessive logs with a script (python).
Please advise.
Thank you,
-Michael Hibbard
|
|
|
68774
|
Tue Apr 3 10:19:07 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 3.1.2 | Re: Create past Elog entry. | David answered the question already.
I would distinguish if this is a once-in-a-year event, where you are willing to edit the logfiles as an administrator to fix it -
or if it happens more weekly, and you want to enable the users to fix it themself.
If it happens once a year and you don't mind to do it yourself: write a little self "how-to" and do it like David suggested.
If it happens more frequent and you prefer your users to fix it themself: introduce a "when" attribute as described in elog:67712
Cheers, Andreas
PS: Changing entry IDs $@MID@$ is only for people who know exactly what they are doing. You need to change all references to the IDs as well (Reply to: attributes) and all cross references (like the one elog:67712).
| Michael Hibbard wrote: |
|
Hello, Sorry if this has been addressed elsewhere, but I could not find info.
I am wanting to submit a new elog entry (that should have been) for a past date, to predate log entrys currently in my system.
I assume I must manually create a new .log file. What ID# should I assign to this entry? Should I sub-increment (i.e 33.1)? I presume the correct think to to would be to automate ID# increments in all sucessive logs with a script (python).
Please advise.
Thank you,
-Michael Hibbard
|
|
|
68775
|
Tue Apr 3 22:34:49 2018 |
 | Michael Hibbard | michael.hibbard@cern.ch | Question | Windows | 3.1.2 | Re: Create past Elog entry. | Thank you David, Andreas. Very useful forum.
| David Pilgram wrote: |
|
Hi Michael,
Elog purists, look away now.
There is an "official" way to do this, which is to have fields for entry date (so can be in the past), but the yymmdda.log file will be of the date and time you make the entry. This is in the offical documentation.
If you are not bothered by the ID number being out of sequence (and elog does not really mind, although it occasionally throws a hissy fit/throws its toys out of the pram, which a restart sorts out), but you are one who wants the date of the entry in the log file to also be in the past, skipping the entry date fields issue, it's perfectly do-able. So long as you can access the yymmdda.log files.
What I, and some others, do is to create a new entry now (for ease, the first entry of the day, but that's not critical), then go to the log files, and with an editor open today's file, find the entry, and edit the day, date and if necessary time; I always set the time as post 22:00, as code for an edited late entry. I also then cut-and-paste the entry into the log file for the day it should have been entered in (creating it if necessary, in linux make sure the permissions are correct, specifically the user).
If you have attachments, and want those also to reflect the date, you'll need to edit the Attachments section of the elog entry headers (format is obvious), and also rename the attachment files in the directory.
I've not tried an ID number being other than an integer, I guess it would not work. ID numbers not being in sequence with the date doesn't seem to matter. Messing with ID numbers can have a number of consequences, such as elog running away, burning CPU time etc (looking for a previous entry that does not exist), or rogue listings of a entry ID no./# 0 (looking for a later entry that does not exist).
One caveat; I use Linux, and on elog 2.9.2. Later elogs and Windows may have a different reaction to what I've written above.
Elog purists can now look again.
| Michael Hibbard wrote: |
|
Hello, Sorry if this has been addressed elsewhere, but I could not find info.
I am wanting to submit a new elog entry (that should have been) for a past date, to predate log entrys currently in my system.
I assume I must manually create a new .log file. What ID# should I assign to this entry? Should I sub-increment (i.e 33.1)? I presume the correct think to to would be to automate ID# increments in all sucessive logs with a script (python).
Please advise.
Thank you,
-Michael Hibbard
|
|
|
|
68778
|
Wed Apr 4 19:56:48 2018 |
 | Andrea Mazzolari | andrea.mazzolari@gmail.com | Question | Linux | 3.1.3 | problem with chkeditor | Hi All,
I just installed elog latest version. I can see that my chkeditor (HTML encoding) is pretty simplified with respect to the version i can see there. Why this ? For example, it does not offer the possibility to upload images.
Could you please help me ?
Thank you
Andrea
|
|
68780
|
Wed Apr 11 11:55:47 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: problem with chkeditor | Can you post a picture here?
| Andrea Mazzolari wrote: |
|
Hi All,
I just installed elog latest version. I can see that my chkeditor (HTML encoding) is pretty simplified with respect to the version i can see there. Why this ? For example, it does not offer the possibility to upload images.
Could you please help me ?
Thank you
Andrea
|
|
|
68784
|
Sat Apr 14 15:11:31 2018 |
| Andrea Mazzolari | andrea.mazzolari@gmail.com | Question | Linux | 3.1.3 | Re: problem with chkeditor | If i try to upload an image here, i got the error "Image Source URL Is Missing"...
can you help me further ?
Best regards,
Andrea
| Stefan Ritt wrote: |
|
Can you post a picture here?
| Andrea Mazzolari wrote: |
|
Hi All,
I just installed elog latest version. I can see that my chkeditor (HTML encoding) is pretty simplified with respect to the version i can see there. Why this ? For example, it does not offer the possibility to upload images.
Could you please help me ?
Thank you
Andrea
|
|
|
|
68787
|
Mon Apr 16 17:27:35 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.1.3 | Re: problem with chkeditor | Yes, I can help with that: you've tried to put the picture into the text body. Try to make it a normal attachment, that'll work always.
| Andrea Mazzolari wrote: |
|
If i try to upload an image here, i got the error "Image Source URL Is Missing"...
can you help me further ?
Best regards,
Andrea
| Stefan Ritt wrote: |
|
Can you post a picture here?
| Andrea Mazzolari wrote: |
|
Hi All,
I just installed elog latest version. I can see that my chkeditor (HTML encoding) is pretty simplified with respect to the version i can see there. Why this ? For example, it does not offer the possibility to upload images.
Could you please help me ?
Thank you
Andrea
|
|
|
|
|
68788
|
Wed Apr 18 12:07:50 2018 |
| Stefan Werler | stefan.werler@ah-senden.de | Question | Windows | 3.1.1 | Email Config | Hi,
I´m new in ELOG,
Can u explain me how i config the Mailing?
in my Configuration i do have not the ability to set an Email Host/Server. or i didn´t find it....
I have to use ELOG as ticket system, is it possible to send an email automatically after expiration of a period?
|
| Attachment 1: config.txt
|
Theme = default
CSS = tiny.css
Display mode = summary
Suppress default = 3
Self register = 2
Entries per page = 100
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1
Summary lines = 1
Display Email recipients = 0
Comment = AH-Senden Ticketsystem
List Display = ID, Author, Auftraggeber, Kategorie, Arbeitsbeschreibung, Standort, Rechnername, Priorität, Status, erstellt am, Fertigstellung bis, fertiggestellt am
Thread Display = $Auftraggeber $Standort, $Arbeitsbeschreibung, $erstellt am, $Fertigstellung bis, $fertiggestellt am,
#Start Page = ?Status=2-offen&mode=threaded&sort=Standort
#Start Page = ?wpwd=1&mode=threaded&Status=1-To Do&sort=Standort
Date Format = %A, %B %d, %Y
Time Format = %A, %B %d, %Y, %H:%M
Message Height = 6
Attributes = Auftraggeber, Kategorie, Standort, Rechnername, Priorität, Status, erstellt am, in Bearbeitung seit, warten auf Freigabe seit, Fertigstellung bis, fertiggestellt am, fertiggestellt durch, Arbeitsbeschreibung, Author
Type To Do = Time
Type Date Entered = time
Type Date Closed = time
Options Kategorie = Netzwerk, TK-Anlage, Internet, SAN, ELO, Zeiterfassung, Exchange,Domäne, W-LAN DHCP, DHCP, Backup
Options Priorität = 1-sehr hoch, 2-hoch, 3-mittel, 4-niedrig, 99-alt,
Options Status = 1-To Do{1}, 2-offen{2}, 3-fertiggestellt{3}, 4-in Bearbeitung seit{4}, 5-warten auf Freigabe{5}
{1} Preset To Do = $Date
{2} Preset erstellt am = $Date
{3} Preset fertiggestellt am = $Date
{4} Preset in Bearbeitung seit = $Date
{5} Preset warten auf Freigabe seit =$Date
Options Standort = Geilenkirchen, Kerpen, Mönchengladbach, Kaarst, sonstige, alle
Extendable options = Standort, Kategorie, Priorität
Page Title = Ticketsystem Senden - $subject
Option Author = Filled In Automatically
Subst Author = $long_name
#Menu Commands = Back, New, Edit, Delete, Reply, Find, Select, Copy to, Move to,
Reverse sort = 1
Quick Filter = Auftraggeber, Standort, Status, Fertigstellung bis
Subst on reply subject = Re: $Arbeitsbeschreibung
Thread display = $subject, posted by $author on $Entry time
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author
Quick filter = Date, Category, Status
|
|