[DOC] reports: clarification about styles
* correct xpath to add style in report.styles * informations about style troubleshoot closes #9105
This commit is contained in:
parent
777f215edb
commit
4eab4d7868
|
@ -1622,6 +1622,30 @@ http://localhost:8069/report/html/account.report_invoice/1 (if ``account`` is
|
|||
installed) and the PDF version through
|
||||
http://localhost:8069/report/pdf/account.report_invoice/1.
|
||||
|
||||
.. _reference/backend/reporting/printed-reports/pdf-without-styles:
|
||||
|
||||
.. danger::
|
||||
|
||||
If it appears that your PDF report is missing the styles (i.e. the text
|
||||
appears but the style/layout is different from the html version), probably
|
||||
your wkhtmltopdf_ process cannot reach your web server to download them.
|
||||
|
||||
If you check your server logs and see that the CSS styles are not being
|
||||
downloaded when generating a PDF report, most surely this is the problem.
|
||||
|
||||
The wkhtmltopdf_ process will use the ``web.base.url`` system parameter as
|
||||
the *root path* to all linked files, but this parameter is automatically
|
||||
updated each time the Administrator is logged in. If your server resides
|
||||
behind some kind of proxy, that could not be reachable. You can fix this by
|
||||
adding one of these system parameters:
|
||||
|
||||
- ``report.url``, pointing to an URL reachable from your server
|
||||
(probably ``http://localhost:8069`` or something similar). It will be
|
||||
used for this particular purpose only.
|
||||
|
||||
- ``web.base.url.freeze``, when set to ``True``, will stop the
|
||||
automatic updates to ``web.base.url``.
|
||||
|
||||
.. exercise:: Create a report for the Session model
|
||||
|
||||
For each session, it should display session's name, its start and end,
|
||||
|
|
|
@ -205,19 +205,20 @@ Useful Remarks
|
|||
* Twitter Bootstrap and FontAwesome classes can be used in your report
|
||||
template
|
||||
* Local CSS can be put directly in the template
|
||||
|
||||
* Global CSS can be inserted in the main report layout by inheriting its
|
||||
template and inserting your CSS::
|
||||
|
||||
<template id="report_saleorder_style" inherit_id="report.layout">
|
||||
<xpath expr="//style" position="after">
|
||||
<style type="text/css">
|
||||
<template id="report_saleorder_style" inherit_id="report.style">
|
||||
<xpath expr=".">
|
||||
<t>
|
||||
.example-css-class {
|
||||
background-color: red;
|
||||
}
|
||||
</style>
|
||||
</t>
|
||||
</xpath>
|
||||
</template>
|
||||
* If it appears that your PDF report is missing the styles, please check
|
||||
:ref:`these instructions <reference/backend/reporting/printed-reports/pdf-without-styles>`.
|
||||
|
||||
.. _reference/reports/paper_formats:
|
||||
|
||||
|
|
Loading…
Reference in New Issue