Skip to Content
This question has been flagged
wkhtmltopdf
942 Vistes
Avatar
Rai Mohammed

To test the reporting engine on Odoo #V17 and #V18, I tried the creation of a QWeb-based PDF report, to see if I can change some parameters to get past the problem of the error : "UserError odoo.exceptions.UserError #Wkhtmltopdf failed (error code : -10)" described in this link, I have this behavior from the report :

  • The QWeb template with "<t t-call="web.external_layout">" : the report is printed without error.
  • The QWeb template with "<t t-call="web.internal_layout">" : the report throws the described error.

So for the same configuration of Odoo 17 and 18, the reporting engine behaves differently, when changing the layout of the report from web.internal_layout --> web.external_layout?!. 

Is this a bug or a misconfiguration or what, can please someone help me to understand ?!

Avatar
Descartar
Related Posts Respostes Vistes Activitat
ir_actions_report.py in _run_wkhtmltopdf raise UserError odoo.exceptions.UserError Wkhtmltopdf failed ( error code : -10)
wkhtmltopdf
Avatar
1
de març 25
1098
PDF report not rendering header/partner details correctly. Solved
wkhtmltopdf
Avatar
Avatar
Avatar
2
de jul. 24
3849
wkhtmltopdf - How to enable local file system access Solved
wkhtmltopdf
Avatar
1
de maig 24
2046
Wkhtmltopdf not found on the sysem Solved
wkhtmltopdf
Avatar
Avatar
Avatar
2
de febr. 24
3216
Wkhtmltopdf failed (error code: 222). Message: b'Unable to call host printing service (ConnectionError)'
wkhtmltopdf
Avatar
0
de juny 22
2267