Link to a page where the issue can be seen: hidden link hidden link
These CPTs each have different images set, as indicated in the data preview offered in screenshots 2 and 3. However, their outputted background images on the front-end are the same. This is indicated in screenshots 4 and 5.
I expected to see:
Different images per CPT, as set in their respective fields.
Instead, I got:
The same image as the background in each CPT.
It seems the background images are set in a cached CSS file, as indicated in screenshots 6 and 7 (each taken from the two different CPT pages). The node number does not change between these two CPTs, resulting in the same image. In my initial contact with BB support, they believe the issue is on the Toolset side.
As an update to this: on a separate staging environment, I added the "Featured Image" option to the "Communities" CPT and tried setting *that* as the background image to the row. the Content Template displays the correct background image when working in the Beaver Builder editor interface invoked through the Content Template page (and when switching the sample CPT at top), but it doesn't display anything when viewing through the frontend of the site -- it does not apply the background image.
Hello. Thank you for contacting the Toolset support.
I see you are using the latest version of Toolset plugins and on top of that you followed the way how you can display custom field with BeaverBuilder as per the doc you shared:
=> hidden link
As you can see the node is generated from the Beaver builder and we do not have control on it. Would you mind to check this issue with BeaverBuilder support and if they see the issue is from Toolset we are happy to help and take it as compatibility issue but for now, it seems to me the issue is from Beaver Builder, as using Toolset we are just passing the custom field name but the rendering mechanism is done from Beaver Builder.
I spoke with BB support parallel to working with you and I was able to get the background images to work by using their Themer product, which does the same as Toolset's Content Templates. I was able to copy the BB page into Themer and set the Toolset Custom Field as the background image and everything is working properly.
Interestingly, when I went back to Toolset's Dashboard to delete that particular Content Template (as it was no longer needed, Themer having taken over that job), I lost all my changes to the CPT's layouts that Themer was handling. Only by restoring the Content Template from the Trash and reconnecting it to those CPTs was Themer able to show the layouts correctly.
I'm leaving the Content Template in place, even though it's unused, because of this strange issue. The BB team believes the original issue (background images not displaying when using the Toolset Custom Field) is an issue with Toolset. I know that your team believes the reverse is true. I'm mentioning it only to put it on Toolset's radar that there is something not functioning correctly between the two plugins, and I'm sure the two teams would be able to quickly figure it out with some short communication. Certainly, that would be best for the community at large!
I've reported the same back to BB support and I'm hopeful that within the next couple of releases of either plugin we can see this bug fixed.
Hello Mike! This is Jamal from the Toolset Support team. As Minesh won't be available, I'd like to continue with you on this ticket.
I understand that the custom field image is working with Themer but not with the Toolset content template, right?
Then, there is this issue when you are not able to use the Themer template without being able to remove the unused content template. Right?
I suggest focusing on the first/original issue and get to a point where you can use Toolset content template with a Toolset image custom field as a background.
To narrow it down and to be able to escalate it to our compatibility team, our process requires us to reproduce this issue on a clean install on our platform, then I'll be able to escalate the ticket to our 2nd Tier who will try to investigate the issue and provide a workaround before handing it over to the compatibility team or to the core developers.
For that reason, I have created a test site on our platform, and I would need your collaboration to install BeaverBuilder and to reproduce this issue. Please find the credentials to the server in my previous private message(July 14, 2020 at 12:36 pm)
Once it is reproduced, I'll escalate it. If it is not, I'll need to take a copy of your website for further analysis.
Hello Jamal, thanks for picking this up with me, and apologies for the long delay from last week, work has kept me busy.
I've installed and activated the two Beaver Buidler plugins required for the functionality (Beaver Builder Agency, in our case) and Beaver Themer (which allows us to use Toolset's custom fields in the Content Templates).
I've gone into Beaver Builder's settings (Settings > Beaver Builder) and enabled BB on the CPT I set up for this purpose (Background Image Tests).
I've used Toolset to create a single Custom Field on the CPT: a photo field to hold the image we'll be using as the background image.
I've created two test posts and assigned different images to their fields.
I've created a Content Template and invoked Beaver Builder to create it. Within, there is a single row that has the background image set to the custom field of the CPT.
After publishing the Content Template, I tried viewing the two different posts from the front end, and they both have the same image. This is the problem; the two posts should have their own respective image showing.
I can say that the image the Content Template/BB ultimately shows seems to be the most recent one used to Preview the template when working in it (Toolset > Content Templates > choose the Template for Background Images > Invoke BB > select a sample post from the menu at top). Whichever post you select just before publishing seems to be the one that sticks.
Let me know if there's any questions, confusion, or more that I can offer.
Before I can escalate this compatibility issue, I still need your help.
- Update the "Beaver Themer" plugin to the latest version(). This could avoid us to debug an issue that might already be fixed in a recent update. hidden link
- Record a short video with "Loom" or "Screencastify" or share a documentation video, to let us know how to pull the image from an ACF custom field.
I tried to check it, but then I lost the custom field and the BB editor for the content template does not allow me to pick a custom field anymore. It only allows us to use the Media Library. hidden link
Then I realized that we need to choose a URL and then we can use the custom field, is that right?
No problem. I've updated the Beaver Themer plugin to the latest version, we should be all set there.
I've recorded a short Screencastify video here: hidden link
You'll see me navigate into the Content Template and invoke Beaver Builder. Then I open the setting for the row to get to the background properties.
I, too, tried inputting the Types shortcode here, but BB won't interpret it. Instead, this is where that Knowledgebase article from earlier in our thread comes in; we need to add the Custom Field's slug, prefixed with "wpcf-". Then it will work (or should!).
You can see me change the sample post I'm viewing while still in the editor, but Screencastify doesn't capture the dropdown, unfortunately. I also didn't capture the address bar when I view the two custom posts from the front end, but you can see the effect -- whether I view Example Post One or Example Post Two, they both have the same background image (and they should be different -- I've already assigned them in each of the posts).
Let me know if I can provide more info, thank you for the help!
According to our 2nd Tier, this is an issue on Beaver Builder instead of Toolset. We suggest checking with the Beaver Builder support team, and if they confirm that the issue is on Toolset, we'll give it another shot and escalate it to our compatibility team.
Ok, thanks for checking with 2nd Tier support. I'll make a similar review with the BB team and let you know what comes of it.
Also, the last post in that Toolset forum thread is mine. 🙂 It *seemed* that it was working at the time I posted that suggestion, but then realized shortly afterward that we were seeing this current problem. Unfortunately, I couldn't make a followup post to indicate as much.
