[6.x] Forms 2 - #15039
Draft
jasonvarga wants to merge 1017 commits into
Draft
[6.x] Forms 2#15039jasonvarga wants to merge 1017 commits into
jasonvarga wants to merge 1017 commits into
Conversation
…ype. The builder wraps it in Fallback, but was sending fieldtype: "fallback" back on save. The repository can't look up "fallback" as a real type, so validation blows up.
…ding, paragraph) had their own collapsed markup that skipped the shared compressed-view structure.
…nge and the category feels pretty different to choice
This reverts commit 237570d.
…m fieldtype. The builder wraps it in Fallback, but was sending fieldtype: "fallback" back on save. The repository can't look up "fallback" as a real type, so validation blows up." This reverts commit 1e759d5.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…15276) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…15332) Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
merging 6.x into forms-2 kept the rewritten `Condition.vue` wholesale, which dropped the change from #14593 that stopped excluding fields already used in another condition. the exclusion lived in the shared `Condition` component, so it blocked field conditions, form field logic and page rules alike. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Sy7LsNJGjpwE2ZNr8BphpQ
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q49Rea3WHrqiVjZ5azU7FG
…lected site (#15350) Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
The form builder already keeps fieldtype icons separate from field config. Remove the remaining backend filter so manually added icon values are preserved like other custom config keys. Add regression coverage for custom icon values and fieldtypes with an `icon` config field.
# Conflicts: # lang/en/messages.php
Forms 2 deleted the legacy text fieldtype's front-end views without porting the autocomplete attribute to the generic fallback views that now render it. The user blueprint still declares name/email as type text with autocomplete defaults, so those inputs were silently dropping autocomplete on user:profile_form and user:register_form. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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
4 participants
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.
Forms 2 is a complete overhaul of Statamic's forms functionality, including (but certainly not limited to):
sitethey're submitted fromSubmitFormaction to submit forms programmaticallyForms Pro
Forms Pro is a paid first-party addon adding extra features on top of Core, like multi-page forms, visualisations, an Address fieldtype with autocomplete, and integrations with popular email marketing tools.
Some of these features live in
cms, gated behind whether Forms Pro is installed. It also lifts the single form limit, so you can have more than one form without needing Statamic Pro.Pricing and other details will be announced when everything is released. Hold tight!
Breaking changes
Because Forms 2.0 is being released in a minor release, we've done our best to avoid breaking changes, migrating what we can to new formats automatically:
emailconfigs are converted into email connections.$form->blueprint()still works. It's now generated using the form's fields.The
configure form fieldspermission has been removed in favour of finer grained permissions. However, it's still supported for roles currently using it.Documentation: statamic/docs#1957
Eloquent Driver: statamic/eloquent-driver#612