ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68091
|
Mon Aug 17 11:26:22 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | For any other filter you need "&<attribute>=", which of course requires the knowlede of all attributes. There is no other "standard" flag in the URL indicating a search.
Philip Leung wrote: |
This only applies to searches which specify that they are searching through the message text though. It would not work for things like quick filter
Stefan Ritt wrote: |
Look for "&subtext=" in the URL
Philip Leung wrote: |
Is there no good way of differentiating search operations from others by URL?
Philip Leung wrote: |
Thanks for the quick response!
It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.
The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.
Stefan Ritt wrote: |
I guess the underlying problem is the long time these requests take and block other users.
I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.
Philip Leung wrote: |
Hello all,
I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.
Does anybody have any suggestions?
Regards,
Philip
|
|
|
|
|
|
|
68093
|
Mon Aug 17 11:36:49 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.1 | Re: Isolating search urls | No, no and again: no.
Philip Leung wrote: |
Would there be a simple way to redirect all URLs BUT the ones which trigger searches?
Stefan Ritt wrote: |
For any other filter you need "&<attribute>=", which of course requires the knowlede of all attributes. There is no other "standard" flag in the URL indicating a search.
Philip Leung wrote: |
This only applies to searches which specify that they are searching through the message text though. It would not work for things like quick filter
Stefan Ritt wrote: |
Look for "&subtext=" in the URL
Philip Leung wrote: |
Is there no good way of differentiating search operations from others by URL?
Philip Leung wrote: |
Thanks for the quick response!
It's great to hear that multi-threading is in the works as this has been my main issue with an otherwise very nice piece of software. I do, however, feel like we should be able to get my slightly hacky approach to work to hold us over until you finish.
The idea is to run separate ELOG instances in read-only mode dedicated to these types of requests. I've managed to sync up the logbook indexation of each instance so now, unless there's some statefulness to ELOG that I'm forgetting about, I only need to make sure that requests are forwarded to the right instance.
Stefan Ritt wrote: |
I guess the underlying problem is the long time these requests take and block other users.
I have pretty high on my todo list to convert ELOG into a multi-threaded server which would fix this completely. So if you are patient enough (=months) you might get what you want.
Philip Leung wrote: |
Hello all,
I am in need of isolating GET-requests referring to long-running, read-only elog functions such as search/filter/sort in our Apache proxy and redirecting them elsewhere. There does not, however, appear to be any easy way of reliably isolating these functions (with the exception of sort) by only looking at the URL.
Does anybody have any suggestions?
Regards,
Philip
|
|
|
|
|
|
|
|
|
68099
|
Thu Aug 20 15:52:26 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | 3.1.1 | Re: Version 3.1.1 of elog has been released | Thanks for reportung that bug. I fixed it in revision f828049.
Edmund Hertle wrote: |
There seems to be a small problem with the new "Date/Time format <attribute>" implementation. It works great for the detailed view of a single entry:

But fails to work on the list view (same entry, the Date column is formated as it should):

