Skip to content

Commit b36f3e4

Browse files
committed
fix labels
1 parent 7336433 commit b36f3e4

File tree

10 files changed

+13
-12
lines changed

10 files changed

+13
-12
lines changed

components/form.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -498,7 +498,7 @@ That's it! By printing ``form_widget(form)``, each field in the form is
498498
rendered, along with a label and error message (if there is one). As easy
499499
as this is, it's not very flexible (yet). Usually, you'll want to render each
500500
form field individually so you can control how the form looks. You'll learn how
501-
to do that in the ":ref:`form-rendering-template`" section.
501+
to do that in the ":doc:`/form/rendering`" section.
502502

503503
Changing a Form's Method and Action
504504
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

form/data_transformers.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -289,7 +289,7 @@ Now, when you create your ``TaskType``, you'll need to pass in the entity manage
289289
.. note::
290290

291291
To make this step easier (especially if ``TaskType`` is embedded into other
292-
form type classes), you might choose to :ref:`register your form type as a service <form-as-services>`.
292+
form type classes), you might choose to :doc:`register your form type as a service </form/form_dependencies>`.
293293

294294
Cool, you're done! Your user will be able to enter an issue number into the
295295
text field and it will be transformed back into an Issue object. This means

form/form_customization.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ just one line:
8383
8484
The remainder of this recipe will explain how every part of the form's markup
8585
can be modified at several different levels. For more information about form
86-
rendering in general, see :ref:`form-rendering-template`.
86+
rendering in general, see :ref:`/form/rendering`.
8787

8888
.. _cookbook-form-customization-form-themes:
8989

form/form_dependencies.rst

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,3 @@
1-
.. _form-as-services:
2-
31
How to Access Services or Config from Inside a Form
42
===================================================
53

form/form_themes.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -97,6 +97,8 @@ For a more extensive discussion, see :doc:`/form/form_customization`.
9797
.. index::
9898
single: Forms; Template fragment naming
9999

100+
.. _form-template-blocks:
101+
100102
Form Fragment Naming
101103
--------------------
102104

@@ -175,6 +177,8 @@ override the default error rendering for *all* fields, copy and customize the
175177
.. index::
176178
single: Forms; Global Theming
177179

180+
.. _forms-theming-global:
181+
178182
Global Form Theming
179183
-------------------
180184

form/rendering.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ the other functions do?
4242

4343
The majority of the work is done by the ``form_row`` helper, which renders
4444
the label, errors and HTML form widget of each field inside a ``div`` tag by
45-
default. In the :ref:`form-theming` section, you'll learn how the ``form_row``
45+
default. In the :doc:`/form/form_themes` section, you'll learn how the ``form_row``
4646
output can be customized on many different levels.
4747

4848
.. tip::

forms.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -185,7 +185,7 @@ That's it! Just three lines are needed to render the complete form:
185185

186186
As easy as this is, it's not very flexible (yet). Usually, you'll want to
187187
render each form field individually so you can control how the form looks.
188-
You'll learn how to do that in the ":ref:`form-rendering-template`" section.
188+
You'll learn how to do that in the ":doc:`/form/rendering`" section.
189189

190190
Before moving on, notice how the rendered ``task`` input field has the value
191191
of the ``task`` property from the ``$task`` object (i.e. "Write a blog post").

reference/configuration/framework.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1218,7 +1218,7 @@ Assume you have custom global form themes in
12181218

12191219
.. seealso::
12201220

1221-
See :ref:`book-forms-theming-global` for more information.
1221+
See :ref:`forms-theming-global` for more information.
12221222

12231223
.. _reference-templating-cache:
12241224

reference/forms/types/submit.rst

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,7 @@ A submit button.
2828
The Submit button has an additional method
2929
:method:`Symfony\\Component\\Form\\ClickableInterface::isClicked` that lets
3030
you check whether this button was used to submit the form. This is especially
31-
useful when :ref:`a form has multiple submit buttons
32-
<book-form-submitting-multiple-buttons>`::
31+
useful when :doc:`a form has multiple submit buttons </form/multiple_buttons>`::
3332

3433
if ($form->get('save')->isClicked()) {
3534
// ...
@@ -74,7 +73,7 @@ from the "Registration" are validated.
7473

7574
.. seealso::
7675

77-
You can read more about this in :ref:`the Form chapter <book-form-validation-groups>`
76+
You can read more about this in :ref:`the Form chapter </form/data_based_validation>`
7877
of the book.
7978

8079
Form Variables

validation/groups.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -185,4 +185,4 @@ will be applied.
185185

186186
Of course, you'll usually work with validation indirectly through the form
187187
library. For information on how to use validation groups inside forms, see
188-
:ref:`book-forms-validation-groups`.
188+
:doc:`/form/validation_groups`.

0 commit comments

Comments
 (0)