[FIX] doc: escape correctly code
Was rendered 'UNKNOWN NODE title_reference' Closes #16064
This commit is contained in:
@@ -643,7 +643,7 @@ instead of a single view its ``arch`` field is composed of any number of
|
||||
``inside``
|
||||
appends ``xpath``'s body at the end of the matched element
|
||||
``replace``
|
||||
replaces the matched element with the ``xpath``'s body, replacing any `$0` node occurrence
|
||||
replaces the matched element with the ``xpath``'s body, replacing any ``$0`` node occurrence
|
||||
in the new body with the original element
|
||||
``before``
|
||||
inserts the ``xpath``'s body as a sibling before the matched element
|
||||
|
||||
@@ -97,7 +97,7 @@ how the matched node should be altered:
|
||||
the content of the inheritance spec is appended to the matched node
|
||||
``replace``
|
||||
the content of the inheritance spec replaces the matched node.
|
||||
Any text node containing only `$0` within the contents of the spec will
|
||||
Any text node containing only ``$0`` within the contents of the spec will
|
||||
be replaced by a complete copy of the matched node, effectively wrapping
|
||||
the matched node.
|
||||
``after``
|
||||
|
||||
@@ -34,8 +34,8 @@ accessible Odoo needs a rule to know which one it should use.
|
||||
That is one of the purposes of :option:`--db-filter <odoo-bin --db-filter>`:
|
||||
it specifies how the database should be selected based on the hostname (domain)
|
||||
that is being requested. The value is a `regular expression`_, possibly
|
||||
including the dynamically injected hostname (`%h`) or the first subdomain (`%d`)
|
||||
through which the system is being accessed.
|
||||
including the dynamically injected hostname (``%h``) or the first subdomain
|
||||
(``%d``) through which the system is being accessed.
|
||||
|
||||
For servers hosting multiple databases in production, especially if ``website``
|
||||
is used, dbfilter **must** be set, otherwise a number of features will not work
|
||||
@@ -70,7 +70,7 @@ in ``/etc/odoo.conf`` set:
|
||||
of securing your deployment.
|
||||
Once it is correctly working and only matching a single database per hostname, it
|
||||
is strongly recommended to block access to the database manager screens,
|
||||
and to use the `--no-database-list` startup paramater to prevent listing
|
||||
and to use the ``--no-database-list`` startup paramater to prevent listing
|
||||
your databases. See also security_.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user