Thanks Jason,
I'm seeing some wacky behaviour from the Validations extension/plugin.
Manually insert your line of code:
$WAFV_Errors .= WAValidateLE(((isset($_POST["Security_Code_1"]))?strtolower($_POST["Security_Code_1"]):"") . "",((isset($_SESSION["captcha_Security_Code_1"]))?strtolower($_SESSION["captcha_Security_Code_1"]):"") . "",true,35);
WORKS!
Then reopen WA Server Validations and Check the settings which now show an ignore case sensitivity condition. Close and accept that and the extension re-renders the line of code as:
$WAFV_Errors .= WAValidateLE(((isset($_POST["Security_Code_1"]))?$_POST["Security_Code_1"]):"" . "",((isset($_SESSION["captcha_Security_Code_1"]))?$_SESSION["captcha_Security_Code_1"]):"" . "",true,35);
Fails - no longer using the String to Lower function and the parenthesis are out of place.
Manually fixing the issue as shown makes the page work:
$WAFV_Errors .= WAValidateLE(((isset($_POST["Security_Code_1"]))?$_POST["Security_Code_1"]:"") . "",((isset($_SESSION["captcha_Security_Code_1"]))?$_SESSION["captcha_Security_Code_1"]:"") . "",true,35);
WORKS!
So it looks as though there are two conditions; one checking case sensitivity and one not. Both can work but the rewrite in the extension fails to rewrite accurately.
Let's do another test removing the validation and resetting it fresh testing both case sensitivity options:
After removing the validation on the captcha and reentering it NOT case sensitive renders this code:
$WAFV_Errors .= WAValidateLE(strtolower($_SESSION['captcha_Security_Code_1']) . "",strtolower(((isset($_POST["Security_Code_1"]))?$_POST["Security_Code_1"]:"")) . "",true,35);
WORKS! - Not case sensitive
Next let's try removing and then adding back but as case sensitive:
$WAFV_Errors .= WAValidateLE(((isset($_POST["Security_Code_1"]))?$_POST["Security_Code_1"]:"") . "",((isset($_POST["Security_Code_1"]))?$_POST["Security_Code_1"]:"") . "",true,35);
WORKS! - BUT NOT case sensitive
Let's now try changing between the two:
Code renders properly but there is NO case sensitive condition. Maybe I am assuming that the opposite of Not Case Sensitive is actually being case sensitive?
The other issues seem related to proper refresh which has been an issue for years and more likely Adobe or Apples fault ( I do not know).
Screen shots attached showing the rendered code and also the view showing Not Case Sensitive being deselected and still allowing the showed string to pass as a successful validation.
