[19.0][MIG] report_qweb_pdf_watermark#1091
Open
antoniodavid wants to merge 57 commits intoOCA:19.0from
Open
Conversation
When no background configuration is present on the report definition, don't try to browse the report model especially because this breaks some upstream reports (see odoo/odoo#23389)
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: reporting-engine-11.0/reporting-engine-11.0-report_qweb_pdf_watermark Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-11-0/reporting-engine-11-0-report_qweb_pdf_watermark/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: reporting-engine-12.0/reporting-engine-12.0-report_qweb_pdf_watermark Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-12-0/reporting-engine-12-0-report_qweb_pdf_watermark/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: reporting-engine-12.0/reporting-engine-12.0-report_qweb_pdf_watermark Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-12-0/reporting-engine-12-0-report_qweb_pdf_watermark/
external_dependencies
[MIG] report_qweb_pdf_watermark: Migration to 15.0
Currently translated at 100.0% (10 of 10 strings) Translation: reporting-engine-17.0/reporting-engine-17.0-report_qweb_pdf_watermark Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-17-0/reporting-engine-17-0-report_qweb_pdf_watermark/it/
Currently translated at 100.0% (10 of 10 strings) Translation: reporting-engine-18.0/reporting-engine-18.0-report_qweb_pdf_watermark Translate-URL: https://translation.odoo-community.org/projects/reporting-engine-18-0/reporting-engine-18-0-report_qweb_pdf_watermark/tr/
antoniodavid
force-pushed
the
19.0-mig-report_qweb_pdf_watermark
branch
from
4284698 to
1e83842
Compare
|
PyPDF is moving back from PyPDF2 to the PyPDF package which now also supports 3.10+ This causes the report_qweb_pdf_watermark module to fail the PyPDF2 import. Not sure if this is the correct place to resolve it in a migration or if a seperate issue should be created. @lmignon |
bosd
approved these changes
Dec 24, 2025
Contributor
|
This PR has the |
Contributor
|
@hbrunn Can you have a look and please merge? 🙏 |
hbrunn
requested changes
Jan 7, 2026
Member
hbrunn
left a comment
hbrunn
left a comment
There was a problem hiding this comment.
the imports should also support the pypdf case as pointed out by #1091 (comment)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.