Difference between revisions of "NATS Common Errors"
Line 24: | Line 24: | ||
== Empty Payment Type Field == | == Empty Payment Type Field == | ||
+ | The payment type field goes missing if you don't have any cascades | ||
+ | selected. | ||
=== NATS3 === | === NATS3 === | ||
− | + | Go to [[Sites Admin]], click the Edit Cascades icon, mark | |
− | |||
one or more cascade checkboxes, and save. | one or more cascade checkboxes, and save. | ||
=== NATS4 === | === NATS4 === | ||
+ | Go to [[Billers Admin]], click on the purple 'rules' arrows for the cascade that should be used, and make sure there is a rule that will be valid with the details you are using. In many cases this will either be 'ALL' for all fields, or specific to the tour you are testing, and 'ALL' for the remaining fields. |
Revision as of 09:23, 14 June 2009
NATS 3
|
---|
The following list describes common errors.
Join Page Denial
If you get a denial page every time you visit a pre-join page, the page or its cascade is probably geo-targeted to prevent users from your country from signing up. Please see the Geo-Targeting Cascades article for more details.
Cascade Fail
If you get a denial page every time you visit a pre-join page or a particular step in a cascade, the page or its cascade is probably geo-targeted to prevent users from your country from signing up. Please see the Geo-Targeting Cascades article for more details.
Membership Not Available
"Sorry, but this Membership is not available for the chosen Payment Type."
This error occurs when that pricing option is not set up properly with the biller or the current cascade has no billers. Make sure the site's biller codes are correct and the current cascade has at least one biller in every cascade this site uses.
Empty Payment Type Field
The payment type field goes missing if you don't have any cascades selected.
NATS3
Go to Sites Admin, click the Edit Cascades icon, mark one or more cascade checkboxes, and save.
NATS4
Go to Billers Admin, click on the purple 'rules' arrows for the cascade that should be used, and make sure there is a rule that will be valid with the details you are using. In many cases this will either be 'ALL' for all fields, or specific to the tour you are testing, and 'ALL' for the remaining fields.