[Resolved] New line when integrating with Beaver Builder

[Author]

Posts

[saint]

Hi guys,

This ticket is in regards to the discussion on the Toolset + Elementor post.

1.) Awhile back, I brought up a bug where in Beaver Builder, there is a new line that is entered every time I insert a custom field from Types.

hidden link

Juan mentioned to just open a ticket and see if this has been resolved yet. I'm not sure if there's a change-log page where I can parse and see what's been fixed or not, so just waiting for that to be fixed before I dive back in to begin development.

There was also an issue where I could NOT access custom fields that are tied via CPT relationships (when developing in BB) which I believe was also being addressed, but not sure where that stands either.

2.) I am also curious if there is a deep integration between Toolset + Beaver Builder similar to Toolset/Elementor or Pods/BB? I reached out to BB team and they said that based off their understanding, they were waiting to hear back from the Toolset team... But this has been on pause for almost 2 years (ha, ha...)

I think a lot of us BB devs would _love_ the same type of tight-knit integration as TS/Elementor or TS + Brizy/Oxygen/etc.

Please let me know if you have any questions.

Thanks,

[Luo Yang]

Hello,

Since it is a compatibility problem with Beaver Builder, please provide a copy of your website, also point out the problem page URL, where and how I can see the problem:
there is a new line that is entered every time I insert a custom field from Types.

I need to duplicate the same problem in my localhost, thanks

[Luo Yang]

Thanks for the details, I can download the files, the video shows only how to see the problem, please point out the problem page URL, where I can see the problem:
there is a new line that is entered every time I insert a custom field from Types.

If the problem is confirmed, it will be escalated to our developers, including Juan as well.

Thanks

[saint]

Hi Luo,

Please see below:

hidden link

Thanks,

[Luo Yang]

Thanks for the details, please edit the view "settlement - name"
hidden link

in section "Loop Editor", you will see two shortcodes: [wpv-layout-start] and [wpv-layout-end].

They will output an extra HTML div tag, which is required for some Views features, for example AJAX pagination and search.

And the HTML div tag conducts the problem you mentioned in video:
there is a new line that is entered every time you insert a Views shortcode [wpv-view ...]

If you don't need the HTML div tag, you can use some custom codes to remove it, for example this thread:
https://toolset.com/forums/topic/filtering-parent-options-by-custom-field/
See the steps 1) and 2) of solution in above thread.

[saint]

Thanks, Luo! I'll give that a shot. Two things:

1. Do you know if the accessibility issue with Beaver Builder where we couldn't get to a custom field in a relationally-linked CPT when we click "Fields and Views" (but _can_ easily get to when outside of Beaver Builder) -- was fixed?

2. Any thoughts re: deeper integration with Beaver Builder (similar to how Toolset currently integrates w/ Elementor?)

Best,

[Luo Yang]

For the new questions:

Q1) Do you know if the accessibility issue with Beaver Builder where we couldn't get to a custom field in a relationally-linked CPT when we click "Fields and Views" (but _can_ easily get to when outside of Beaver Builder) -- was fixed?

Is there any existed ticket for the problem you mentioned above? Can you provide the link of that ticket? I need to search it in our to-do list.

If there isn't existed ticket, please create one, and describe detail steps to duplicate the same problem, we need to debug it.

Q2) Any thoughts re: deeper integration with Beaver Builder (similar to how Toolset currently integrates w/ Elementor?)

I suggest you create a new "Feature request" ticket, and describe details for the "deeper integration", for example:
What kind of new feature you want to see in Toolset plugins