Sauter la navigation

[Résolu] References to Fusion Builder should be replaced with Avada Builder

This support ticket is created Il y a 4 années. 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.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Ce sujet contient 5 réponses, a 2 voix.

Dernière mise à jour par simonM-5 Il y a 4 années.

Assisté par: Christian Cox.

Auteur
Publications
#2035825

HI Christian

With the latest update, I am able to use the Fusion Builder again to update the Content Templates (awesome!), however:
b) Avada has renamed their builder to "Avada Builder", I think all references to "Fusion" should be updated to "Avada". This will confuse new users of Avada who will never come across the outdated term "Fusion"

Thank and regards
Simon

Les nouveaux fils créés par Christian Cox et associés à celui-ci sont repris ci-dessous :

https://toolset.com/fr/forums/topic/content-template-editor-setting-for-fusion-builder-does-not-persist-in-toolset-settings-general/

#2036677

Okay I have reported this issue to my 2nd tier support team, who will forward the issue to our developers. Since it's not a blocking issue, I think we can close out here. Our developers will address these text changes in a future release of the plugins. Thanks for the report!

#2036829

Please note I have split the template editor settings persistence issue into a separate thread.

#2039053
Screenshot 2021-05-01 at 15.57.41.png

Hi Christian

Here's another caption/label that should be updated too, I think.

Kind regards
Simon

#2039707

Yes thanks, I included this in my initial report. My second tier team has acknowledged the issue and asked our developers to correct these text strings in a future update.

#2040651

My issue is resolved now. Thank you!