Temporary fix for frontend AfformTokens being generated incorrectly #31801
+10
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
On WordPress when you use the Afform "MessageTokens" it doesn't always generate the correct URLs.
Before
URLs generated incorrectly depending on context
After
URLs generated correctly.
Technical Details
Example:
https://mysite.com/myfirstform
.https://mysite.com/mysecondform
.It looks like:
https://mysite.com/myfirstform?civiwp=mysite.com/mysecondform&token=...
But should look like:
https://mysite.com/mysecondform?token=...
This is because the tokens code detects the referrer form and uses that as the frontend_url which we don't want in this case because the forms are completely separate.
Comments
Adding this as draft because it's a hacky proof of concept using \Civi::$statics to pass context through. But we should do it a better way.