Rule does not work

Hi,

what does not work here?

<?php

function WA_Auth_GetComparisonsForRule($ruleName){
	$comparisons = array();
	
	switch ($ruleName){
		case "hgAdmin":
			$comparisons[0] = array(FALSE, "".((isset($_SESSION['memberID']))?$_SESSION['memberID']:"")  ."", 4, "0");
			$comparisons[1] = array(TRUE, "".((isset($_SESSION['level']))?$_SESSION['level']:"")  ."", 1, "9");
			$comparisons[2] = array(FALSE, "".mktime()  ."", 5, "".((isset($_SESSION['logoutTime']))?$_SESSION['logoutTime']:"")  ."");
			break;
	}
	return $comparisons;	
}


function WA_Auth_GetGroup($groupName){
	$group = Array();
	
	switch($groupName){
	
	}

	return $group;
}

?>

This ist the logoutTime:

<?php
if (!session_id()) session_start();
if (isset($_POST["buttonLogin"]))     {
  $_SESSION["logoutTime"] = "".mktime(date("H"),date("i")+5,date("s"),date("m"), date("d"),date("Y"))  ."";
}
?>

The page does not redirect when mktime is over logoutTime :-(((

HEY!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



Its not working cause its on the 3 PLACE! whats that? If I put it on first position the page is close and the user is redirect!



HELLO!!!!!


FIX THAT PROBLEM!!!!!!!!!

  Corrected an issue that caused access rules with multiple conditions to completely fail as soon as the first condition was not met. Additional conditions will now process after an earlier condition fails.  

I use 1.1.8

Thing works!

I got 3 conditions...and the 3rd wont WORK, cause the 1st two work well! If I put the last in 1st position it works.

BUT CAN I BE SURE THE LAST TWO WORK WELL?

I cant sleep if I dont know that my CONDITIONS REALLY works.


PLEASE!

I think NO ONE is interessted in taht stuff!

If I do something wrong let me know!

It seems that you are having an issue getting your access rules to work correct? Please explain a little about the conditions of the rule, why you are setting them this way and what the result is when they are applied. The information that you have supplied is a little out of context and I will need some more of the details to help determine what is going wrong and why.

???

1. check if memberID is bigger 0
2. check if level is 9
3. check if the time is OVER then logout.

this way, ther is no outomatic LOGOUT when the time is over.
when the third is the first it works, so i think, there is something worng witht he extension.

what more do you need to know? the thing is, if the logouttime thing is in 3 position it does not work.

if its on first position it logs out after mktime is bigger than logoutTime.

just try.

Here is something to CHECK:

login.php

login2.php

both

test@test.de / test

look what happens, when reload the page after TIME is UP, thats not good quality!

Are you using "allow if" or "restrict if" when stacking your rules.

If you use "allow if" it will allow the user in as soon as they meet one requirement. If you use "restrict if" it will reject the user as soon as it fails one requirement.

My guess is that you have not applied it with that in mind and you expect that all three conditions would have to be met. You should probably be using:

"restrict if" member ID is less than 0
"restrict if" level does not equal 9
"restrict if" the time is over

is that what you have done?

1st.

allow if
allow if
restrict if

2nd.
restrict if
allow if
allow if


This is funny, you say i need to check the order? write it down in the manual, if so!

I thin, allow if, go to next, allow if, ok, go to next, restrict if, ok, go to next, allow if, FAILS, go LOGOUT!

if, not so, WRITE it in the MANUAL, that the rules directly BREAK if 1 thing allow if is OK.

stupid!

I'm actually not stupid... conservatively average intelligence. You don't have to change the order, you have to change the reaction to the conditions and how the conditions are termed (and possibly your tone).

you should use all "restrict if" in your case. Since "allow if" will "allow if" that line passes. It won't break, it will just do exactly what it says it will do and allow the user in if the condition passes. Your mistake (and possibly our documentation team's) is to think that all of the conditions are evaluated as a group, when really it goes line by line.

I'll suggest to our documentation team that this was not clear... Thank you for the not so elegant suggestion.