For [as what ... ], [switch field ... ], and [block field ... ], we are comparing against 11 of 1ShoppingCart's fields for capitalization.
The way this works is if something matches without the check, we use that. Otherwise, if the field we are trying to use is available in it's lowercase form, we will use that.
What won't work is to use the lower case version of the name within the shortcode.
Example: [as what="company"] will not work with an old form using Company, but it will respond to the new form's company.
Only [as what="Company"] will respond to both the old form's Company(preferred) and the new form's company.
I think this is acceptable, since what we recommend, and generate, is the capitalized version of the field.
For
[as what ... ]
,[switch field ... ]
, and[block field ... ]
, we are comparing against 11 of 1ShoppingCart's fields for capitalization.The way this works is if something matches without the check, we use that. Otherwise, if the field we are trying to use is available in it's lowercase form, we will use that.
What won't work is to use the lower case version of the name within the shortcode.
Example:
[as what="company"]
will not work with an old form usingCompany
, but it will respond to the new form'scompany
.Only
[as what="Company"]
will respond to both the old form'sCompany
(preferred) and the new form'scompany
.I think this is acceptable, since what we recommend, and generate, is the capitalized version of the field.