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
|
|