We are wondering if anyone has had experience in creating custom fields with image URLs and specifically including those in a dynamic emails as {leadfield = imageURL} and how this was implemented.
thanks
We are wondering if anyone has had experience in creating custom fields with image URLs and specifically including those in a dynamic emails as {leadfield = imageURL} and how this was implemented.
thanks
I dropped in HTML for Facebook links so that we could dynamically display those and it worked great. HTML code for images should work just as well.
@waxwing do you have an example? Maybe I wasn’t clear but I am looking for dynamic populating of images in the same way you would do {leadfield=Firstname} as a token.
I just dropped the HTML image code right into the custom field. It rendered just fine.
There was a bug in 1.2.0 which destroyed a HTML tag if the leadfield variable was a part of an attribute. I tested it with a link tag. But it should work in 1.2.1. @ehill , after you test it, please, let us know if it works. The best would be also to add a note to documentation so others could save some testing time.
@escopecz Great thanks. As we upgrade, let me describe what we are doing. We are adding URL to an Image Custom Field in order to populate each recipient with their own personal image. Obviously the bug is a problem, but in principle the fix should support this use case, correct?
Yep, I think so. 1.2.1 should be out any time now.
@escopecz great news…it was the one thing that was causing us extreme heart ache
@escopecz do you know when the release will occur?
It’s been released already https://github.com/mautic/mautic/releases. So far as update package it seems. You should see an icon in the notification area of your Mautic. Log out and back in if not.
@escopecz any test cases that are appropriate or is there a Github bug #? suggestions?
I don’t follow. Could you rephrase your question?
@escopecz Sorry. You said that we could help test and provide feedback. I wanted you to point me to the Github fix # or a test case so I could understand the specific functionality that was fixed and therefore insure that I am adequately testing against that.
Oh, well, I thought you’ll test the problem you’d described here, but if you want to know more about testing, I’m glad.
All opened pull requests are here:
https://github.com/mautic/mautic/pulls?q=is%3Apr+is%3Aopen
Here is a short tutorial about how to test those:
https://github.com/mautic/mautic#how-to-test-a-pull-request
The PR I was talking about that should fix your issue is here:
https://github.com/mautic/mautic/pull/920
It had been merged to 1.2.1 already.