-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Logo in email is too big #15236
Comments
You can upload a separate email logo that works better with the email layout. |
I understand, but 570 is an overkill in an email. Who needs such big logo in their emails? :) |
We give you the ability to upload an email image specifically because we don't know what the dimensions of your logo might be (wide and short, taller and more square, etc.) Just upload a separate image for email. Use the tools we already provide for you. (Who needs a 512x514 logo on the website, by that logic.) There are lots of online image resizing tools. https://imageresizer.com
|
Logo resizes nicely as Site Logo, but it doesn't in emails. And why Site Logo shows in emails? Maybe I don't want logos is emails. :) Do I need to edit php files or env settings? |
That's why you upload a different one. One for each purpose. Upload a clear gif as your email logo if you don't want one. I swear I feel like you just find things to open issues about. That code isn't even getting the logo - that's getting the image of the item being requested, checked out etc:
The mail template logo code is here: snipe-it/resources/views/vendor/mail/html/message.blade.php Lines 16 to 44 in 28abb8d
|
We absolutely do not think the product is perfect, and have never implied as much, however intentionally uploading a gigantic logo is also a weird thing to do, when resizing it to the size you actually want seems like a pretty normal thing for a user to do. Since we don’t know what every logo will look like, we can’t guess what it will look like in emails. Additionally, uploading a giant image is going to slow down page loads, so it’s generally an overall bad idea. That’s not because of anything we do, it’s just how the internet works. We always appreciate a heads up on things we can improve on, but this particular detail seems like it’s solvable by the user as easily (or more so) as by us, and in every single issue you open here, you never have anything nice to say about any of the things (and there are many) that we do right. We’re glad for the heads up, but you could soften some of these issues by sounding a little more supportive of the hard work and attention to detail we have in addition to the things we miss. That’s just called “being nice”. Additionally, whenever we change something, even the size of a logo, we always impact other people with different workflows, and it’s our responsibility to bear that in mind. We’re not losing customers over this issue. We’ll take a look at it but it’s lower priority over more important issues we’re working on. |
Debug mode
Describe the bug
It's more aesthetics when a bug, but it looks like this 570px creeped in during intense coding session. 150-200 px would look better. Such big image in email looks meh...
(Disregard 1024x1024 - for testing purposes only)
570px found in these files:
snipe-it-7.0.10\resources\views\notifications\markdown\asset-requested.blade.php
snipe-it-7.0.10\resources\views\notifications\markdown\checkin-accessory.blade.php
snipe-it-7.0.10\resources\views\notifications\markdown\checkin-asset.blade.php
snipe-it-7.0.10\resources\views\notifications\markdown\checkout-accessory.blade.php
snipe-it-7.0.10\resources\views\notifications\markdown\checkout-asset.blade.php
<center><img src="{{ $item->getImageUrl() }}" alt="Asset" **style="max-width: 570px;">**</center>
Reproduction steps
Just send confirmation emails.
Expected behavior
Logo doesn't use all readable space in in Outlook (or other email client)
Screenshots
Snipe-IT Version
7.0.10
Operating System
Web Server
PHP Version
Operating System
No response
Browser
No response
Version
No response
Device
No response
Operating System
No response
Browser
No response
Version
No response
Error messages
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: