Re: Change default for suppressing email notification and/or targeting entries manually, posted by Stefan Ritt on Thu Jun 22 21:02:16 2006
|
| Alan Stone wrote: | | However, I want to invert the default check box, so that no email is sent to subscribers unless someone takes the extra step to check a box which might read "Send Email notification". |
Ahh, now I understand 
Suppress default =1
should do the job. |
|
Re: Change default for suppressing email notification and/or targeting entries manually, posted by Stefan Ritt on Tue May 1 16:54:12 2007
|
| Alan Stone wrote: | | I would also like the option to add additional email addresses on the fly. |
There is a simple way to accomplish this. Define a new attribute, let's call it "cc". Then add to your config file following statement:
Email all = $cc
In you entry form, you can now enter comma-separated email addresses in the CC filed, to which a notification will be sent. |
|
Re: Change column width in list mode?, posted by Stefan Ritt on Wed Dec 4 10:37:32 2019
|
You need
.listframe td:nth-child(3) {
min-width: 250px;
}
/Stefan
| David Wallis wrote: |
|
In some of our logbooks, some columns are very narrow, which makes their content difficult to read. I have tried adding a custom css file like this:
listframe td:nth-child(3) {
width: 250px;
}
But I find that the column width does not change. I have verified via element inspection that the width attribute is active on the correct column (td).
Am I doing someting wrong, or is this not possible?
|
|
|
Re: Change column width in list mode?, posted by David Wallis on Fri Dec 6 15:40:19 2019
|
Awesome, thank you!
| Stefan Ritt wrote: |
|
You need
.listframe td:nth-child(3) {
min-width: 250px;
}
/Stefan
| David Wallis wrote: |
|
In some of our logbooks, some columns are very narrow, which makes their content difficult to read. I have tried adding a custom css file like this:
listframe td:nth-child(3) {
width: 250px;
}
But I find that the column width does not change. I have verified via element inspection that the width attribute is active on the correct column (td).
Am I doing someting wrong, or is this not possible?
|
|
|
Re: Change background color, posted by Stefan Ritt on Mon Dec 8 08:59:56 2008 
|
| mike cianci wrote: |
|
I copied the following line from the ELOG documentation file to my config file (with the appropriate changes to the attribute and value fields) and nothing happens. Am I missing something?
Style importance severe = background-color:red
Thanks for all your help.
|
Just the "usual candidates":
- Any typo?
- Edited the wrong file?
- Must send a HUP signal to elogd if running under linux
- Note that the style changes only in the list display
I just tried with a minimal configuration file:
[demo]
Attributes = Author, Importance, Subject
Options Importance = normal, severe
Style Importance severe = background-color:red
and it just worked fine:
|
|
Re: Change / List Change doen't work anymore?, posted by Stefan Ritt on Thu Sep 17 18:32:59 2009
|
| 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 |
|
Re: Change / List Change doen't work anymore?, posted by Harry Martin on Tue Dec 1 02:12:14 2020
|
| 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. |
|
Re: Change / List Change doen't work anymore?, posted by Harry Martin on Tue Dec 1 02:39:45 2020
|
| 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. |
|