NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[FIX] *: unbalanced literal markups

Browse Source 
Part-of: odoo/documentation#2978
This commit is contained in:
Victor Feyens 2022-11-17 15:54:48 +00:00
parent efb6c47e92
commit 06f328a39e
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/applications/websites/website/optimize/seo.rst
View File

@ -621,7 +621,7 @@ robots.txt
---------- ----------
When indexing your website, search engines take a first look at the When indexing your website, search engines take a first look at the
general indexing rules of the a``/robots.txt`` file (allowed robots, general indexing rules of the ``/robots.txt`` file (allowed robots,
sitemap path, etc.). Odoo automatically creates it. Its content is: sitemap path, etc.). Odoo automatically creates it. Its content is:
User-agent: \* User-agent: \*

6
content/developer/howtos/rdtraining/K_dashboard.rst
View File

@ -36,7 +36,7 @@ File Structure
You probably have already guessed that since dashboard views are an Enterprise view, they must have You probably have already guessed that since dashboard views are an Enterprise view, they must have
a dependency on an Enterprise module. The Enterprise module is ``web_dashboard``. Don't forget to a dependency on an Enterprise module. The Enterprise module is ``web_dashboard``. Don't forget to
add it to your manifest file! It is standard to add dashboards intended to be used as a add it to your manifest file! It is standard to add dashboards intended to be used as a
``view_mode`` for one of your module's models (in the ``model`` folder``) to the views directory ``view_mode`` for one of your module's models (in the ``model`` folder) to the views directory
(i.e. the same file that contains the other views for the same model). (i.e. the same file that contains the other views for the same model).
It is standard to create a separate Enterprise module to add extra Enterprise views and features to It is standard to create a separate Enterprise module to add extra Enterprise views and features to
@ -319,8 +319,8 @@ View
Now that we have our model, we can make its dashboard view. There is no difference to how its made Now that we have our model, we can make its dashboard view. There is no difference to how its made
except that its file is located in the ``report`` folder. Since it is a new model not linked to except that its file is located in the ``report`` folder. Since it is a new model not linked to
any other model, we will also have to add a new menuitem to view our dashboard. Typically SQL views any other model, we will also have to add a new menuitem to view our dashboard. Typically SQL views
are added under a first level menu called ``Reporting` (because it's a report, surprise!). Do you are added under a first level menu called ``Reporting`` (because it's a report, surprise!). Do you
remember how to add a ``menuitem``? If not, revisit :ref:`howto/rdtraining/06_firstui`) again. remember how to add a ``menuitem``? If not, revisit :ref:`howto/rdtraining/06_firstui` again.
.. exercise:: Create report view. .. exercise:: Create report view.

2
content/developer/reference/javascript/qweb.rst
View File

@ -173,7 +173,7 @@ variables for various data points:
index index
These extra variables provided and all new variables created into the These extra variables provided and all new variables created into the
``foreach`` are only available in the scope of the``foreach``. If the ``foreach`` are only available in the scope of the ``foreach``. If the
variable exists outside the context of the ``foreach``, the value is copied variable exists outside the context of the ``foreach``, the value is copied
at the end of the foreach into the global context. at the end of the foreach into the global context.