-
-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Smarty modifier - stop using isset to check taxTerm #22323
Conversation
(Standard links)
|
b947cfa
to
e949b90
Compare
As expected a swag of test fails on notices (since I haven't added the assign yet) api_v3_ContributionPageTest.testSubmitContributionPageWithPriceSetQuantity with data set #0 |
d72079c
to
6ec4dda
Compare
6ec4dda
to
74229a4
Compare
I'm thinking this should fail on some notices on CI - so will follow with the fix
7f05fb6
to
2e9b470
Compare
I do wonder about making this a domain token - I go back & forth a bit but as a domain token it would be available in non-smarty contexts too & could be exported
2e9b470
to
b8fe55c
Compare
This looks good. Merging per discusson with @seamuslee001 |
Overview
Smarty modifier - stop using isset to check taxTerm. This works by adding a new domain token (domain.tax_term) and exporting it as the smarty variable
$taxTerm
to the smarty layer.Before
Use of isset - which doesn't work with default modifiers
After
$taxTerm
is always assigned (as an empty string if none exists). In addition it is available as a tomain token.Technical Details
Adding it as a domain token helps to keep our logic in the tokens layer and makes it avialable from non-workflow templates. Realistically people likely would write it in in letters but if being copied from one site to another or used in a multisite it would make sense.
Comments