This support ticket is created 7 years, 3 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
I was hoping this would be resolved in version 2.4.1 but it wasn't.
I still think it should be working.
Just wanted to know the status of this as it WAS escalated and all.
Other than that: I just love what I can do with toolset! But now my customer is bugging me about this regularly and I think they are right. It should work.
Thank you for contacting Toolset support. Looking in our internal system I can see that this is not fixed. Mainly because this requires good collaboration from Beaver Builder and this involves some changes on their end too, since this is a compatibility issue.
I am trying to get more info from development team for you and will let you know what they say on this.
I have received update from the Development team, below is what they have informed me:
" We will not be able to solve this, but that we will review the mechanism so you can only insert shortcodes without GUI in fields that do support them. "
This is mainly because we are no longer working with Beaver Builder, they discontinued working relationship with us in favor of their own Beaver Themer product. Whereas this fix required their collaboration and to add some changes in their plugin too, which could not be happen now.
As developer mentioned above that we will review our mechanism to see if we can achieve something related to this issue. Thank you for your understanding.
I am sorry, I have just received notice that there has been some discussions and both plugins are now open for cooperation. Beaver Builder has continued working relation with us again and that we will be trying our best to fix the reported issues and it will again go through normal development processes (such as this issue).
We again strongly apologize for the confusion that had occurred. Thank you
