Re: XML, CSV and Raw export produces 'last' page only, posted by Stefan Ritt on Tue Nov 7 08:17:40 2006
|
| Brian Marshall wrote: | The Find command page provides an option, 'Display n entries per page' which is useful when the result of the search is to be viewed on-screen.
However this value is also applied to CSV, XML and Raw export and only the 'last' page of data is exported.
For example, if there are 17 matching entries and n is set to 8, only one entry will appear in the exported file.
In my opinion, this option should be ignored for XML, CSV and Raw export and all matching entries should be exported. |
This is indeed right. I fixed it in the current SVN revision #1741. |
Specifying the size of am image attachment, posted by Val Schmidt on Mon Apr 6 20:46:42 2009
|
Hello,
I'm curious, is it possible to specify (perhaps by default) the rendered size of an attached image. For example, I'd like all images uploaded to be scaled to 100% of the browser window size so a large image is not most off the screen. What I want is to specify the width="100" attribute of the <img /> tag, but it's not clear 1) how do to this for an attachment and 2) if it might be possible to do this in the config file for all img attachments.
Thanks,
Val |
|
Re: Specifying the size of am image attachment, posted by Stefan Ritt on Wed Apr 8 12:25:07 2009
|
| Val Schmidt wrote: |
|
I'm curious, is it possible to specify (perhaps by default) the rendered size of an attached image. For example, I'd like all images uploaded to be scaled to 100% of the browser window size so a large image is not most off the screen. What I want is to specify the width="100" attribute of the <img /> tag, but it's not clear 1) how do to this for an attachment and 2) if it might be possible to do this in the config file for all img attachments.
|
When you use the ImageMagick package, attached images are scaled to a predefined size using the option "Thumbnail size = ...". See the documentation for that option for details. |
Corrupt page link, posted by Ulrich Trüssel on Wed Jun 21 14:21:01 2006
|
If a loggbook contains more than one page of entries, above and under the list are links for changing the page by number (or privous / last and all) conatining links looking like "http://localhost:8080/logbook/page2?mode=mode". This is the correct link and will work until Version 2.6.1-5!
In Version 2.6.1-6 the link is corrupted and look always like "http://localhost:8080/logbook/pag" |
|
Re: Corrupt page link, posted by Stefan Ritt on Wed Jun 21 17:03:23 2006
|
| Ulrich Trüssel wrote: | If a loggbook contains more than one page of entries, above and under the list are links for changing the page by number (or privous / last and all) conatining links looking like "http://localhost:8080/logbook/page2?mode=mode". This is the correct link and will work until Version 2.6.1-5!
In Version 2.6.1-6 the link is corrupted and look always like "http://localhost:8080/logbook/pag" |
Well, in this forum the link is fine, so it must have to do with your special configuration. Can you try with the demo logbook and find out which configuration option causes this problem? |
|
Re: Corrupt page link, posted by Arno Teunisse on Wed Jul 5 00:18:29 2006
|
| Ulrich Trüssel wrote: | If a loggbook contains more than one page of entries, above and under the list are links for changing the page by number (or privous / last and all) conatining links looking like "http://localhost:8080/logbook/page2?mode=mode". This is the correct link and will work until Version 2.6.1-5!
In Version 2.6.1-6 the link is corrupted and look always like "http://localhost:8080/logbook/pag" |
In this version, the above is true. It also has corrupted entries when clicking : Full | Summary | Threaded.
On MSExplorer and Firefox only a part of the link is shown in the left-down corner of the browser :
http://localhost:8080/?mo
No matter what button you click.
It should be : http://localhost:8080/?mode=full
http://localhost:8080/?mode=Summary
http://localhost:8080/?mode=Attachments
I'v tested is with the default elogd.cfg file which comes with the installation.
Something is going wrong here.
When importing a csv text file the above is introduced also.
Just installed the previous version :
====================================
[C:\Program Files\ELOG]elogd -c elogd.cfg
elogd 2.6.1 built May 24 2006, 08:59:09 revision 1688
Indexing logbooks ... done
Server listening on port 8080 ...
And the problem is gone. !!!!
problem is in version :
==========================
[C:\Program Files\ELOG1]elogd -c elogd.cfg
elogd 2.6.1 built Jun 13 2006, 08:43:21 revision 1691
Indexing logbooks ... done
Server listening on port 8080 ...
I love elog , for it's simplicity,
but will not upgrade to the lastest release untill this is solved. |
|
Re: Corrupt page link, posted by Stefan Ritt on Wed Jul 5 12:51:25 2006
|
| Arno Teunisse wrote: | Just installed the previous version :
====================================
[C:\Program Files\ELOG]elogd -c elogd.cfg
elogd 2.6.1 built May 24 2006, 08:59:09 revision 1688
Indexing logbooks ... done
Server listening on port 8080 ...
And the problem is gone. !!!!
problem is in version :
==========================
[C:\Program Files\ELOG1]elogd -c elogd.cfg
elogd 2.6.1 built Jun 13 2006, 08:43:21 revision 1691
Indexing logbooks ... done
Server listening on port 8080 ...
|
Thanks for your detailed information. The hint with the two different revisions heally helped. I fixed that in revision 1695, and made an intermediate release 2.6.1-7. This will fix the problem. Can you please check that this is working? |
|
Re: Corrupt page link, posted by Arno Teunisse on Sun Sep 3 23:16:31 2006
|
| Stefan Ritt wrote: |
| Arno Teunisse wrote: | Just installed the previous version :
====================================
[C:\Program Files\ELOG]elogd -c elogd.cfg
elogd 2.6.1 built May 24 2006, 08:59:09 revision 1688
Indexing logbooks ... done
Server listening on port 8080 ...
And the problem is gone. !!!!
problem is in version :
==========================
[C:\Program Files\ELOG1]elogd -c elogd.cfg
elogd 2.6.1 built Jun 13 2006, 08:43:21 revision 1691
Indexing logbooks ... done
Server listening on port 8080 ...
|
Thanks for your detailed information. The hint with the two different revisions heally helped. I fixed that in revision 1695, and made an intermediate release 2.6.1-7. This will fix the problem. Can you please check that this is working? |
Sorry for my ( very ) late answer , But yes the problem is GONE after installing the new release? Thanks. |