Skip Navigation

[Resolved] Avada and Toolset dont work together

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.

This topic contains 2 replies, has 2 voices.

Last updated by sorinR 1 year, 10 months ago.

Author
Posts
#2376105

hello friends

you have this post on your website

https://toolset.com/course-lesson/using-toolset-with-avada/

but then you have this post

https://toolset.com/errata/avada-theme-settings-not-working-in-toolset-templates/

which says that actually there is a big problem when working with toolset and Avada.

The issue is there for a year now.... and, let's be honest, you will not solve it any time soon, maybe you will not solve it at all.

My situation:

I bought Avada two weeks ago. I am switching from the Kallyas theme(a discontinued product, as they haven't updated it in the last two years).

On my current website I have a large collection of Custom Post Types and Custom Posts.

I decided to buy Avada after reading your post on Avada.

this one https://toolset.com/course-lesson/using-toolset-with-avada/

This is the one that shows on Google search when I've tried to find out if there are integration problems between the two items: Avada and Toolset.

Now after discovering the issue, I feel cheated by your post about Avada integration that should clearly mention that YOU HAVE ISSUES with AVADA.

The text mentioned in your article is a lie:

"When you create a template for a single post or an archive page using Toolset and the Block Editor (aka Gutenberg), you can control different Avada theme options like the appearance of sidebar or content width."

Yes. A lie. Plain and simple.

Actually you can't control Avada related settings on Content Templates created with Toolset.

Please do correct that on the main post about avada. If you did that, I wouldnt be writing this text and none of my above problems have existed.

The workaround is not cool. It's actually a joke.

"You have to manually go on each post and modify the Avada related settings."

Really?

My website has thousands of posts.

What if I change my mind about a content template design? I need to go back and modify again on each post?

That kind of defeats the purpose of using a plugin for displaying dinamic content.

A plugin that should give you free time and not take your time.

A plugin that should make you life easier, not harder.

Avada doesnt work with toolset, not in the way you would want it to work anyways.

And you should make that clear in the main post you have about avada, not in the Errata Section where people like myself will find it after investing money and time in the Avada + Toolset setup.

Your misleading post about Avada cost me 70 USD to buy Avada and two weeks of website work trying to learn how to use Avada just to find out that hey.. actually I cant use avada with toolset.

Now I need to do the whole process again.

Find a theme. Pay it. Learn it.

What payed theme works with toolset without any issues?

#2376121

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+01:00)

I'm sorry about your experience.

I have contacted the Documentation team and asked them to take down the Avada page, given the lack of input from the developers in fixing the issue.

It is possible to use Avada and Toolset together, but not to design Content Templates with Avada, you would need to design the templates with the block editor, for example.

We have a recommended themes page (Avada isn't on it): https://toolset.com/documentation/recommended-themes/

Given your experience with Avada, I would suggest checking the errata page for any open issues with any theme that you choose: https://toolset.com/errata/

#2378109

My issue is resolved now. Thank you!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.