Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 328 of 808  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6460 Entries 
Goto page Previous  1, 2, 3 ... 327, 328, 329 ... 806, 807, 808   Next  
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  69411   Mon Nov 15 11:48:25 2021 Reply Chris Körnerchris.koerner@physik.uni-halle.deBug reportWindows3.14Re: Restrict edit time = 0 behavior intended?

Actually this is related to post 68993 from Sebastian Schenk in Jul 2019. Are there any new workarounds I may have missed?

Chris Körner wrote:

Hi,

I have set the options "Restrict edit time = 24" and "Admin restrict edit time = 0" in [global]. This way can only edit entries for 24 hours while the admin can forever. I now want a single logbook where all users have unlimited time to edit entries. However, setting "Restrict edit time = 0" in this specific logbook behaves differently to the admin setting as it simply sets the time to 0. Is this behavior intended or a bug? I guess a workaround is to specify the edit limitation not in global but in all logbooks seperately.

 

  69412   Mon Nov 15 14:02:42 2021 Reply Sebastian Schenksebastian.schenk@physik.uni-halle.deBug reportWindows3.14Re: Restrict edit time = 0 behavior intended?

Hi Chris,

my old entry was related to the admin options of edit time.
The option "Admin restrict edit time" was implemented later, see ab8b98c

As a workaround you should be able to give "Restrict edit time" a ridiculous high number in the specific logbook, which should overwrite the global.
In the documentation is no rule specified for diabling global settings for specific logbooks, as far as i know.

Best wishes,
Sebastian

 

Chris Körner wrote:

Actually this is related to post 68993 from Sebastian Schenk in Jul 2019. Are there any new workarounds I may have missed?

Chris Körner wrote:

Hi,

I have set the options "Restrict edit time = 24" and "Admin restrict edit time = 0" in [global]. This way can only edit entries for 24 hours while the admin can forever. I now want a single logbook where all users have unlimited time to edit entries. However, setting "Restrict edit time = 0" in this specific logbook behaves differently to the admin setting as it simply sets the time to 0. Is this behavior intended or a bug? I guess a workaround is to specify the edit limitation not in global but in all logbooks seperately.

 

 

  69416   Tue Nov 16 15:14:42 2021 Reply Chris Körnerchris.koerner@physik.uni-halle.deBug reportWindows3.14Re: Restrict edit time = 0 behavior intended?

Hi Sebastian,

thanks for the reply. It is just a bit confusing that these similar settings behave so differently. For me it is no big deal to set the time for every logbook independently instead of [global], but it leaves more room for configuration errors.

Best,
Chris

Sebastian Schenk wrote:

Hi Chris,

my old entry was related to the admin options of edit time.
The option "Admin restrict edit time" was implemented later, see ab8b98c

As a workaround you should be able to give "Restrict edit time" a ridiculous high number in the specific logbook, which should overwrite the global.
In the documentation is no rule specified for diabling global settings for specific logbooks, as far as i know.

Best wishes,
Sebastian

 

Chris Körner wrote:

Actually this is related to post 68993 from Sebastian Schenk in Jul 2019. Are there any new workarounds I may have missed?

Chris Körner wrote:

Hi,

I have set the options "Restrict edit time = 24" and "Admin restrict edit time = 0" in [global]. This way can only edit entries for 24 hours while the admin can forever. I now want a single logbook where all users have unlimited time to edit entries. However, setting "Restrict edit time = 0" in this specific logbook behaves differently to the admin setting as it simply sets the time to 0. Is this behavior intended or a bug? I guess a workaround is to specify the edit limitation not in global but in all logbooks seperately.

 

 

 

  66245   Tue Mar 10 16:33:52 2009 Cool Heinzmanncatman333@web.deQuestionMac OSXV2.7.5-217Re: Restrict edit - issue

Heinzmann wrote:
Problem solved, I had to set the 'preset funktion' additionally

 

  66270   Wed Mar 25 10:35:59 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSXV2.7.5-217Re: Restrict edit - issue

 

Heinzmann wrote:

Hello,

please could you help me.

The Restrict edit funktion is not working. Because my user Dirk is able to edit/delete the text from user Peter:

 via select and edit.

Delete the - keep original text here - and then submit.

The whole text disappeared from the user Peter

I have tried both Restrict edit = 0 and then Restrict edit = 1 

Please note my config:

 

[global]
port = 80
Password file = C:\Program Files\ELOG\test.txt
Admin user = admin3
Self register = 1
Login expiration = 0

[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Login user = Peter, Dirk, Kervin, Frank, MichaelH
Password file = C:\Program Files\ELOG\user.txt
Self register = 1
Login expiration = 0
Restrict edit = 0

 

Thanks

 

First, you need "Restrict edit = 1" in your config file. Then for each edit operation the system checks the currently logged in user against the "Author" attribute. Therefore, the "Author" attribute must contain the full user name. This can be achieved by adding

Preset Author = $long_name
Locked Attributes = Author

as described in the manual.

  1336   Tue Jul 26 20:32:02 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.0bRe: 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.
  1338   Tue Jul 26 20:51:10 2005 Reply Chris Greengreenc@fnal.govRequestLinux2.6.0bRe: Restrict Top Groups to logged-in users?

Stefan Ritt wrote:

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.


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. Neither moving the password line to [global] nor setting Show Top Groups = 0 helped. Am I doing something wrong?

Thanks,
Chris.
  1340   Tue Jul 26 21:11:31 2005 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.0bRe: 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.
Goto page Previous  1, 2, 3 ... 327, 328, 329 ... 806, 807, 808   Next  
ELOG V3.1.5-3fb85fa6