astaadmin

Forum Replies Created

  • A
    astaadmin
    Participant

    Hello, 

    Ive done some inspections here my conclusion please check this out and may resolve this in a new version if my inspections are correct: (i am not sure) 

    The missing logo in ticket print / PDF view under osTicket 1.18.3 is not a server, permission, or osTicket core issue.
    It is an incompatibility between the osTicket Awesome print template and mPDF ≥ 8.1, which is used starting with osTicket 1.18.3.

    Test environment (minimal, reproducible):

    PHP 8.2.x (also tested with 8.3 / 8.4)
    Apache or Nginx
    PHP extensions: gd, mbstring
    no imagick
    allow_url_fopen = Off
    allow_url_include = Off
    Software:

    osTicket 1.18.2 (baseline)
    osTicket 1.18.3
    osTicket Awesome 102
    mPDF:

    1.18.2 → mPDF 8.0.x
    1.18.3 → mPDF 8.2.7
    Reproduction steps:

    Working baseline
    Fresh osTicket 1.18.2 installation
    Install osTicket Awesome
    no changes
    allow_url_fopen = Off
    Print ticket to PDF
    Result: Logo renders correctly.

    Failing case
    Same server, same PHP config
    Fresh osTicket 1.18.3 installation
    Install osTicket Awesome
    no changes
    allow_url_fopen = Off
    Print ticket to PDF
    Result:

    Logo missing (red X)
    Avatars missing (red X)
    Control test
    Replace Awesome print template with the osTicket 1.18.3 core template
    Print again
    Result:

    Logo renders correctly
    This confirms the issue is in the Awesome print template, not in osTicket core.

    Root cause:
    The Awesome print template outputs image sources like:

    In mPDF 8.0.x, root-relative image paths were often implicitly treated as local files.
    Since mPDF 8.1, these paths are classified as URLs.
    mPDF attempts HTTP(S) fetching, which fails when allow_url_fopen = Off.
    This results in the red X placeholder in the PDF.

    Why it worked before:
    The behavior in mPDF 8.0.x was implicit and undocumented.
    The Awesome template relies on this old behavior.
    With mPDF ≥ 8.1 (osTicket 1.18.3), this no longer works.

    Why core works:
    The osTicket core uses pdf_logo() and embeds the logo internally (cid / local).
    No URL-based image loading is used in PDFs.

    Conclusion:
    This is not an osTicket regression.
    It is a template compatibility issue in osTicket Awesome caused by changes in mPDF ≥ 8.1.

    Recommended fix:

    Embed the logo via pdf_logo() / cid / Base64
    Avoid URL-based images in PDFs
     

    A
    astaadmin
    Participant

    Additional testing: 
    I can reproduce the missing logo in PDF issue on our side, regardless of whether a custom logo is enabled or not. Neither the custom logo nor the default osTicket logo is rendered in the PDF.

    Tested with a clean installation:

    uploaded the release ZIP
    extracted it
    applied permissions
    copied only include/ost-config.php
    (no other changes)
    The issue occurs with osTicket 1.18.3.
    Running the exact same steps with 1.18.2 on the same server (same permissions, same config) works fine and the logo is shown.

    This looks like a regression in 1.18.3.

    Please let me know where I should upload a sample PDF.

    Environment details:

    PHP: 8.2.30 testet also with 8.3, 8.4
    Extensions: gd, mbstring (no imagick)
    PDF engine: no mPDF detected (class_exists returns false)
    osTicket: 1.18.3
    Install type: clean install, only ost-config.php copied

    Same setup with osTicket 1.18.2 works fine (logo rendered in PDF).
    Issue appears only with 1.18.3.

    Best regards

    A
    astaadmin
    Participant

    Additional information

    I also noticed that avatars are not rendered correctly in the ticket print / PDF view.
    Instead of the avatar image, only an “X” placeholder is shown.

    This issue only occurs with osTicket 1.18.3 + osTicket Awesome.
    Using the core 1.18.3 print template, avatars are printed correctly.

    This further supports that the Awesome print template is not fully compatible with osTicket 1.18.3.

    In reply to: New version update osTicket Core, v1.18.3

    January 30, 2026 at 4:32 am #24653
    A
    astaadmin
    Participant

    Hello,

    after upgrading osTicket from 1.18.2 to 1.18.3, the logo is missing in the ticket print / PDF view when using osTicket Awesome.

    What I tested
    Replaced ticket-print.tmpl.php with the original osTicket 1.18.3 core version → logo works
    Re-applied osTicket Awesome → logo broken again
    File permissions and paths are correct

    Comparison
    1.18.2 + osTicket Awesome → OK
    1.18.3 + osTicket Awesome → FAIL
    1.18.3 + core print template → OK
    This points to an incompatibility in the Awesome print template with osTicket 1.18.3.

    Please investigate and update the print template accordingly.

    Best regards

    A
    astaadmin
    Participant

    Hello,

    after upgrading osTicket from 1.18.2 to 1.18.3, the logo is missing in the ticket print / PDF view when using osTicket Awesome.

    What I tested
    Replaced ticket-print.tmpl.php with the original osTicket 1.18.3 core version → logo works
    Re-applied osTicket Awesome → logo broken again
    File permissions and paths are correct

    Comparison
    1.18.2 + osTicket Awesome → OK
    1.18.3 + osTicket Awesome → FAIL
    1.18.3 + core print template → OK
    This points to an incompatibility in the Awesome print template with osTicket 1.18.3.

    Please investigate and update the print template accordingly.

    Best regards

    In reply to: Os Ticket Plus

    October 29, 2024 at 4:58 am #21743
    A
    astaadmin
    Participant

    No, your statement is wrong.
    There is an osticket plus editon for selfhosted please specify how we can use osticket awesome with it?