| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69236
|
Tue Oct 20 08:24:20 2020 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | latest | Re: Field values dependent on other selections | Look in the manual under "conditional attributes"
Stefan
| Anthony Krishock wrote: |
|
All,
I would like to know if there is a way in elog to populate a field based on the value of another field. What I want to do is have a field with a few selections (a menu) and another text field that populates based on what I select from the menu.
Is this possible?
|
|
|
69238
|
Tue Oct 20 16:05:40 2020 |
 | Bruno Schuler | bruno.schuler@empa.ch | Question | Windows | 3.1.4-2 | Upload attachment with py_elog | Hello,
How can one add an attachment to a new or existing entry with py_elog?
E.g. if I want to upload an image.
Thanks for the help! |
|
Draft
|
Wed Oct 21 02:26:32 2020 |
| Anthony Krishock | ajkrishock@verizon.net | Question | Windows | latest | Re: Field values dependent on other selections | Thanks for your suggestion.. Is it possible to, once
| Stefan Ritt wrote: |
|
Look in the manual under "conditional attributes"
Stefan
| Anthony Krishock wrote: |
|
All,
I would like to know if there is a way in elog to populate a field based on the value of another field. What I want to do is have a field with a few selections (a menu) and another text field that populates based on what I select from the menu.
Is this possible?
|
|
|
|
69245
|
Wed Oct 21 02:27:43 2020 |
| Anthony Krishock | ajkrishock@verizon.net | Question | Windows | latest | Re: Field values dependent on other selections | Thanks for your suggestion. Right now, my log is configured as follows:
Options Eyepiece = Pentax{a}, TeleVue{b}, Meade{c}
{a} Options Pentax = 5mm, 20mm, 30mm
{b} Options TeleVue = 7mm Nagler, 10mm Radian, 24mm Panoptic
{c} Options Meade = 8.8mm UWA, 14mm UWA, 26mm QX
If I select "Pentax", I would like the other two options to be unavailable. Instead, all three options are shown. Can I mask the other unused options?
| Stefan Ritt wrote: |
|
Look in the manual under "conditional attributes"
Stefan
| Anthony Krishock wrote: |
|
All,
I would like to know if there is a way in elog to populate a field based on the value of another field. What I want to do is have a field with a few selections (a menu) and another text field that populates based on what I select from the menu.
Is this possible?
|
|
|
| Attachment 1: Capture.JPG
|
|
|
69248
|
Fri Oct 23 15:10:54 2020 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | latest | Re: Field values dependent on other selections | Instead of using three different options you could use the same:
Options Eyepiece = Pentax{a}, TeleVue{b}, Meade{c}
{a} Options Form = 5mm, 20mm, 30mm
{b} Options Form = 7mm Nagler, 10mm Radian, 24mm Panoptic
{c} Options Form = 8.8mm UWA, 14mm UWA, 26mm QX
It makes more sense.
But it is as well possible to supress attributed in the edit from. See
Show Attributes = <list>
Attributes present in this list are shown in the single entry page. Omitting attributes can make sense for attributes which are automatically derived from other attributes via the Change <attribute> command.Show Attributes Edit = <list>
The same as Show Attributes, but for the entry form.
You just have a different <list> for each conditional case {a} {b} {c}.
| Anthony Krishock wrote: |
|
Thanks for your suggestion. Right now, my log is configured as follows:
Options Eyepiece = Pentax{a}, TeleVue{b}, Meade{c}
{a} Options Pentax = 5mm, 20mm, 30mm
{b} Options TeleVue = 7mm Nagler, 10mm Radian, 24mm Panoptic
{c} Options Meade = 8.8mm UWA, 14mm UWA, 26mm QX
If I select "Pentax", I would like the other two options to be unavailable. Instead, all three options are shown. Can I mask the other unused options?
| Stefan Ritt wrote: |
|
Look in the manual under "conditional attributes"
Stefan
| Anthony Krishock wrote: |
|
All,
I would like to know if there is a way in elog to populate a field based on the value of another field. What I want to do is have a field with a few selections (a menu) and another text field that populates based on what I select from the menu.
Is this possible?
|
|
|
|
|
69262
|
Tue Dec 1 02:12:14 2020 |
| Harry Martin | harrymartin772@gmail.com | Bug report | Windows | 2.7.7-2246 | Re: Change / List Change doen't work anymore? |
| Stefan Ritt wrote: |
| Holger Mundhahs wrote: | Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my .cfg file I've:
In the old ELOG version I've "RIB-Board" as text in the page and the link works well. But now there is the following code generated:
Is the syntax changed from 2.7.0 to 2.7.7? What's the correct syntax for 2.7.7?
|
For security reasons (XSS or cross site scripting) , HTML code in attributes is not allowed by default. To turn it on (and if you know what you are doing), add following line to your configuration
Allow HTML = 1 |
I know this is an old, old thread, but I am trying to use this feature in a recent version of elog (3.1.3). Is there any chance this will ever get fixed, or at least made workable? I tried "Allow HTML = 1", but that did not work. I'd like to be able to use this to link directly to carriers to track packages.
Also, the documentation seemed a bit confusing to me:
| Quote: | Change <attribute> = <string>
Instead of subsituting an attribute, the original attribute can be kept and just the output formatting can be changed. This can be very handy for constructing HTML links out of attributes. Presume that a company has a telephone book reachable under
http://any.company.com/telbook.cgi?search=<name>
where <name> has to be replaced by a search string. Now one can construct an automatic telephonebook lookup with following options:
Attributes = Name, Telephone, ...
Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>
The attribute Telephone is now automatically constructed from the attribute Name and consists of a link to the company's telephonebook. The advantage of this system is if the URL of the telephonebook changes one day, only one statement in the config file has to be changed, while otherways (like with the Subst Telephone = ... option) all entries would have to be changed manually. |
The example seems to be using a different syntax ("Display Telephone") rather than the syntax described by the section header ("Change <attribute>...").
Any update to this information would be greatly appreciated. I'm just looking for a workable solution of any kind. Thank you for your continuing fine work. |
|
69263
|
Tue Dec 1 02:39:45 2020 |
| Harry Martin | harrymartin772@gmail.com | Bug report | Windows | 2.7.7-2246 | Re: Change / List Change doen't work anymore? |
| Harry Martin wrote: |
| Stefan Ritt wrote: |
| Holger Mundhahs wrote: | Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my .cfg file I've:
In the old ELOG version I've "RIB-Board" as text in the page and the link works well. But now there is the following code generated:
Is the syntax changed from 2.7.0 to 2.7.7? What's the correct syntax for 2.7.7?
|
For security reasons (XSS or cross site scripting) , HTML code in attributes is not allowed by default. To turn it on (and if you know what you are doing), add following line to your configuration
Allow HTML = 1 |
I know this is an old, old thread, but I am trying to use this feature in a recent version of elog (3.1.3). Is there any chance this will ever get fixed, or at least made workable? I tried "Allow HTML = 1", but that did not work. I'd like to be able to use this to link directly to carriers to track packages.
Also, the documentation seemed a bit confusing to me:
| Quote: | Change <attribute> = <string>
Instead of subsituting an attribute, the original attribute can be kept and just the output formatting can be changed. This can be very handy for constructing HTML links out of attributes. Presume that a company has a telephone book reachable under
http://any.company.com/telbook.cgi?search=<name>
where <name> has to be replaced by a search string. Now one can construct an automatic telephonebook lookup with following options:
Attributes = Name, Telephone, ...
Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>
The attribute Telephone is now automatically constructed from the attribute Name and consists of a link to the company's telephonebook. The advantage of this system is if the URL of the telephonebook changes one day, only one statement in the config file has to be changed, while otherways (like with the Subst Telephone = ... option) all entries would have to be changed manually. |
The example seems to be using a different syntax ("Display Telephone") rather than the syntax described by the section header ("Change <attribute>...").
Any update to this information would be greatly appreciated. I'm just looking for a workable solution of any kind. Thank you for your continuing fine work. |
I am able to make it work by passing just a plain string constructing the URL. Strange though... before I posted the previous log entry, it didn't work no matter what I tried! Bizarre.
However, it would still be a good idea to update the documentation to clarify things somewhat and bring it up to date with actual usage today. |
|
69264
|
Tue Dec 1 22:57:25 2020 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Windows | 2.7.7-2246 | Re: Change / List Change doen't work anymore? |
| Harry Martin wrote: |
| Harry Martin wrote: |
| Stefan Ritt wrote: |
| Holger Mundhahs wrote: | Hello @all,
I'm not sure if this is a bug, but after upgradeing from 2.7.0 to 2.7.7 the Change <attribute> and List Change <attribute> doesn't work anymore. In my .cfg file I've:
In the old ELOG version I've "RIB-Board" as text in the page and the link works well. But now there is the following code generated:
Is the syntax changed from 2.7.0 to 2.7.7? What's the correct syntax for 2.7.7?
|
For security reasons (XSS or cross site scripting) , HTML code in attributes is not allowed by default. To turn it on (and if you know what you are doing), add following line to your configuration
Allow HTML = 1 |
I know this is an old, old thread, but I am trying to use this feature in a recent version of elog (3.1.3). Is there any chance this will ever get fixed, or at least made workable? I tried "Allow HTML = 1", but that did not work. I'd like to be able to use this to link directly to carriers to track packages.
Also, the documentation seemed a bit confusing to me:
| Quote: | Change <attribute> = <string>
Instead of subsituting an attribute, the original attribute can be kept and just the output formatting can be changed. This can be very handy for constructing HTML links out of attributes. Presume that a company has a telephone book reachable under
http://any.company.com/telbook.cgi?search=<name>
where <name> has to be replaced by a search string. Now one can construct an automatic telephonebook lookup with following options:
Attributes = Name, Telephone, ...
Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>
The attribute Telephone is now automatically constructed from the attribute Name and consists of a link to the company's telephonebook. The advantage of this system is if the URL of the telephonebook changes one day, only one statement in the config file has to be changed, while otherways (like with the Subst Telephone = ... option) all entries would have to be changed manually. |
The example seems to be using a different syntax ("Display Telephone") rather than the syntax described by the section header ("Change <attribute>...").
Any update to this information would be greatly appreciated. I'm just looking for a workable solution of any kind. Thank you for your continuing fine work. |
I am able to make it work by passing just a plain string constructing the URL. Strange though... before I posted the previous log entry, it didn't work no matter what I tried! Bizarre.
However, it would still be a good idea to update the documentation to clarify things somewhat and bring it up to date with actual usage today. |
You are referring here to a Forum entry for an old ELOG version: this will not be changed, since it was for that old version.
If you want some documentation to be updated, then you should show the documentation part that should be updated. |
|