ELOG Forum

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.

1330

Tue Jul 26 16:50:59 2005

Re: hide attributes when view the logbook

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.

1335

Tue Jul 26 20:23:33 2005

Re: New and reply pages don't use Page Title

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.

1336

Tue Jul 26 20:32:02 2005

Re: Restrict Top Groups to logged-in users?

Chris Green wrote:

I'd like to be able to prevent non-logged-in users from seeing what logbooks exist in a top group. Currently it seems that one is only required to log in once one has chosen a logbook. Is this possible?

To protect the logbook selection page, you put the "password file = <file>" into the [global] section or the [global <top group>] section. So "hide" the top group selection page, you put a "show top groups = 0" into the [global] section.

1337

Tue Jul 26 20:35:45 2005

Re: hide attributes when view the logbook

Juliana Peng wrote:

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.

Use "list display = <attribute list>" to specify which attributes to show in the listing page. RTFM.

1340

Tue Jul 26 21:11:31 2005

Re: Restrict Top Groups to logged-in users?

Chris Green wrote:

I already had the "password file = <file>" in the [global <top group>] section but I was still able to see the logbooks in that section. Moving the password line to [global] and / or setting Show Top Groups = 0 helped. Am I doing something wrong?

If you move the "password file = <file>" entry around, you can get fooled by stored cookies. So after each modification, make sure to delete all cookies in your browser.

1344

Wed Jul 27 09:07:17 2005

Re: hide attributes when view the logbook

Juliana Peng wrote:

But is there a way to control to hide or view the attributes? so that we don't need to change the elog.conf file each time.

For example, add a menu "expend" in "Find menu commands", we can click to view all the attributes or just view the attributes defined in "List Display"

Or use "{1} List Display = ....", we can view all the attributes at list page, but if selecting SunOS, only show attributes in List Display

In that case I would suggest two separate logbooks, for for SunOS and one for others. This way you can manage two separate sets of attributes.

Goto page Previous 1, 2, 3 ... 196, 197, 198 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6