Attachment Uploaded Time is off by one hour, posted by Edmund Hertle on Wed Sep 2 20:23:21 2015
|
If I upload an attachment the timestamp of the attachment is set to one hour in the future, as demonstrated with this test attachment being one hour in the future compared to the entry time |
Copy To Function, posted by Mike Bodine on Wed Sep 2 17:06:17 2015
|
Hi,
We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?
Thanks,
Mike
|
Copy To Function, posted by Mike Bodine on Wed Sep 2 17:06:10 2015
|
Hi,
We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?
Thanks,
Mike
|
Copy To Function, posted by Mike Bodine on Wed Sep 2 16:55:00 2015
|
Hi,
We've recently implemented the Copy To function and it works as advertised. The issue we're having is the original entry time is also copied, so if we take an old log and copy it to another log book the entry using reverse sort, preserve = 0 may not display as the newest id. It will receive the next message id, but not display in the correct order on the page. Is there an option or parameter that will force Copy To create a new entry time, so the message id will appear in the correct order?
Thanks,
Mike
|
Preset on duplicate, posted by Daniel Sajdyk on Mon Aug 31 22:35:03 2015
|
Hi.
Is there any way that "Preset on duplicate" contain ID entry from which it was duplicated?
Cheers
Daniel. |
Draft saved is treated as an entry edit, posted by Daniel Sajdyk on Fri Aug 28 21:01:42 2015
|
Hello.
In Elog i have attribute called "Zmieniano" (eng. changed) which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)".
From version V3.1.1-3f311c5 I have problem with that.
When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:
- Oryginalny wpis (eng. oryginal entry),
- Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... )
The second value is autosave time.
Is this a bug?
Regards
Daniel.
|
Re: Draft saved is treated as an entry edit, posted by Andreas Luedeke on Mon Aug 31 09:38:38 2015
|
Hi Daniel,
this is an undesired side effect of a new feature. I wouldn't call it a bug ;-)
There is no straight forward way for elog to distinguish between a "Submit" and an automatic save. Therefore the "... on edit = ..." kicks in when an entry is saved automatically.
I guess Stefan can figure out a workaround, but for the moment I would sugest that you just switch off the auto save feature -- if you want to keep your save history:
Save drafts = 0
Cheers
Andreas
Daniel Sajdyk wrote:Save drafts = 0 |
Hello.
In Elog i have attribute called "Zmieniano" (eng. changed) which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)".
From version V3.1.1-3f311c5 I have problem with that.
When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:
- Oryginalny wpis (eng. oryginal entry),
- Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... )
The second value is autosave time.
Is this a bug?
Regards
Daniel.
|
|
Re: Draft saved is treated as an entry edit, posted by Daniel Sajdyk on Mon Aug 31 13:12:09 2015
|
Hi Andreas and thank you very much for explanation ;)
So, we'll have to wait for new version which will correct this.
Cheers
Daniel.
Andreas Luedeke wrote: |
Hi Daniel,
this is an undesired side effect of a new feature. I wouldn't call it a bug ;-)
There is no straight forward way for elog to distinguish between a "Submit" and an automatic save. Therefore the "... on edit = ..." kicks in when an entry is saved automatically.
I guess Stefan can figure out a workaround, but for the moment I would sugest that you just switch off the auto save feature -- if you want to keep your save history:
Save drafts = 0
Cheers
Andreas
Daniel Sajdyk wrote:Save drafts = 0 |
Hello.
In Elog i have attribute called "Zmieniano" (eng. changed) which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)".
From version V3.1.1-3f311c5 I have problem with that.
When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:
- Oryginalny wpis (eng. oryginal entry),
- Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... )
The second value is autosave time.
Is this a bug?
Regards
Daniel.
|
|
|
Send e-mail based on a hierarchy of attributes?, posted by Phil Rubin on Mon Aug 24 20:40:14 2015
|
Is there a way to distribute e-mail based on the consideration of several attributes and values? A simple example: attributes type and category have several different values, say, routine and problem for type and hardware and software for category, but one would only like messages sent when there's a problem to different sets of hardware or software types. Thus:
Email
type routine category hardware = no message
category software = no message
type problem category hardware = a@bcd.efg, h@ijk.lmn
category software = 1@opq.rst, 2@uvw.xyz |
Re: Send e-mail based on a hierarchy of attributes?, posted by Andreas Luedeke on Wed Aug 26 09:18:17 2015
|
Yes, this can be done. See below for an example configuration.
Attributes = entrytype, category
Options entrytype = routine{1}, problem{2}
Options category = software, hardware
{1} Email category software =
{1} Email category hardware =
{2} Email category software = 1@opq.rst, 2@uvw.xyz
{2} Email category hardware = a@bcd.efg, h@ijk.lmn
Phil Rubin wrote: |
Is there a way to distribute e-mail based on the consideration of several attributes and values? A simple example: attributes type and category have several different values, say, routine and problem for type and hardware and software for category, but one would only like messages sent when there's a problem to different sets of hardware or software types. Thus:
Email
type routine category hardware = no message
category software = no message
type problem category hardware = a@bcd.efg, h@ijk.lmn
category software = 1@opq.rst, 2@uvw.xyz
|
|
Version 3.1.1 of elog has been released, posted by Stefan Ritt on Tue Aug 4 15:35:39 2015
|
Version 3.1.1, released August 4th, 2015
-
Updated CKEditor to version 4.5.1
-
Implemented "Date/Time format <attribute> = ..."
-
Implemented "Use Email Subject Edit = ..."
-
Replaced "Back" by "Delete" button
-
Fixed many issues with Draft Messages
-
CSS file is now in *addition* to the default file elog.css
-
Added LDAP documentation
-
Added "Logout to URL = ..." option
-
Added description of Apacher server authentication
|
Re: Version 3.1.1 of elog has been released, posted by Edmund Hertle on Thu Aug 20 14:23:43 2015
|
There seems to be a small problem with the new "Date/Time format <attribute>" implementation. It works great for the detailed view of a single entry:

But fails to work on the list view (same entry, the Date column is formated as it should):

Relevant config part:
Time format Time Start = %H:%M:%S
Time format Time End = %H:%M:%S
Stefan Ritt wrote: |
Version 3.1.1, released August 4th, 2015
-
Updated CKEditor to version 4.5.1
-
Implemented "Date/Time format <attribute> = ..."
-
Implemented "Use Email Subject Edit = ..."
-
Replaced "Back" by "Delete" button
-
Fixed many issues with Draft Messages
-
CSS file is now in *addition* to the default file elog.css
-
Added LDAP documentation
-
Added "Logout to URL = ..." option
-
Added description of Apacher server authentication
|
|
Re: Version 3.1.1 of elog has been released, posted by Stefan Ritt on Thu Aug 20 15:52:26 2015
|
Thanks for reportung that bug. I fixed it in revision f828049.
Edmund Hertle wrote: |
There seems to be a small problem with the new "Date/Time format <attribute>" implementation. It works great for the detailed view of a single entry:

But fails to work on the list view (same entry, the Date column is formated as it should):

Relevant config part:
Time format Time Start = %H:%M:%S
Time format Time End = %H:%M:%S
|
|