ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 188 of 806

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

6446 Entries

Goto page Previous 1, 2, 3 ... 187, 188, 189 ... 804, 805, 806 Next

Author Email down

Tue Mar 6 13:55:15 2007

Re: Conditional Email Notification by a text file

An Thai wrote:

Dear Stefan,

what i mean is that you maybe modify the setup file for Windows (elog-latest.exe) so that everybody can make change of -[options] while install Elog. I am not a Windows expert, but I think that a lot of software can be set or configurated at the first install time (For Example: Path destination, features avaible, ...)

Do you know if it is possible?

I don't know how to set-up the scheduled tasks from the installation script. Furthermore, having a application constantly running is somehow unusual, and it will confuse normal people. To my knowledge, not many people use the -x option under Windows. These people how really need it are clever enough (like you) to set-up the batch file manually.

2159

Thu Mar 8 08:08:42 2007

Re: Search all logbooks as default

An Thai wrote:

do you know how I can default set the option "Search all logbooks" in the Find page selected/checked?

I added the option

Search all logbooks = 2

which lets you do that. It's in the SVN version and will be contained in the next release.

2161

Mon Mar 12 20:35:17 2007

Re: Hiding attributes in Detail view?

Justin Ellison wrote:

The only thing that isn't working as I'd like is when someone views a log entry. Both Bug Number and Bugzilla show up in the attributes. This isn't a huge deal, it's just showing redundant data.

Is there a way to hide Bug Number on the view page?

In revision 1809 I implemented the options

Show attributes = ...
Show attributed edit = ...

The first one is for the log entry page, the second for the entry form. This way you can distinguish between the bug number and the link. The old option Hidden attributes has been dropped, since it has the same effect now as Show attributes edit.

2163

Tue Mar 13 20:58:07 2007

Re: Addition of a "Restrict edit attribute" option?

Justin Ellison wrote:

It would be a nice addition to have a config file option named "Restrict edit attribute".

Basically, I would like to have an attribute that was either:

a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.

Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.

Conditional attributes? Like:

Attributes = ..., Status
Options Status = Open{1}, Closed{2}

{2}Locked attributes = Status

Unfortunately once it's locked, the admin has to change the config file to unlock it.

2166

Wed Mar 14 12:06:20 2007

deletoille wrote:

For 1 event, I need the date and the hour of this one. An event can be enter in elog several days after this one. The problem is that I do not manage to carry out one sorts on these two attibuts. I tested the order “? rsort” but this one works only on one entry not out of 2 at the same time (? rsort=Heure+evenement, Date+evenement&mode=threaded)
have an easy way?

Yepp. Since you can only sort on a single attribute, you combine time and date into one. This can be done like following:

Attributes = Icone, Type def fiche, ..., Evenement
Type Evenement = datetime

Now you can not only sort on Evenement, but you get also a date picker for that attribute in the entry form. To format the way Evenement is displayed, use the Time format option.

2168

Wed Mar 14 15:06:27 2007

Re: Addition of a "Restrict edit attribute" option?

Justin Ellison wrote:

Sorry, I didn't explain it enough.

This feature is like "Restrict edit time", but instead of setting an entire entry as read only after n hours, we set it read only if attribute y is true. Admin would be able to go in and reset that attribute to false to unlock the entry for editing, but no one else would be able to.

I understand what you want. The conditional attributes I showed you give you that functionality, except that unlocking is a bit painful for the admin (has to edit the config file each time). Sorry, but that's all I can give you.

2170

Mon Mar 19 19:51:26 2007

Re: submit modified elog entry

deletoille wrote:

hello, I have small a bug,
when I create an entry. Per moment the program requires of me: "Submit modified Elog entry"
if I answer yes, Eog create 2 entry identical.
If I answer not it create only one.
I don't wait that elog asks me a confirmation

Are you sure about that? Can you reproduce it? I tried to reproduce it with the simple example logbook from the distribution, by adding the Use lock = 1 option to the configuration, but without success. I got only a single entry or no entry. You can of course remove the Use lock option, if you don't need locking.

2172

Tue Mar 20 13:48:50 2007

Re: Private logbook - no guest access?

Ben Shepherd wrote:

I want to set up a logbook which you have to be logged in to be able to read entries. I've already got three logbooks which can be viewed by anyone but only logged-in users can modify them. For the fourth one, I want to have a private logbook which can't be read by 'guest' users. Is this possible?

Per default, logbooks can only be read by logged in users if you use "password file = xxx". It is however possible to make these logbooks readable by 'guest' users if you use "Guest menu commands = xxx" and "Guest list menu commands = xxx". So just remove these two options from your fourth logbook and you get what you want.

Goto page Previous 1, 2, 3 ... 187, 188, 189 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6