How to test

• try to insert and save a value of zero as session time
• make sure no issues are reported
• apply the patch
• try zero again
• repeat the test with 1 and 2 as values (both should work)

Thanks @maxvalentini77

I still able to save negative value:

I think problem that there no backend validation for this input,
also filter="integer" allow negative value (that is valid),
min="1" have not much effect at least in my Chrome browser 😄

same problem with "Cache Time" in same configuration form

@maxvalentini77 I suggest to add filter="uint" as well to the field, though I don't see it as necessary.

@Fedik You are right, I'm working on a server side validation.
@izharaazmi Thanks for the tip!

Added number validator to check min/max range for number fields.
Added the validator to cachetime and session lifetime, both setted with min of 1.

RTC based on testing by @ChrisBreaks and @jonnyefftek on #jab15 #makeithappen

@test test resutls are: without patch applied, there's no error displayed and you can enter 0 inside "Session Lifetime " field. After applying the patch if you try to enter 0 as a value inside "Session Lifetime " field, you get this error: "Invalid field: Session Lifetime"

Merged with b649299 into 3.5-dev.

Thanks!

Is there a list of available JFormRules somewhere? If so that would need updated as we introduce a new one here.

@Bakual Should the doc block say @since xx.x?

I wrote xx.x in the attribute because i didn't know in which version this class will be introduced. Now should contain 3.5.0, right?

Correct @maxvalentini77 can you just send a quick PR that fixes that?

@zero-24 I create a new PR #7109 it's ok?

Awww. I usually don't look at the doc blocks close enough...

@zero-24 I create a new PR #7109 it's ok?

👍 Thomas allready merged it. Thanks