ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67
|
Thu Jul 11 10:36:09 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | | | Re: a bug and a question |
> If you have only one entry in the logbook and have it set up in threaded
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon
> of the entry or the number of the entry to see it, it does not allow you
> to. If there is more than one entry, it works fine.
Ok, has been fixed. Will come in 2.0.5
> Also I wanted to make a submit page from where you could either go back
> to the logbook which you just entered a message for or type a new entry for
> that logbook. First of all, is there a way to have only one file called
> submitpage.html in which I can define this for all logbooks or do i need it
> for ever logbook. And also, is there a way I can even set a link that will
> allow to create a new entry. I tried:
> <a href="demo/?cmd=new">Enter</a> another message<p>
>
> but for some reason it does not work. Is there a way to implement this?
The documentation was wrong about that which has been corrected. The proper
file contents should be
<h1>You successfully submitted a message</h1>
<a href="?cmd=Back">Back</a> to the logbook<p>
<a href="?cmd=New">Enter</a> another message
This way one only needs one file for all logbooks. |
67
|
Thu Jul 11 10:36:09 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | | | Re: a bug and a question |
> If you have only one entry in the logbook and have it set up in threaded
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon
> of the entry or the number of the entry to see it, it does not allow you
> to. If there is more than one entry, it works fine.
Ok, has been fixed. Will come in 2.0.5
> Also I wanted to make a submit page from where you could either go back
> to the logbook which you just entered a message for or type a new entry for
> that logbook. First of all, is there a way to have only one file called
> submitpage.html in which I can define this for all logbooks or do i need it
> for ever logbook. And also, is there a way I can even set a link that will
> allow to create a new entry. I tried:
> <a href="demo/?cmd=new">Enter</a> another message<p>
>
> but for some reason it does not work. Is there a way to implement this?
The documentation was wrong about that which has been corrected. The proper
file contents should be
<h1>You successfully submitted a message</h1>
<a href="?cmd=Back">Back</a> to the logbook<p>
<a href="?cmd=New">Enter</a> another message
This way one only needs one file for all logbooks. |
67
|
Thu Jul 11 10:36:09 2002 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | | | Re: a bug and a question |
> If you have only one entry in the logbook and have it set up in threaded
> mode like: ?cmd=Search&mode=threaded&reverse=1, when you click on the icon
> of the entry or the number of the entry to see it, it does not allow you
> to. If there is more than one entry, it works fine.
Ok, has been fixed. Will come in 2.0.5
> Also I wanted to make a submit page from where you could either go back
> to the logbook which you just entered a message for or type a new entry for
> that logbook. First of all, is there a way to have only one file called
> submitpage.html in which I can define this for all logbooks or do i need it
> for ever logbook. And also, is there a way I can even set a link that will
> allow to create a new entry. I tried:
> <a href="demo/?cmd=new">Enter</a> another message<p>
>
> but for some reason it does not work. Is there a way to implement this?
The documentation was wrong about that which has been corrected. The proper
file contents should be
<h1>You successfully submitted a message</h1>
<a href="?cmd=Back">Back</a> to the logbook<p>
<a href="?cmd=New">Enter</a> another message
This way one only needs one file for all logbooks. |
1991
|
Mon Oct 16 16:20:06 2006 |
| Dimitrios Tsirigkas | dimitrios.tsirigkas@cern.ch | Question | | | Problem with large entry size |
Hi Stefan,
I have posted an entry of approximately a thousand lines (ten thousand words). Posting it took some time, which is logical to a certain degree. However, whenever a user asks for "Full" view of the logbook, the page takes around two minutes to load and the CPU usage on the elog server goes to beyond 90% for all this time. Is this to be expected for an entry of that size or is there something going wrong here?
Thanks,
Dimitris |
1992
|
Mon Oct 16 16:53:43 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Problem with large entry size |
Dimitrios Tsirigkas wrote: | I have posted an entry of approximately a thousand lines (ten thousand words). Posting it took some time, which is logical to a certain degree. However, whenever a user asks for "Full" view of the logbook, the page takes around two minutes to load and the CPU usage on the elog server goes to beyond 90% for all this time. Is this to be expected for an entry of that size or is there something going wrong here? |
The problem lies in the ELCode parsing. When you post an entry in ELCode form, the elogd server has to parse every word to see if it's any of the ELcode tags. This is right now implemented in a kind of poor way, such that it takes very long for long entries. I will work to optimize that. In the meantime, it will help if you post such long entries just in "plain" form.
- Stefan |
1993
|
Mon Oct 16 17:18:58 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | | | Re: Problem with large entry size |
I improved the performance by some factor in SVN revision 1733. Can you give it a try and report your speed improvement? Depending on the result, I can probably do even a bit better with some more effort.
- Stefan |
1994
|
Mon Oct 16 17:32:58 2006 |
| Dimitrios Tsirigkas | dimitrios.tsirigkas@cern.ch | Question | | | Re: Problem with large entry size |
Stefan Ritt wrote: | I improved the performance by some factor in SVN revision 1733. Can you give it a try and report your speed improvement? Depending on the result, I can probably do even a bit better with some more effort.
- Stefan |
Dear Stefan,
Thank you for your quick reply. I will install the new version and I will let you know as soon soon as possible.
Best,
Dimitris |
2003
|
Tue Oct 17 14:39:29 2006 |
| Dimitrios Tsirigkas | dimitrios.tsirigkas@cern.ch | Question | | | Re: Problem with large entry size |
Stefan Ritt wrote: |
The problem lies in the ELCode parsing. When you post an entry in ELCode form, the elogd server has to parse every word to see if it's any of the ELcode tags. This is right now implemented in a kind of poor way, such that it takes very long for long entries. I will work to optimize that. In the meantime, it will help if you post such long entries just in "plain" form.
- Stefan |
Hi again,
I was wondering what is the cleanest way of changing old entries already submitted in ELCode into plain text. If I do not include ELCode in the allowed encodings does this apply to already submitted entries as well or will they still be treated as ELCode?
Thanks,
Dimitris |