-
Notifications
You must be signed in to change notification settings - Fork 775
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
Web invoice does not show logo #1012
Comments
Thanks for the bug report, man!
I'm looking to reproduce the problem and then of course merge your fix. What I want to prevent is that after merging some other logo's won't show again, if you know what I mean. Related: |
Just to restate the issue: when viewing an invoice using the web view, the logo will not load. When viewing what URL was generated from the template we can see that it's a file system path, in my case: In #898 / #964 the stated issue was related to PDF's only but both invoice_logo() invoice_logo_pdf() were modified. As far as I can tell the main difference between the two functions is that:
#964 seems to have modified both functions when working on an issue related specifically to PDFs. In #897 the issue was related to PDF and only invoice_logo_pdf() was modified so it wont be related to my issue. You can see in the default PDF template, the logo is pulled with invoice_logo_pdf() so as long as that function isn't modified those referenced issues/pulls should not be impacted unless someone used invoice_logo() in a custom pdf template by mistake.
I just made an additional commit because I made a mistake and had an extra slash, I didn't see that base_url() already includes a trailing slash (although I'm not sure if it will when IP is in a sub directory). |
Expected Behavior
The invoice's web view uses invoice_logo() in invoice_helper.php, this function should provide a URL to the IP configured logo
Current Behavior
invoice_logo() produces an invalid URL based on an absolute file system path, it seems this change was only intended for invoice_logo_pdf()
Possible Solution
#1013
The text was updated successfully, but these errors were encountered: