Permalink
Browse files

minor #3650 Fixing some build errors (xabbuh)

This PR was merged into the 2.3 branch.

Discussion
----------

Fixing some build errors

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | all
| Fixed tickets |

Commits
-------

62d4a97 fix seealso directive name
62586a4 fix table syntax
72659e2 fix PHP code block
c7f2ee6 fixing doc roles
  • Loading branch information...
weaverryan committed Mar 18, 2014
2 parents fa3f531 + 62d4a97 commit 2192c3274e7a64f3a5de1eab5a9a4cb6adf2be9e
@@ -74,7 +74,7 @@ that the type guesser cannot guess the type.
The ``TypeGuess`` constructor requires 3 options:
* The type name (one of the :doc:`form types </reference/forms/types`);
* The type name (one of the :doc:`form types </reference/forms/types>`);
* Additional options (for instance, when the type is ``entity``, you also
want to set the ``class`` option). If no types are guessed, this should be
set to an empty array;
@@ -204,8 +204,8 @@ own, it just needs to follow these rules:
:method:`Symfony\\Component\\Security\\Core\\Encoder\\PasswordEncoderInterface::isPasswordValid`
must first of all make sure the password is not too long, i.e. the password length is no longer
than 4096 characters. This is for security reasons (see `CVE-2013-5750`_), and you can use the
:method:`Symfony\\Component\\Security\\Core\\Encoder\\BasePasswordEncoder::isPasswordTooLong`_
method for this check:
:method:`Symfony\\Component\\Security\\Core\\Encoder\\BasePasswordEncoder::isPasswordTooLong`
method for this check::
use Symfony\Component\Security\Core\Exception\BadCredentialsException;
View
@@ -7,7 +7,7 @@ How to use the Cloud to Send Emails
Requirements for sending emails from a production system differ from your
development setup as you don't want to be limited in the number of emails,
the sending rate or the sender address. Thus,
:doc:`using Gmail </cookbook/email/gmail>`_ or similar services is not an
:doc:`using Gmail </cookbook/email/gmail>` or similar services is not an
option. If setting up and maintaining your own reliable mail server causes
you a headache there's a simple solution: Leverage the cloud to send your
emails.
@@ -9,7 +9,7 @@ object and all sub-objects associated with it.
| Applies to | :ref:`property or method <validation-property-target>` |
+----------------+---------------------------------------------------------------------+
| Options | - `traverse`_ |
| | - `message`_ |
| | - `message`_ |
+----------------+---------------------------------------------------------------------+
| Class | :class:`Symfony\\Component\\Validator\\Constraints\\Type` |
+----------------+---------------------------------------------------------------------+
View
@@ -344,7 +344,7 @@ process. By default, form guessing is done by "guessers" based on the validation
metadata and Doctrine metadata (if you're using Doctrine) or Propel metadata
(if you're using Propel).
.. seelalso::
.. seealso::
For information on how to create your own type guesser, see
:doc:`/components/form/type_guesser`.
@@ -847,7 +847,7 @@ swiftmailer.default.plugin
If you're using a custom SwiftMailer plugin (or want to create one), you can
register it with SwiftMailer by creating a service for your plugin and tagging
it with ``swiftmailer.default.plugin`` (it has no options).
it with ``swiftmailer.default.plugin`` (it has no options).
.. note::

0 comments on commit 2192c32

Please sign in to comment.