I am trying to: Display a Hero image from a custom field, using the Divi Image Module in a content template
Link to a page where the issue can be seen: hidden link
I expected to see: the image at the top of the page
Instead, I got: image tag with no url
=== there's a text module just below the image module. In the text module I use the same shortcode and display the link. In addition I have another shortcode in the text module, to display the image itself. The link makes sense and the image in the text module is displayed properly.
1. The Divi image module is the preferred method for displaying images with Divi. Toolset is working very hard to enhance Divi by integrating Divi library layouts with Toolset. Why would you question my desire to use the image module? I'm reporting a bug.
2. No, I am not trying to add a link to the image currently, although I might want to do that at some point. All I'm trying to do now is display an image, using the Divi image module, in a Divi layout that is used as a Toolset content template. Using the text module is a workaround, but the image module would be the preferred method.
BTW: this bug is being reported by Toolset Contractor Chuck Gregory, cwg@cwgservices.com. I'm working on a site for Brendan Moran so Toolset for the site is connected to his account and I posted the ticket here. I've prepared screenshots to show the setup:
Content templates: hidden link
Toolset editor: hidden link
Divi Builder Editing Content Layout: hidden link
Image Module: hidden link
This is clearly a bug. it's not stopping us from proceeding on the site, but it needs to be addressed.
I'm adding an update here, from my own account, so that I'll get on the email list for it.
I look forward to seeing this resolved, so we don't have to work around the limitation.
I have made a design change on the site in question, so that I'm using the Featured Image rather than a custom field Hero Image... but I still need the image module to work.
Thanks
Here is the feedback from our 2nd tier supporters, it should be fixed in the latest stable version of Types plugins, please test it and check if it is fixed, you can download it here: https://toolset.com/account/downloads/