Skip to content

Consolidation of Mautic Form Types#291

Open
patrykgruszka wants to merge 2 commits intomautic:5.xfrom
patrykgruszka:MTC-9688_remove-form-types-docs
Open

Consolidation of Mautic Form Types#291
patrykgruszka wants to merge 2 commits intomautic:5.xfrom
patrykgruszka:MTC-9688_remove-form-types-docs

Conversation

@patrykgruszka
Copy link
Member

Description

Remove form type distinctions (Standalone Forms vs Campaign Forms) from Mautic 7.1 documentation. All forms now have unified capabilities: triggering campaigns and accessing the full range of form actions without type selection.

Linked issue

mautic/mautic#15803

Screenshots or screen recordings

@patrykgruszka patrykgruszka requested a review from a team as a code owner January 28, 2026 11:33
@patrykgruszka patrykgruszka requested review from adiati98 and favour-chibueze and removed request for a team January 28, 2026 11:33
@adiati98 adiati98 added this to the 7.x milestone Jan 28, 2026
Copy link
Contributor

@adiati98 adiati98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR, @patrykgruszka!

We need to address the Vale warning here. 🙂

Co-authored-by: Ayu Adiati <45172775+adiati98@users.noreply.github.com>
* - ``formType``
- string
- Applicable values are ``standalone`` or ``campaign``.
- **Deprecated.** Previously indicated whether a Form was a Standalone or a Campaign. As of Mautic 7.1, all Forms function identically. Mautic 8.0 schedules the removal of this property.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mautic/core-team @RCheesley a question here. Do we need to mention Mautic 8.0 here?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It won't hurt but we have different docs like https://github.com/mautic/mautic/blob/7.x/UPGRADE-7.0.md to document breaking changes. So i guess we should start one for M8.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will need to be based on the 7.1 branch indeed - we should add a warning in 7.1 and then in the 8.0 branch it would be removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants