Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[UX] Change how the ways to implement a form are called #183

Merged
merged 3 commits into from
Jun 13, 2024
Merged

[UX] Change how the ways to implement a form are called #183

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
845dc2a
Update getting_started.rst
andersonjeccel Mar 20, 2024
65300f2
Update docs/form_hooks/getting_started.rst
andersonjeccel Apr 4, 2024
f7619e4
Merge branch '5.x' into ux-Change-how-the-ways-to-implement-a-form-ar…
RCheesley Jun 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/form_hooks/getting_started.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ You can define hooks for multiple Forms using the API name of the Form as follow

.. Note:: Define the Form hooks somewhere in the DOM before the code that loads the Form.

You'll need to view the HTML of the Form to find it's API name. The easiest way to do this is to browse to the Form's details in Mautic then click the "Manual Copy" button. Look for the following in the second box:
You'll need to view the HTML of the Form to find its API name. The easiest way to do this is to browse to the Form details in Mautic then click the 'Self-hosted' button. Look for the following in the second box:

.. code-block:: html

Expand Down
Loading