Search the Community
Showing results for tags 'universal'.
Found 2 results
-
I am trying to understand how the examples in Error Checking (http://docs.blesta.com/display/dev/Error+Checking)relate to the JSON formated version of Input Rules in the Universal Module. All the examples in Error Checking are php arrays. The simple examples seem obvious, but how would the ones with functions be done in Input Rules? What is the correct way to validate an email address given the Service Option of admin_email? { "admin_email":{ "valid":{ "rule":["filter_var",["admin_email","FILTER_VALIDATE_EMAIL"]], "message":"Please enter a valid email address." } } } The above fires but fails with a valid address in the field. Why aren't there more examples in the docs for the JSON formatted Input Rules?
-
I am trying to set up Blesta 3.3 using the Customer Information Manager (CIM) within Authorize.net (which seems to be configured OK). I created an Order Form under Packages and set the type to Client Registration. The form asked for email, but the email did not pass through to CIM; Only the basic account information did. Is there a point of configuration to map the fields from Blesta to the payment gateway/CIM? Also when using CIM, what credit card information gets stored locally?
