Blog notification email image not responsive or accepting alternative sizes over 450px
SOLVE
I've been working on this for a client for some time and cannot get the featured image to behave. I've been able to edit the featured image sizing on another client's blog notification email to make it 600px and responsive using the max width of the content module and of course my content module is responsive.
Does anyone know if the {{post.featured_image}} token is related to some setting unique to each portal? I can't explain how I would get different results with the same template in two different portals. I need to be able to edit this image.
The source url of the featured image, selected when the blog was published
This variable literally only outputs the url of the image. to use it you would place it in the src of an img tag.
You can check the url to see if a height or width dimension is appended to the end, but this shouldn't be the case.
You didn't really explain what the issue is so it is hard to help you solve it. If you went into detail it would help. I do know that in the content settings for blogs their is an option to use featured image in listing and this will effect rss feeds. Also, based on what I said above, your issue is most likely css related so you should look at the web version of the email and use the console to check for interfering css.
Blog notification email image not responsive or accepting alternative sizes over 450px
SOLVE
@Jsum thanks for responding to my post so quick, I know I did a poor job explaining my problem. What happens is that the token pulls in more than just the image, it pulls in an impressive amount of markup. In this case it pulls in the following for{{ post.featured_image }}:
Which is fine, however, it's not easily editted and while i wrote some css to make it work for the meanwhile I'd prefer to operate using inline css whenever possible.
Do you know where the {{ content.featured_image }} lives? Can its configuration be edited?
I am not very familiar with setting up an rss feed in an email template. It seams like Hubspot has a different ouput rules for email. I will play with this in a few minutes and let you know.
Thanks, I appreciate the help, as you'll notice there's no class on the <img> so editing what's inline required some !importants which aren't—always—robust enough for email.