ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67584
|
Tue Oct 15 14:14:07 2013 |
 | David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | 2.9.2 | Re: Error: Attribute <date> not supplied. |
| Barend wrote: |
|
Stefan/Andreas,
When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."
The configuration file uses:
Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.
As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.
But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.
Is this a bug -or- do I have to change the configuration?
Thanks & regards, Barend
|
Hi Barend,
I can reproduce your point.
I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line. True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.
Another way is if you *preview* your entry, you can then submit it and that works. This seems to work by bring up a different page where you can edit all those Fixed Attributes. (I'm not sure that Preview is meant to do that, but it does and it's a work-around).
Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way. But I see that you don't want the opportunity for these to be changed.
I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).
So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination. |
|
67583
|
Mon Oct 14 12:08:16 2013 |
 | Barend | office@amtc2.com | Question | Windows | 2.9.2 | Error: Attribute <date> not supplied. | Stefan/Andreas,
When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."
The configuration file uses:
Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.
As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.
But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.
Is this a bug -or- do I have to change the configuration?
Thanks & regards, Barend |
|
67582
|
Sun Oct 13 16:32:05 2013 |
| Barend | office@amtc2.com | Bug report | Windows | 2.9.2 | Re: Importing XML/CSV |
| Andreas Luedeke wrote: |
|
| Barend wrote: |
|
Hi Stefan,
I'm experiencing problems importing XML (.csv is not working at all for me).
My logbook contains 3 date-attributes besides the system DATE (entry time), date-format is defined as %d %b %y.
The XML file hold the date format "DD.MM.YYYY"
- During "preview" I see that all entries are listed.
- During the import I get the "wrong date format" error.
- When I review the Summary, I see that only the first XML entry (all 3 date-attributes hold a date) was imported.
- When I try to re-import the XML from the second entry (after removing the 1st entry from XML - this second entry hold NO date-value on one of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
- When I try to re-import the XML from the modified second entry (after removing the 1st entry from XML - this second entry holds date-value on all of the date-attributes) the elogd.exe crashes and I get the "Service Temporarily Unavailable" error page.
Any suggestion what could be wrong? Is it the missing date-value?
|
Can you post your elog configuration file (elog.cfg)?
⇄
Detect language » English
|
Hi Andreas,
I had to filter-out some other logbook. Please find attached the configuration section for the affected logbook "UMOWY".
Looking forward to your review.
Regards, Barend |
| Attachment 1: umowy.cfg
|
[UMOWY]
Time format = %d %b %y - %H:%M
Date format = %d %b %y
Display mode = summary
Comment = Umowy
Menu commands = List, New, Edit, Reply, Delete, Duplicate, Find, Config, Logout, Help, Import
List Menu commands = List, New, Select, Find, Config, Logout, Help, Import
Attributes = Data dekretacji, Numer rejestru, Numer umowy, Nazwa dokumentu, Przedmiot umowy, Kontrahent, Data zawarcia, Data konca, Dzial, Status, Aneksy, Opis
List display = Data dekretacji, Numer rejestru, Numer umowy, Nazwa dokumentu, Przedmiot umowy, Kontrahent, Data zawarcia, Data konca, Dzial, Status, Aneksy, Opis
Style STATUS Nieaktualna = background-color:#FFC0CB
Style STATUS Aktualna = background-color:lightgreen
Preserve IDs = 0
Preset Numer rejestru = XXX/%Y/###
Quick filter = Numer rejestru, Numer umowy
Extendable options = Author, Carrier
Options Status = Aktualna, Nieaktualna
Options Aneksy = boolean
Options Okres obowiazywania = 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
Options Dzial = DA, DOP, DP, DTL, DTL BZG, DTL GDN, DTL KTW, DTL POZ, DTL WAW, DTL WRO, L&F
Options Przedmiot umowy = Obsluga, Najem, Media, Leasing
Format Numer rejestru = 0, attribname, attribvalue, 10, 10
Format Numer umowy = 0, attribname, attribvalue, 10, 20
Format Opis = 0, attribname, attribvalue, 1000, 1000
Comment Aneksy = Jezeli sa to zaznacz: X
Type Date of change = datetime
Type Data zawarcia = date
Type Data konca = date
Type Data dekretacji = date
Thread display = $Carrier $Name of Doc $Version No $Date of change entered by $author on $Entry time
Page Title = Umowy Logbook - $Subject
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 0
Subst on reply subject = Re: $Subject
Suppress Email to users = 1
Theme = digilog
CSS = digilog.css
Title image = <img style="width:91;height:21;border:0" src="digilog.png" alt="eLOG" title="eLOG">
Top text = <img src="aerocol-transparent.png" style="height:46;width:146;border=0" alt="AeroSoft Systems Inc." title="AeroSoft Systems Inc."> <span class="asiTitle">DigiLOG™ Electronic Event Log</span>
Allowed encoding = 1
Suppress default = 3
Suppress Email on edit = 3
Fonts = Verdana, Geneva, Arial, Helvetica, sans-serif
Show attachments = 0
Preview attachments = 0
Append on reply = \n\nAdded $date by $long_name\n\n
Preset on reply Author = $long_name
Preset on reply Number= $Number
Subst on edit Author = $long_name
Fixed Attributes Edit = Author
Allow Delete = admin
Show text = 1
Sort Attributes = Carrier, Name of Doc, Version No
Message comment = Tu prosze umieszczac informacje o ANEKSACH oraz informacje dodatkowe:
Reply comment = Please enter your reply here:
Attachment comment = Tu prosze dodac zalaczniki:
Use Lock = 0
Fix text = 0
Logout to main = 1
Resubmit default = 2
Expand default = 1
Reverse sort = 1
Suppress default = 3
Suppress execute default = 2
Suppress Email on edit = 3
|
|
67581
|
Fri Oct 11 19:20:22 2013 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2-2455 | Re: Navigation previous and next button don't work |
| Stefan Ritt wrote: |
| Hung Dao wrote: |
|
| Stefan Ritt wrote: |
|
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum?
|
I have tried this forum, it worked fine. So, it should not be a browser. The only different I have logbook that I have been working on ELOG v2.6.5 and I have installed a new version v2.9.2. I just wonder any different data format (2.6.5 vs. 2.9.2) could have caused a problem.
|
The data format has nothing to do with the functionality of browsing buttons. Except if you have an empty logbook, or a logbook with just one entry, then of course going forwared and backward will not make any sense. |
I have a group includes more than one logbooks. One has about 1600 entries and another new one has 5 entries. I have tried them both. When I retested with v2.6.5, the buttons are still functional. This problem also exists on Firefox plus giving me a message "This is the first entry" "This is the last entry" when I clicked a previous button and next button respectively. I need to use v2.9.2 since it has many improvements |
|
67580
|
Fri Oct 11 16:47:58 2013 |
| Paraic Fahey | paraic.fahey@pfizer.com | Question | Windows | 2.7.6 | Re: cannot add new logbooks to any of my logbook groups |
| David Pilgram wrote: |
|
| Stefan Ritt wrote: |
|
| Paraic Fahey wrote: |
|
Each time a attempt to CREATE A LOGBOOK on any of my logbook groups, I get an ELOG ERROR page presenting saying FORBIDDEN ATTRIBUTE DATE.
I have, up until recently been able to add new logbooks.
Can anybody help me on this.
Paraic Fahey
|
Just modify your configuration file elogd.cfg manually with an editor and add your logbooks there, then restart elogd.
/Stefan
|
I cannot answer for Windoze, BUT there is more to this if you use Linux.
(Sorry for re-entry, I spotted a cut-and-paste error from first time around)
If you want to make a new logbook in linux manually, you need to do the following:
0. Stop the elogd daemon.
1. Edit elogd.cfg as Stefan said. This will be in two parts - at the top, and then a block of entries which is what you normally see when you go to the "config" section of any logbook. Easiest to copy and paste an existing block, only remember to put in a new header in the square brackets at the top - the name of your new logbook. While most of the elogd.cfg is the same as in the documentation, the additional headers etc are pretty self-explanatory, and you only see these because you're editing the file raw rather than through the elog interface. Once restarted, you can then edit the config for the new logbook in the usual way.
2. Create a new subdirectory in your logbooks directory *with the same name* as the name you added in when editing elogd.cfg.
3. Give that subdirectory the correct ownership and permissions.
4. Only then, start elogd again.
As a windows user, which of the above you need to do: create the subdirectory (I imagine so) and/or anything else (I don't know). I don't use Windows - apart from AutoCAD and one other javascript based program that non-the-less has windows dependancies (!).
David.
|
David, Stefan,
Thanks for your help. Directly editing the elog.cfd file worked.
Paraic |
|
67579
|
Fri Oct 11 16:18:05 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.2-2455 | Re: Navigation previous and next button don't work |
| Hung Dao wrote: |
|
| Stefan Ritt wrote: |
|
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum?
|
I have tried this forum, it worked fine. So, it should not be a browser. The only different I have logbook that I have been working on ELOG v2.6.5 and I have installed a new version v2.9.2. I just wonder any different data format (2.6.5 vs. 2.9.2) could have caused a problem.
|
The data format has nothing to do with the functionality of browsing buttons. Except if you have an empty logbook, or a logbook with just one entry, then of course going forwared and backward will not make any sense. |
|
67578
|
Fri Oct 11 15:59:39 2013 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2-2455 | Re: Navigation previous and next button don't work |
| Stefan Ritt wrote: |
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum? |
I have tried this forum, it worked fine. So, it should not be a browser. The only different I have logbook that I have been working on ELOG v2.6.5 and I have installed a new version v2.9.2. I just wonder any different data format (2.6.5 vs. 2.9.2) could have caused a problem.
|
|
67577
|
Fri Oct 11 11:19:00 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Windows | 2.9.2-2455 | Re: Navigation previous and next button don't work |
| Stefan Ritt wrote: |
|
| Mark Campbell wrote: |
|
| Stefan Ritt wrote: |
|
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum?
|
The navigation buttons work for me but Ctrl-PgUp and Ctrl-PgDn does not in IE8 or Chrome.
However buttons and Ctrl-PgUp and Ctrl-PgDn both work in FireFox, so seems to be browser specific, I noted that in Chrome Ctrl-PgUp and Ctrl-PgDn moves through your open Tabs.
|
I confirm that IE8 and Chrome "eat" the Ctrl-PgUp/Dn keys, so they are not passed to ELOG, and there is nothing I can do about.
|
On this linux box, using Firefox 12, if tabs are in use, Ctrl-Pgup/Ctrl-Pgdn goes throught the tabs. If you force tabs off, then it goes through the entries.
Bavigation buttons work fine. |
|