Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit fb1cd56

Browse filesBrowse files
committed
Fixed a missing cross reference
1 parent 32ec45d commit fb1cd56
Copy full SHA for fb1cd56

File tree

Expand file treeCollapse file tree

2 files changed

+4
-2
lines changed
Filter options
Expand file treeCollapse file tree

2 files changed

+4
-2
lines changed

‎form/create_custom_field_type.rst

Copy file name to clipboardExpand all lines: form/create_custom_field_type.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,8 +90,8 @@ shipping options.
9090
.. tip::
9191

9292
If the purpose of this new form type was to customize the rendering of some
93-
fields only, skip this step and use ``block_name`` or ``block_prefix`` option
94-
instead. For more information, see :ref:`form-customization-form-themes`.
93+
fields only, skip this step and use ``block_name`` or ``block_prefix`` options
94+
instead to :ref:`define a custom form fragment name <form-fragment-custom-naming>`.
9595

9696
.. tip::
9797

‎form/form_themes.rst

Copy file name to clipboardExpand all lines: form/form_themes.rst
+2Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -275,6 +275,8 @@ form. You can also define this value explicitly with the ``block_name`` option::
275275
In this example, the fragment name will be ``_product_custom_name_widget``
276276
instead of the default ``_product_name_widget``.
277277

278+
.. _form-fragment-custom-naming:
279+
278280
Custom Fragment Naming for Individual Fields
279281
............................................
280282

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.