Hi @geoff the PDF generator relies on images being resolvable by its URL, We’ve seen this issue when people are running InvoiceNinja on their local PC’s / behind a proxy/firewall and their DNS resolvers are not able to resolve the file locally.
@ben this issue has cropped up again, did we have a fix for this merged? or pending?
After some more analysis, I can confidently confirm that it is not a DNS issue nor a firewall issue. I can successfully load image using FQDN/storage/xxxxx/xxxx.png
You can completely remove storage/logs/laravel.log file.
Now, just generate new invoice or modify the current one. After generating you should see HTML in laravel.log. If you’re not familliar with that, that’s fine, send that log file in private messages on forum or on ben[at]invoiceninja.com and I’ll check it for you.
In case you’re using database/redis queue driver, please execute following command:
Hi @ben,
Yes, behaviour is exactly the same for me, no issue using default invoice ninja logo, once you update company details with logo them image does not display but alt tag value does.
I can only assume within you code you are using base64 and not an image because I replaced all ninja invoice images with different one and in most places within the application the logo changed as expected except generating the invoice pdf. Thus my request to review code to identify the issue.
Cheers
Hi @ben,
Many thanks for you update.
I followed you steps exactly and still the same issue, plus once I remove company logo from details section invoice pdf work perfectly with invoice ninja logo.
I will try and send log file to you.
Also note that my .env is very spartan compared to .env.example and their was no entry for QUEUE_CONNECTION…could this have an impact?
Cheers
Now log has the following;
[2020-11-25 19:59:10] production.INFO: MNIGn1ymACjbmdvMpxSqBrYGYLT7GTNPxLx88OwnVZzgm3FUyBZaEufbgZCD1Oc2/zfHA0RvoZxP04npYajTbuo8bwvIFg2qrJvS0Ha2t.png
[2020-11-25 19:59:10] production.INFO: 51c8d1d940db05739c4c4b149c4018cf24048529.png
[2020-11-25 19:59:10] production.INFO: the path /storage/MNIGn1ymACjbmdvMpxSqBrYGYLT7GTNPxLx88OwnVZzgm3FUyBZaEufbgZCD1Oc2/zfHA0RvoZxP04npYajTbuo8bwvIFg2qrJvS0Ha2t.png
When I put domain url in front of /storage/…/…png the logo/image displays perfectly just not in the pdf.
Cheers
We’ve use v4.5 with white-labelling successfully for over a year with an associated company and have never had a requirement to contact Invoice Ninja.
We only considering implementing with v5 because we received an email stating there was a stable release ready to use.
My experiences to-date are that this version is not stable and is not ready for production use and has a long way to go before it is.
I’ve seen a lot of comments saying bad things but to be honest, I personally like what you guys have done to-date, the item I give a big tick too is customising CSS for invoices, soooooo much better than previous versions.
The use of Material Design & Tailwinds is a great decision. My only criticism is too many frameworks/plugins being used and you’ve dive too much into the technology and forgotten about the basics plus the KISS theory.
From my prospective the 2 must have before any other functionality is white-labelling and invoices with our companies logo, sadly neither of these features are working with v5.
We have strong Java, Python and Javascript skills but very poor PHP and therefore are unable to assist and contribute to your great work.
Also note, that we had about 8 attempt trying to standup a Redhat version of v5 and then gave up, had 2 more goes with Debian 10 and finally got a working environment.
Sorry for long winded message, all the best with the future development of v5 but we are calling it a day as it’s became mission impossible for us.
v5 is currently a “stale release candidate”, if the only serious issues you’re seeing are the logo and white labelling then I think we got the label just right. I’m sure we’ll have those issues resolved for our official stable release.
Can you explain what you mean by “you’ve dive too much into the technology and forgotten about the basics plus the KISS theory”. It’s a vey general statement, it would be helpful if you could provide specifics.
We’re using Flutter to build the admin portal. The tech is still very new and has some compromises on web but (a) it will improve over time and (b) the fact that it enables us to provide web, iOS, Android, Windows, Linux and macOS apps with one codebase in my opinion make it the best choice for our app/team.