Creating ELog Links not working properly in HTML Editor, posted by Edmund Hertle on Mon Sep 7 12:44:42 2015
|
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 |
Re: Creating ELog Links not working properly in HTML Editor, posted by Andreas Luedeke on Mon Sep 28 06:29:57 2015
|
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
|
|
Re: Creating ELog Links not working properly in HTML Editor, posted by Stefan Ritt on Mon Sep 28 12:05:04 2015
|
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
|
|
|
Re: Creating ELog Links not working properly in HTML Editor, posted by Andreas Luedeke on Tue Sep 29 08:50:30 2015
|
Hi Stefan,
yes, I know that a plain text " elog:1" works in the HTML editor, too.
But if you put " elog:1" in the URL field of the link dialog, then ELOG screws up: you get the text
and the link points to link type "URL", protocol "<other>", URL "1".
Or more precisely, the HTML source looks like the following:
<a href="1">elog.1</a>"><a href="1">elog.1</a>
(I've replaced ":" by "." here in the source, to avoid another iteration of links by ELOG).
That is not what I would have expected:
either it should have been remained unchanged, or it should point to the right URL of the entry elog:1 (the latter case preferred :-).
Cheers, Andreas
Stefan Ritt wrote: |
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
|
|
|
|
Elog command not working properly, posted by Stefano colafranceschi on Thu Sep 24 00:14:49 2015
|
<p>Hi,</p>
<p>I have a problem running elog command from php script. Basically in the php I call system("elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache logfile no problem), any suggestions?</p> |
Re: Elog command not working properly, posted by Edmund Hertle on Fri Sep 25 22:37:08 2015
|
> <p>Hi,</p>
>
> <p>I have a problem running elog command from php script. Basically in the php I call system("elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache
logfile no problem), any suggestions?</p>
Hey,
this sounds more like a PHP issue.
Which PHP version are you using?
Which webserver?
Which php function are you using: shell_exec() or exec()? Try looking at the return of exec()
Is the elog file set to the correct file permissions to be executed by the webserver?
Is the elog file in the PHP path or do you take care of defining the correct path?
eddy |
Re: Elog command not working properly, posted by Stefano on Sat Sep 26 03:34:44 2015
|
Yes it was a path issue PHP was not loading correctly environmental path
> > <p>Hi,</p>
> >
> > <p>I have a problem running elog command from php script. Basically in the php I call system("elog -h etc etc.. And from the php command line works but not in the browser apparently without errors (php apache
> logfile no problem), any suggestions?</p>
>
> Hey,
> this sounds more like a PHP issue.
> Which PHP version are you using?
> Which webserver?
> Which php function are you using: shell_exec() or exec()? Try looking at the return of exec()
> Is the elog file set to the correct file permissions to be executed by the webserver?
> Is the elog file in the PHP path or do you take care of defining the correct path?
>
>
> eddy |
Submit to multiple logbooks simultaniously, posted by Francois Cloutier on Fri Sep 25 19:10:45 2015
|
Good day,
My question is : Is it possible to submit to multiple logbooks simultaniously ?
I have 5 logbooks that could share common attributes, is there a way to acheive that without recreate a new entry in each of them ?
Thanks for your help. |
Re: Submit to multiple logbooks simultaniously, posted by Edmund Hertle on Fri Sep 25 22:24:18 2015
|
Hey,
You can use the elog command line tool and submit the same attributes to the 5 different logbooks by iterating over the logbook names executing something like this:
elog -l logbook1 -a "attr1=value1" -a "attr2=value2"
elog -l logbook2 -a "attr1=value1" -a "attr2=value2"
elog -l logbook3 -a "attr1=value1" -a "attr2=value2"
elog -l logbook4 -a "attr1=value1" -a "attr2=value2"
elog -l logbook5 -a "attr1=value1" -a "attr2=value2"
Another option would be having an additional common logbook, removing the commonly shared attributes from the other logbooks and add an attribute which links to this entry (using the "elog:logbook/ID" syntax as a value).
Cheers, eddy
Francois Cloutier wrote: |
Good day,
My question is : Is it possible to submit to multiple logbooks simultaniously ?
I have 5 logbooks that could share common attributes, is there a way to acheive that without recreate a new entry in each of them ?
Thanks for your help.
|
|
Elog command not working properly, posted by Stefano colafranceschi on Thu Sep 24 00:13:31 2015
|
|
elog from php, posted by Stefano on Wed Sep 23 23:57:43 2015
|
Hi,
I need to run elog command in an online php script. The problem I see is that the script works from the command line but not from the browser. In the script I just use:
system(elog -h mypc -p 8080 -l bla -a Author=\'io\' -a Type=\' ..etc.etc
any suggestions? |
Suggestion for tooltips and/or comments, posted by Edmund Hertle on Tue Sep 22 15:04:55 2015
|
Hey,
if you define a Tooltip at the moment it is only displayed on the attribute. I would like it very much if it would also be displayed on the values (on the right column in the detailed view and on the whole column in the list view), since we are using the tooltips to define the units of the attribute and it would be nice to pop up when you hover a value.
As for the comment it would be nice to have a flag to also show the comment on the detailed view while looking at an entry. At the moment it is only showed when creating a new entry. Again we use this field to define the units.
This is an example of how we use these options:
attributes = Fill Number, Beam Current, Beam Energy, Beam Lifetime, RF Voltage S2, RF Voltage S4, RF Frequency, Synchrotron Frequency
Comment Beam Current = in mA
Comment Beam Energy = in GeV
Comment Beam Lifetime = in hh:mm
Comment RF Voltage S2 = in kV
Comment RF Voltage S4 = in kV
Comment RF Frequency = in MHz
Comment Synchrotron Frequency = in kHz
Tooltip Beam Current = in mA
Tooltip Beam Energy = in GeV
Tooltip Beam Lifetime = in hh:mm
Tooltip RF Voltage S2 = in kV
Tooltip RF Voltage S4 = in kV
Tooltip RF Frequency = in MHz
Tooltip Synchrotron Frequency = in kHz
Cheers
eddy |
Suggestion for tooltips and/or comments, posted by Edmund Hertle on Tue Sep 22 14:56:37 2015
|
Hey,
if you define a Tooltip at the moment it is only displayed on the attribute. I would like it very much if it would also be displayed on the values (on the right column in the detailed view and on the whole column in the list view), since we are using the tooltips to define the units of the attribute and it would be nice to pop up when you hover a value.
As for the comment it would be nice to have a flag to also show the comment on the detailed view while looking at an entry. At the moment it is only showed when creating a new entry. Again we use this field to define the units.
This is an example of how we use these options:
attributes = Fill Number, Beam Current, Beam Energy, Beam Lifetime, RF Voltage S2, RF Voltage S4, RF Frequency, Synchrotron Frequency
Comment Beam Current = in mA
Comment Beam Energy = in GeV
Comment Beam Lifetime = in hh:mm
Comment RF Voltage S2 = in kV
Comment RF Voltage S4 = in kV
Comment RF Frequency = in MHz
Comment Synchrotron Frequency = in kHz
Tooltip Beam Current = in mA
Tooltip Beam Energy = in GeV
Tooltip Beam Lifetime = in hh:mm
Tooltip RF Voltage S2 = in kV
Tooltip RF Voltage S4 = in kV
Tooltip RF Frequency = in MHz
Tooltip Synchrotron Frequency = in kHz
Cheers
eddy |
elog client overwriting attached files when editing existing log, posted by Joseph McKenna on Wed Sep 16 01:27:20 2015
|
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
|
|