Relevant config part:
Time format Time Start = %H:%M:%S
Time format Time End = %H:%M:%S
|
|
68131
|
Mon Sep 28 11:58:11 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.9.0(elogd) | Re: elog client overwriting attached files when editing existing log | You are right. "Edit" should be more like "Replace". I changed that in the documentation.
I acknowledge the request to replace or append only a specific attribute or attachment, and put it on my to-do list.
Stefan
Andreas Luedeke wrote: |
The "elog" command has no "append" feature. You can either create a new entry, or you can overwrite an old entry. Therefore this is not a bug but the intended bahaviour.
I admit that the documentation is misleading, since overwriting an existing entry is called "editing":
[-e <id>] Edit existing message
I interprete your posts that you would like to have two new features for the "elog" command:
- to append text to the body of an existing entry
- to add additional attachments to an existing entry
Without a specific application in mind I would like to add a request (for consistency):
- to modify a specific attribute of an existing entry.
Cheers, Andreas
Edmund Hertle wrote: |
Hey,
I think this is a "problem" of the elog client, since it simply replaces the data. In most cases this is what you want, but since I wanted to have the option to append to the acutal message I built a function to first read-back the entry and add to the message instead of replacing it.
I just played around a bit and found that the attachments will be even disconnected, if you do not specify the -f parameter but just edit a different part of this entry.
A work-around for this is tricky. I tried to write to the "Attachment" attribute directly (-a "Attachment=Filename'), since then you coud read back the data first and manually add the filenames again. But this does not work.
Since the attachments are not actually removed, the only option I see is to modify the logbook file entry on the server by manually re-adding the filenames to the "Attachment: " line.
Joseph McKenna wrote: |
Using the elog client to upload atachments, I can successfully send attachments to an existing elog, however the existing attachments are lost.
I have tested using the elog client version 3.1.1 and elog client version 2.9.2 sending to elogd 2.9.0
elog -h localhost -p 8080 -l test -f file1.png -f file2.png -e 249 -v -x
This works great, the text contained in the elog post is retained, however all attachments are lost and replaced with those sent by this command.
Can anyone provide some tips? I am not sure if its a problem with the client or server.
Thank you in advance!
Joseph
|
|
|
|
68132
|
Mon Sep 28 12:05:04 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 3.1.1 | Re: Creating ELog Links not working properly in HTML Editor | Right, spaces won't work. But others work. Andreas, if you just put elog:1 without any link etc. just as plain text, it will be converted automatically into a link.
A workaround is to explicitly specify a link to an elog entry. Press the link button from the editor toolbar, enter a name and copy the full URL from the browser address bar, like here: https://midas.psi.ch/elogs/Forum/68129. If you switch to "Source" (Top left editor toolbar, you can changed the link name manually, like here.
Andreas Luedeke wrote: |
I can confirm this bug.
But I don't think this has to work as you've described it, when using the HTML editor: if you use HTML, you can use the link feature of the editor.
But that link feature does currently not work at all with internal elog references, not even a simple elog:1"> elog:1 (as you can see here). I suppose there is some more work to do for Stefan on that ;-)
Cheers, Andreas
Edmund Hertle wrote: |
Hey,
the syntax for creating links to other elog entries has a small issue in the HTML editor. The link will not be created properly if there are whitespaces in the name of the logbook. Using ELCode (or in a simple attribute field) the whitespaces can be replaced by "+", but this does not work in the HTML editor. The work-around would be to use ELCode mark-up instead of HTML.
Example 1 (this should work): elog:Contributions/47
Example 2 (this will not work): elog:Config+Examples/11
Example 3 (will also not work): elog:Config%20Examples/11
|
|
|
68142
|
Tue Oct 13 09:47:18 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | V3.1.0-2411f95 | Re: inline jpg to png | You can turn off thumbnail creation with
Thumbnail size = 0
as written in the documentation. The PNG files are "thumbnails" (= smaller versions of large pictures). Mostly people put large images into elog entries, which take long times to download. Having small thumbnails insted speeds up download times considerably.
Stefan
Jacky Li wrote: |
Hi,
We have a user who posted a lot of inline jpg. The elog system converted those to png and thus cause the size of the elog to expand about ~4x of the original size. It is caused the problem of entry size too large for email notifications. Is there a way to turn off the conversion to png picture file? May I know also know why it converts to png to store on the server? Thank you very much.
Jacky
|
|
68145
|
Thu Oct 15 14:34:36 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.1 | Re: How does one create a html template for an entry | > Good Day
>
> I am new to elog and have a question. This is best explain with an example. If I have two logbooks named "home" and "work" and I would like all the entries of home to be of a specific html format (for example a table containing
> a set amount of rows and columns) and work can be any plain text entry how would I go about doing this? I saw the documentation mention something about html templates but i cant seem to find the section about where they are stored
> or how they are created and applied to a specific logbook. I know how to restrict the entry encoding to either html, elcode or plain text for a logbook. Any help would be appreciated.
>
> Regard
> Kenzo Abrahams
So-called "custom" entry/view forms are a bit for experienced people. You should be fluent with HTML and JavaScript. The (minimal) documentation is here: https://midas.psi.ch/elogs/Forum/66909
If you want a table style input form, better use Google Spreadsheets.
Stefan |
68148
|
Fri Oct 23 08:29:33 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | Latest | Re: Columns numeric input are added/computed | No, formulas are not yet implemented. For such things I would use Google Spreadsheets in meantime.
Stefan
Dawang wrote: |
Hi Stefan,
Good day. I'm thinking if this wishlist is already available in elog. The values in columns we're added or computed according to formula set in a single separate column.
Thanks,
Raymund
|
|
|