[Resolved] Cannot edit Content Templates with Avada Builder (since latest Toolset updates?)

[Author]

Posts

[simonM-5]

Dear Support

I've discovered a weird behaviour with Content Templates and using Avada. I wanted to edit a Content Template, but when I click "Edit with Fusion Builder" button I land on the same page again.

I double checked the setting under Toolset > Settings > General > Editor to use for Content Templates and set it to Fusion Builder, but when I refresh the page it reverts to Classic Editor again.

This has led me to be unable to edit my Content Templates I created previously using Avada Builder.

I thought this may have been due to having switched recently to Avada Child theme, but I reverted back to Avada theme to test and the behaviour is the same.

I tried adding the code from

https://toolset.com/forums/topic/content-templated-cannot-be-edited-with-avada-fusion-builder/

in the child functions.php, but that didn't help and also have added it as as custom code snippet and it still doesn't work in either Avada or Avada Child theme.

Is this caused by the latest plugin updates? Are there any workarounds?

Thanks and regards
Simon

[Christian Cox]

Hi, I tried the same process and noticed the same behavior in my local test site. Let me escalate this to my 2nd tier support team for additional investigation. We may be able to produce a workaround or another custom code snippet solution. I'll let you know what I find out.

[Christian Cox]

Hello, I have a quick update. Our 2nd tier support team has confirmed this behavior begain with the Blocks 1.5 / Views 3.5 release. We have escalated the problem to our developers and published a related erratum post here: https://toolset.com/errata/cannot-edit-content-templates-with-avada-fusion-builder/

Thank you for reporting this Avada builder compatibiity problem. I will continue to keep you up-to-date here as I receive more information, like if a patch is generated or if another workaround is available.

[simonM-5]

HI Christian

Thanks for the update. I am trying to downgrade to Toolset Blocks 1.4.2 downloaded from your site, but when I try to install it, it gets stuck with the attached screenshot..

I'm just using Plugins > Add New and uploading the zip file. Is there something else I should be doing, or do I need to deactivate 1.5 version or something first?

Thanks and regards
Simon

[Christian Cox]

I'm just using Plugins > Add New and uploading the zip file. Is there something else I should be doing, or do I need to deactivate 1.5 version or something first?
Yes, you should definitely deactivate and delete Toolset Blocks version 1.5 before installing version 1.4.2, regardless of the installation method. However, if the problem shown in your screenshot is displayed again after deactivating and deleting version 1.5, there may be another issue. This error message comes from WordPress and it can be a bit misleading. Usually when I see this error during plugin uploads, the problem is actually a limitation on the maximum accepted file upload size. This limitation is established by configurations on the server, and varies per site installation. The Blocks plugin is slightly larger than 11MB, and some hosts set a 10MB file upload size maximum by default. In those cases, you have some options:
- You can ask your hosting provider to increase the maximum allowed file upload size for this site - a setting called upload_max_filesize - to something like 20MB. You may need to submit a support ticket with your hosting provider to get this changed.
- You can ask your hosting provider if they offer a feature to upload and automatically extract zip archives from your site's control panel without requiring FTP. Your hosting provider may or may not offer this capability. If they do offer this feature, you can upload the entire Blocks plugin zip archive to the wp-content/plugins directory, then use the automatic extraction tool to automatically extract the archive. This article describes the process in a common Control Panel application "cPanel", but your environment may be different:
https://smallbusiness.chron.com/upload-zip-files-cpanel-45042.html
- If the two previous options are not available, the fallback is to extract the downloaded plugin zip archive on your computer, then upload the extracted toolset_blocks directory to your site using FTP. The entire toolset_blocks folder should be uploaded into the plugins directory at wp-content/plugins, as shown in the screenshot.

[simonM-5]

HI Christian

Thanks for the info, I checked on our server, it was set to 8 MB so that's what the issue will have been.

As we aren't live yet, we can hopefully hold out until Toolset fixes this glitch with the Avada Builder. Is there any estimate of the time on that (I appreciate you can't give exact dates, but the errata says you guys are working on it urgently, so does that mean days or weeks?)

I also can use the workaround of using Toolset blocks to create the Product Content Template in the meantime, although there are formatting issues with those blocks too. We have many other Woo issues we are solving one after the other. Woo is seriously buggy! 😔 Let's hope they get their act together a little better, now that they are an integral part of WP.

Thanks and regards
Simon

[Christian Cox]

Okay good to know about the upload size. I expect the Avada CT fix will be available in days rather than weeks, we're in the process of testing those fixes now and hope to have a release ready very soon.

[Christian Cox]

In fact, I've been informed these fixes are being pushed out today. If you're not prompted to update yet in wp-admin, you may need to go to Plugins > Add New and click the Commercial tab. Then scroll down to the Toolset installer and click "Check for updates". Please update to the latest versions and let me know if you are still unable to edit templates with the Fusion builder.

[simonM-5]

HI Christian

With the latest update, I am able to use the Fusion Builder again to update the Content Templates (awesome!), however:
a) under Toolset > Settings > Editor to use for Content Templates, the setting is still not being preserved when changing to Fusion Builder. When the page is refreshed it is still going back to Classic Editor.
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

New threads created by Christian Cox and linked to this one are listed below:

https://toolset.com/forums/topic/references-to-fusion-builder-should-be-replaced-with-avada-builder/

[Christian Cox]

Okay thanks for the update. I'll split off another ticket for that issue and raise it to my 2nd tier team.

[simonM-5]

Hi Christian

As this is now possible, I agree, this can be closed now.

Best regards
Simon

My issue is resolved now. Thank you!