[phorm] [Phorm:] Re: that worked, but another question...

  • From: webbbs@xxxxxxxxx
  • To: support@xxxxxxxxx
  • Date: 31 Mar 2004 04:38:14 -0000

The following new message has been posted on Phorm Support Forum at 
<http://www.phorm.com/support/>. 

*************************************************************************** 

  MESSAGE:  (#3929) Re: that worked, but another question... 
            <http://www.phorm.com/support/?rev=3929> 
  AUTHOR:   David Fisher 
  DATE:     March 30, 2004 at 11:38 p.m. EST 

  Reply To: (#3926) that worked, but another question... 
  Author:   Mary Ellen 
  Date:     March 30, 2004 at 9:40 a.m. EST 

You could use PHP's un-operator(!): 
$i != 0; 
would evaluate true only if $i was not equal to 0. 

Your rule might look like this: 
RULE: 1 
CRIT: REQ 
FFLD: field_name 
COND: $field_name != 0 

This rule would require that field_name had a value that was not equal to 0. 
You could string multiple un-equals and ORs together to accomplish your goal. 

> In making one thing easier, I managed to shoot myself 
> in the foot with the rules. 

> Instead of passing a literal to the config files, I 
> changed the form so it passes a number. Zero means the 
> field isn't in use, but the zero makes the rules file 
> think the field has been completed. What's the easiest 
> way around that? 

*************************************************************************** 

This is an automatically-generated notice.  If you'd like to be removed from 
the mailing list, please visit Phorm Support Forum at 
<http://www.phorm.com/support/>, or send your request to webbbs@xxxxxxxxxx  If 
you wish to respond to this message, please post your response directly to the 
board.  Thank you! 
-------------------------------------------------
You are receiving this message because you are subscribed to the Phorm mailing 
list. To send messages to the mailing list, simply send email to 
phorm@xxxxxxxxxxxxx from the address you have subscribed. You may unsubscribe 
from the list by sending email to phorm-request@xxxxxxxxxxxxx with 
'unsubscribe' in the SUBJECT field.

Other related posts:

  • » [phorm] [Phorm:] Re: that worked, but another question...