ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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. |
67576
|
Fri Oct 11 10:21:52 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.9.2-2455 | Re: Navigation previous and next button don't work |
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. |
67575
|
Fri Oct 11 10:18:04 2013 |
| Mark Campbell | CAMP2MAR@police.nsw.gov.au | 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?
|
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. |
67574
|
Fri Oct 11 09:44:42 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: |
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? |
67573
|
Thu Oct 10 21:03:09 2013 |
| Hung Dao | hungtdao@yahoo.com | Bug report | Windows | 2.9.2-2455 | Navigation previous and next button don't work |
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. |
67572
|
Wed Oct 9 09:19:54 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.9.2 | Re: Importing XML/CSV |
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
|
67571
|
Tue Oct 8 18:14:20 2013 |
| Barend | office@amtc2.com | Bug report | Windows | 2.9.2 | Importing XML/CSV |
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? |
Attachment 1: import.xml
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<ELOG_LIST>
<ENTRY>
<MID>1</MID>
<DATE>Mon 07 Oct 2013 11:41:42 +0200</DATE>
<ENCODING>plain</ENCODING>
<Data_dekretacji>01.10.2013</Data_dekretacji>
<Numer_rejestru>XXX/2013/001</Numer_rejestru>
<Numer_umowy>44/333/N/2012</Numer_umowy>
<Nazwa_dokumentu>XXXXXXXXXXXXXXXX</Nazwa_dokumentu>
<Przedmiot_umowy></Przedmiot_umowy>
<Kontrahent>AAAAAAAA BBBBBBBBBB</Kontrahent>
<Data_zawarcia>10.07.2012</Data_zawarcia>
<Data_konca>10.07.2013</Data_konca>
<Dzial></Dzial>
<Status>Nieaktualna</Status>
<Aneksy></Aneksy>
<Opis></Opis>
<Opis2></Opis2>
<Opis3></Opis3>
</ENTRY>
<ENTRY>
<MID>2</MID>
<DATE>Mon 07 Oct 2013 11:41:42 +0200</DATE>
<ENCODING>plain</ENCODING>
<Data_dekretacji>01.10.2013</Data_dekretacji>
<Numer_rejestru>XXX/2013/002</Numer_rejestru>
<Numer_umowy>33/330/N/2012</Numer_umowy>
<Nazwa_dokumentu>CCCCCC DDDDDDDD</Nazwa_dokumentu>
<Przedmiot_umowy></Przedmiot_umowy>
<Kontrahent>XXXXXXXXXXXXXX</Kontrahent>
<Data_zawarcia>01.06.2012</Data_zawarcia>
<Data_konca></Data_konca>
<Dzial></Dzial>
<Status>Aktualna</Status>
<Aneksy></Aneksy>
<Opis></Opis>
<Opis2></Opis2>
<Opis3></Opis3>
</ENTRY>
</ELOG_LIST>
|
67570
|
Mon Oct 7 10:33:32 2013 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | 2.7.6 | Re: cannot add new logbooks to any of my logbook groups |
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. |