-
Notifications
You must be signed in to change notification settings - Fork 6.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't print any custom print format as PDF in v15 #41397
Comments
If the standard print format is working, there must be some problem in the custom format's code itself. We tested in v15 latest with custom print format, but there is no issue found. Please share the code. |
`<style> /* arabic /
}
} .table .table-condensed .table-hover .table-bordered .print-format td, .print-format th{ } .print-heading {
border-bottom: 1px solid #d1d8dd !important; .alert-logo { .cr{ } text-align: right !important;
.logo-div2 { .logo-div4{ .logo-div5{
.logo-div6{ text-align:center !important;
.table-bordered, .table-bordered>tbody>tr>td, .table-bordered>tbody>tr>th, .table-bordered>tfoot>tr>td, .table-bordered>tfoot>tr>th, .table-bordered>thead>tr>td, .table-bordered>thead>tr>th { .td1 { border-bottom: 0.5px solid #d1d8dd !important; .si {
} .table-no-b { border-top: 0 !important; .space {
} .ql-editor.read-mode { padding:6px !important ; .h1, .h2, .h3, .h4, .h5, .h6, h1, h2, h3, h4, h5, h6 {
} .w1 {
{% if not no_letterhead and footer %}
{{ footer }}
{% endif %}
{{ _("Page {0} of {1}").format('', '') }}
{{ _("Service & product information") }}
{%- if doc.terms -%} {{ _("الملاحظات و الشروط و الاحكام") }}
{%- endif -%} ` |
Information about bug
Hello guys,
While I'm printing more than one material request, the system opens a blank PDF
although I was printing with the same print format as pdf in v14
FYI
The print format is customed not standard
Thanks for you all
Module
buying, other
Version
ERPNext: v15.22
Frappe: v15.25
Installation method
FrappeCloud
Relevant log output / Stack trace / Full Error Message.
No response
The text was updated successfully, but these errors were encountered: