| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67546
|
Thu Jul 4 15:27:13 2013 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Bug fix | All | 2.9.2-2481 | Re: Export entries to XLS or CSV? |
| Jim Tinlin wrote: |
|
| Stefan Ritt wrote: |
|
| Andreas Luedeke wrote: |
|
Yes, you're right: the text field is only exported in XML and Raw mode.
It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.
But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.
I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.
(This string has not yet been added to the localization.)
As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.
Of course the spreadsheet programs just display the HTML source.
Stefan, do you think this should be added to the official branch?
 ⇄
Detect language » English
⇄
Detect language » English
|
Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution.
|
Has this been added yet?
I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work.
Thanks!
|
Hi Jim, I've incorporated the patch to our production server about a week ago.
I've agreed with Stefan that he'll add it, when it proved to run stable for a while.
Until now it appears to work fine. I think Stefan will add it to the distribution soon.
But I won't touch any Windows systems, you'll need to wait for someone else to compile it for you.
Maybe some skilled Windows user want to give it a try: i've attached the changes in the elogd.c file from v2.9.2-2481,
the modified file can be currently downloaded from http://people.web.psi.ch/luedeke/public/tmp/elogd.c
⇄
Detect language » English
Andreas
⇄
Detect language » English
⇄
Detect language » English
⇄
Detect language » English
|
| Attachment 1: elog-2.9.2-2481_cvs3patch.diff
|
11597c11597
< rsprintf("<tr><td class=\"form1\"><table><tr><td valign=\"top\" class=\"form1\">\n");
---
> rsprintf("<tr><td class=\"form1\">\n");
11599c11599
< rsprintf("<b>%s:</b>
", loc("Mode"));
---
> rsprintf("<b>%s:</b> ", loc("Mode"));
11609c11609
< rsprintf("<label for=\"full\">%s </label>
\n", loc("Display full entries"));
---
> rsprintf("<label for=\"full\">%s </label>\n", loc("Display full entries"));
11615c11615
< rsprintf("<label for=\"summary\">%s </label>
\n", loc("Summary only"));
---
> rsprintf("<label for=\"summary\">%s </label>\n", loc("Summary only"));
11622c11622
< rsprintf("<label for=\"summary\">%s </label>
\n", loc("Summary"));
---
> rsprintf("<label for=\"summary\">%s </label>\n", loc("Summary"));
11631c11631
< rsprintf("</td><td valign=\"top\" class=\"form1\"><b>%s:</b>
", loc("Export to"));
---
> rsprintf("<b>%s:</b> ", loc("Export to"));
11637c11637
< rsprintf("<label for=\"CSV1\">%s </label>
\n", loc("CSV (\",\" separated)"));
---
> rsprintf("<label for=\"CSV1\">%s </label>\n", loc("CSV (\",\" separated)"));
11643,11649c11643
< rsprintf("<label for=\"CSV2\">%s </label>
\n", loc("CSV (\";\" separated)"));
<
< if (strieq(mode, "CSV3"))
< rsprintf("<input type=radio id=\"CSV3\" name=\"mode\" value=\"CSV3\" checked>");
< else
< rsprintf("<input type=radio id=\"CSV3\" name=\"mode\" value=\"CSV3\">");
< rsprintf("<label for=\"CSV3\">%s </label>
\n", loc("CSV (\";\" separated) + Text"));
---
> rsprintf("<label for=\"CSV2\">%s </label>\n", loc("CSV (\";\" separated)"));
11655c11649
< rsprintf("<label for=\"XML\">XML </label>
\n");
---
> rsprintf("<label for=\"XML\">XML </label>\n");
11661c11655
< rsprintf("<label for=\"Raw\">Raw </label>
\n");
---
> rsprintf("<label for=\"Raw\">Raw </label>\n");
11663c11657
< rsprintf("</td>\n");
---
> rsprintf("</td></tr>\n");
11665c11659
< rsprintf("<td valign=\"top\" class=\"form2\"><b>%s:</b>
", loc("Options"));
---
> rsprintf("<tr><td class=\"form2\"><b>%s:</b>
", loc("Options"));
11707c11701
< rsprintf("</td></tr></table></td></tr>\n");
---
> rsprintf("</td></tr>\n");
19535c19529
< csv = strieq(mode, "CSV1") || strieq(mode, "CSV2") || strieq(mode, "CSV3");
---
> csv = strieq(mode, "CSV1") || strieq(mode, "CSV2");
20266,20268c20260
< } else {
< if (strieq(mode, "CSV3"))
< rsprintf(";\"Text\"");
---
> } else
20270d20261
< }
20973,20987c20964
< } else {
< if (strlen(text)>0 && strieq(mode, "CSV3")) {
< rsprintf(";");
< strlcpy(str, text, sizeof(str));
< rsputs("\"");
< pt1 = str;
< while ((pt2 = strchr(pt1, '"')) != NULL) {
< *pt2 = 0;
< rsputs(pt1);
< rsputs("\"\"");
< pt1 = pt2 + 1;
< }
< rsputs(pt1);
< rsputs("\"");
< }
---
> } else
20989d20965
< }
|
|
67667
|
Fri Feb 21 13:25:55 2014 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | All | 2.9.2-2481 | Re: Export entries to XLS or CSV? |
| Andreas Luedeke wrote: |
|
| Jim Tinlin wrote: |
|
| Stefan Ritt wrote: |
|
| Andreas Luedeke wrote: |
|
Yes, you're right: the text field is only exported in XML and Raw mode.
It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.
But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.
I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.
(This string has not yet been added to the localization.)
As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.
Of course the spreadsheet programs just display the HTML source.
Stefan, do you think this should be added to the official branch?
⇄
Detect language » English
⇄
Detect language » English
|
Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution.
|
Has this been added yet?
I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work.
Thanks!
|
Hi Jim, I've incorporated the patch to our production server about a week ago.
I've agreed with Stefan that he'll add it, when it proved to run stable for a while.
Until now it appears to work fine. I think Stefan will add it to the distribution soon.
But I won't touch any Windows systems, you'll need to wait for someone else to compile it for you.
Maybe some skilled Windows user want to give it a try: i've attached the changes in the elogd.c file from v2.9.2-2481,
the modified file can be currently downloaded from http://people.web.psi.ch/luedeke/public/tmp/elogd.c
⇄
Detect language » English
Andreas
⇄
Detect language » English
⇄
Detect language » English
⇄
Detect language » English
|
This patch is now officially in the GIT repository. |
|
66420
|
Thu Jun 25 15:37:14 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.6 | Re: Export and save problem with IE7 |
| soren poulsen wrote: |
|
Hi
Would it be possible to use the "Export to:" function with IE7 on the Forum logbook, and save the logbook.
I can do the export but saving the file with IE7 does not work. Saving the file with Firefox, Chrome, Safari works.
This makes me think that E-log is good and IE7 is bad ?
Soren
|
Right 
It seems to be a well known probmel with IE: http://classicasp.aspfaq.com/files/directories-fso/how-do-i-send-the-correct-filename-with-binarywrite.html
So I tried all variations there, but none of them worked. The interesting thing is that it works if you use it locally, but not with the forum (which has an additional "/elogs" in the URL).
|
|
66587
|
Tue Nov 10 12:54:47 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.5-2130 | Re: Export Text to a csv File |
| Michael Dannmeyer wrote: |
|
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?
Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else. |
|
66588
|
Tue Nov 10 13:06:26 2009 |
| Michael Dannmeyer | michael.dannmeyer@solvias.com | Question | Windows | 2.7.5-2130 | Re: Export Text to a csv File |
| Stefan Ritt wrote: |
|
| Michael Dannmeyer wrote: |
|
Hello,
is it possible to export the Text Field and the entries in this field to a csv file? If yes, what are the settings to do this?
Regards
Michael
|
A CSV file is by definition one line per entry. So if you have several lines in your Text Field, how will you be able to squeeze this into one line?
Alternatively you can export to XML, which contains the Text Field, then do a manual conversion to something else.
|
Thanks for your fast answer. |
|
65938
|
Thu Jul 31 09:25:01 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.4-2113 | Re: Exploit Browser Tabs to Make Anonymous Entries |
| Alan Stone wrote: |
|
One of my shifters just managed to make an anonymous logbook entry even though the Author attribute is required.
It turns out that he had two tabs in his browser opened/logged into the Elog. He logged out in one tab only. Then he
did some other work on the desktop. Then he returned to the browser to make a new logbook entry, finding the tab which
still showed the logged in menu, including the link for "New". The Shifer is on day two, so he did not give any special
notice to seeing Anonymous in the Author field instead of his name. He did point it out when I came in, and noted that
no warning was given about making an anonymous entry.
I tested the same scenario myself. One cannot preview an anonymous entry (when Author field is a required attribute).
A warning is given. However, one can submit the anonymous entry, and no warning is given.
|
What configuration do you use? I tried to reproduce your problem with a "minimal" configuration like
[demo]
Attributes = Author, Subject
Preset Author = $long_name
Locked Attributes = Author
When I log out from the second browser tab and click on "New" on the first browser tab, I am shown the login page, not the new entry page. I guess your "menu commands" and "guest menu commands" allow non-logged in users to issue a "New" command. Try removing that.
Stefan |
|
69172
|
Fri Jul 17 09:18:18 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | ELOG V3.1.4-a04 | Re: Expanding column width when viewing in Summary mode | You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.
| Illam Pakkirisamy wrote: |
|
Hi,
I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it. Is this possible and if so, how would I do it.
Thanks in advance for your help.
Illam
|
|
|
Draft
|
Sat Jul 18 17:18:54 2020 |
| Illam Pakkirisamy | illam@senseeker.com | Question | Windows | ELOG V3.1.4-a04 | Re: Expanding column width when viewing in Summary mode |
| Stefan Ritt wrote: |
|
You can't directly change individual columns, but you can reduce the "Text" column. This is done in themes/default/elog.css. Search for "listtitle2" and change or remove the line "width:100%". This makes the text column narrower, leaving more space for the subject column.
| Illam Pakkirisamy wrote: |
|
Hi,
I'm trying to expand the Subject column, when viewing in summary mode, and couldn't find any documentation for it. Is this possible and if so, how would I do it.
Thanks in advance for your help.
Illam
|
|
|
|