Re: Can't set Author attribute properly in reply?, posted by Stefan Ritt on Tue Jul 26 10:51:12 2005
|
| Emiliano Gabrielli wrote: | | Substitute is the only way I have to be assure it is as I want ... |
No, that's not true. A
Locked attributes = Author
will do the job as well. |
|
Re: Can't set Author attribute properly in reply?, posted by Emiliano Gabrielli on Tue Jul 26 10:55:03 2005
|
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | | Substitute is the only way I have to be assure it is as I want ... |
No, that's not true. A
Locked attributes = Author
will do the job as well. |
I can't argue how it works ...
The following code will assure that, if the HTML generated by elog would be modified by hand by a malicious user the server can still preset the author field with the right $long_name?
Locked attributes = Author
Preset on Reply Author = $long_name
how works in details the "Locked Attribute" parameter then ?? ... |
|
Re: Can't set Author attribute properly in reply?, posted by Stefan Ritt on Tue Jul 26 10:59:45 2005
|
| Emiliano Gabrielli wrote: | | The following code will assure that, if the HTML generated by elog would be modified by hand by a malicious user the server can still preset the author field with the right $long_name? |
Ok, you're right. But that requires quite some knowledge to change the generated HTML by hand. So for paranoiac people the "Subst" might be better. Actually you could have both the "Preset on Reply" and the "Subst on Reply", so on the reply entry form one sees already the correct author. |
|
Re: Can't set Author attribute properly in reply?, posted by Emiliano Gabrielli on Tue Jul 26 12:02:35 2005
|
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | | The following code will assure that, if the HTML generated by elog would be modified by hand by a malicious user the server can still preset the author field with the right $long_name? |
Ok, you're right. But that requires quite some knowledge to change the generated HTML by hand. So for paranoiac people the "Subst" might be better. Actually you could have both the "Preset on Reply" and the "Subst on Reply", so on the reply entry form one sees already the correct author. |
It's my actual configuration infact  |
Re: hide attributes when view the logbook, posted by Juliana Peng on Tue Jul 26 16:44:41 2005 
|
| Stefan Ritt wrote: |
| Juliana Peng wrote: | | Thanks so much. But the new feature seems not working. |
Are you sure you got the latest CVS version and recompiled correctly?
I tried with following config:
[global]
port = 8080
[demo]
Attributes = Name, SysAdmin, OS, Manufacturer, Model, Serial Number, Description, Main Function, Location, Memory, CPU Speed, Num CPU, Owner, Contact Name, Contact Phone, Contact Email, Bought From, Bought Date, Maintenance, Network Drop, Console Drop
Options OS = SunOs{1}, Linux{2}, Aix
{1} Show Attributes = Name, SysAdmin, OS, Manufacturer, Model, Serial Number, Description
Then I added two entries, where OS = SunOS and Aix. As soon as I select SunOS, the attributes except those listed in {1} disappear. The same is true then for the single entry display. Here is the one with the Aix:
and here with SunOS:
So can you reproduce this? |
Thanks. But what I want is to hide the unwanted attributes at summary view, not just hide them when I click on entry.
Here is the example, can i hide the attributes at this page when I select SunOS:
 |
|
Re: hide attributes when view the logbook, posted by Stefan Ritt on Tue Jul 26 16:50:59 2005
|
| Juliana Peng wrote: | | Thanks. But what I want is to hide the unwanted attributes at summary view, not just hide them when I click on entry. |
No you can't do that.
Assume that you have different types of entries, ones where your unwanted attributes are missing and ones where they are present. If you would hide them, they would be missing even for the entries where you want them. Or you would change the table layout for every line, meaning that attributes which are common in all entries do not line up nicely below each other.
An other approach would be to make elog hide those columns which do not contain any value in the whole page, but that is not (yet) implemented. |
|
Re: hide attributes when view the logbook, posted by Juliana Peng on Tue Jul 26 17:28:31 2005
|
| Stefan Ritt wrote: |
| Juliana Peng wrote: | | Thanks. But what I want is to hide the unwanted attributes at summary view, not just hide them when I click on entry. |
No you can't do that.
Assume that you have different types of entries, ones where your unwanted attributes are missing and ones where they are present. If you would hide them, they would be missing even for the entries where you want them. Or you would change the table layout for every line, meaning that attributes which are common in all entries do not line up nicely below each other.
An other approach would be to make elog hide those columns which do not contain any value in the whole page, but that is not (yet) implemented. |
I may have all the attributes in logbook to keep a full record of all the machine. But for daily use, some of the attibutes we are not using so often. Too many attributes will make the window so big that can not be hold in one screen which is the reason why I want to hide some of them. Of course the hidden attributes have data, but those data are rarely used so we'd rather hide them.
Since "show attributes" prevent from inputing attributes, may not be suitable in this case. We appreciate if you can impletement a new feature like "view attibutes" which do not affect adding new entry, just hide attributes at summary view. |
|
Re: New and reply pages don't use Page Title, posted by Stefan Ritt on Tue Jul 26 20:23:33 2005
|
| Chris Green wrote: | | I'd like every page associated with a particular logbook to use that logbook's page title as at least part of its own. |
On the list page, you can use "summary page title = <title>". Since this option is misleading, I renamed it to "List page title = <title>". Then I added "edit page title = <title>". Modifications are in CVS.
| Chris Green wrote: | | Also, is it possible to have a reply comment in the same way as one has a message comment? |
I added "reply comment = <comment>"
So, that gave another two options. With all that many options it's hard to read through the configuration documentation. So if you have time and fun doing it, you could restructure the documentation page into some separate pages, to give people a better overview. Please send the modified pages back to me and I will include them on the web site. |
|