FIO-9992: check for server when triggering the captcha#6085
Merged
brendanbond merged 2 commits intomasterfrom Apr 9, 2025
Merged
FIO-9992: check for server when triggering the captcha#6085brendanbond merged 2 commits intomasterfrom
brendanbond merged 2 commits intomasterfrom
Conversation
johnformio
approved these changes
Apr 9, 2025
lane-formio
pushed a commit
that referenced
this pull request
Apr 10, 2025
FIO-9992: check for server when triggering the captcha
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Link to Jira Ticket
https://formio.atlassian.net/browse/FIO-9992
Description
We're still using @formio/js for email rendering on the server (soon to change!) and it appears that the captcha trigger is causing problems, namely because the Captcha component appears to the server as a Hidden component. I'm not sure if this is because the vm library is not properly loading premium components or what, but because this is a blocker right before release and because presumably you shouldn't need to trigger the captcha component just to render an email, I've gone ahead and gated the captcha trigger to client-side stuff only.
Breaking Changes / Backwards Compatibility
n/a
Dependencies
n/a
How has this PR been tested?
n/a
Checklist: