Re: Addition of a "Restrict edit attribute" option?, posted by Justin Ellison on Wed Mar 14 15:03:41 2007
|
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.
That make more sense?
Justin |
|
Re: Addition of a "Restrict edit attribute" option?, posted by Stefan Ritt on Wed Mar 14 15:06:27 2007
|
| 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. |
|
Re: Addition of a "Restrict edit attribute" option?, posted by Justin Ellison on Wed Mar 14 15:43:51 2007
|
| Stefan Ritt wrote: |
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. |
Now I understand what you were getting at. Sorry for the confusion. That should work fine for us - unlocking is something that shouldn't ever happen.
Thanks for the quick response!
Justin |
|
Re: submit modified elog entry, posted by Stefan Ritt on Mon Mar 19 19:51:26 2007
|
| 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. |
|
Re: Private logbook - no guest access?, posted by Stefan Ritt on Tue Mar 20 13:48:50 2007
|
| 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. |
|
Re: Private logbook - no guest access?, posted by Ben Shepherd on Tue Mar 20 14:42:05 2007
|
| Stefan Ritt wrote: |
| 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. |
Thanks! I actually saw that in the config documentation, but I had assumed that it didn't work. Turns out I'd left those two options in my [global] section as well. Oops! |
Re: sort attributs, posted by deletoille on Wed Mar 21 16:51:14 2007 
|
| Stefan Ritt wrote: |
| 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. |
thanks, It works but the order "?sort" seems to works only in summary view (attachment 1) and not in threaded (attachement 2) view.
Any idea? |
|
Re: Global "MOptions", posted by Stefan Ritt on Mon Mar 26 13:03:05 2007
|
| Fergus Lynch wrote: | | Would it be an option to have Global "MOptions" - perhaps configured in the 'global options' file - which can be called up and referenced in all logbooks? |
Sure, that's possible alreay with the current version. Just put your MOptions statement under [global] and it will be used in all logbooks. If a specific logbook uses different MOptions, put the a second MOptions list under that logbook's section and it will overwrite the global setting. |