[Resolved] Problems between Content Templates and WPBakery Builder

[Author]

Posts

[ROTOTOM]

I am trying to: edit with WPBakery Page Builder the content templates we already created.

Link to a page where the issue can be seen: all the content templates. Link to an example (it's a test template, not published)
hidden link

I expected to see: we expected to be able to edit the template, adding/editing elements with WP Bakery

Instead, I got: the WP Bakery Builder editing page is empty, even if the Content Template already has come content. If we try to add new elements nothing happens (no WPBakery popup).

There are no errors or warnings in the WordPress Debug Log. The only issue we've seen (using the Chrome inspector) is the one you can see in the screenshots attached (one is the error, the other one is where Chrome positions the error).

This issue doesn't appear in all other places where WPBakery is in use (posts, pages, ...).

Thank you.

[Waqar]

Hi,

Thank you for contacting us and I'd be happy to assist.

Based on your report, I was able to reproduce this behavior on my test website too and it seems it is not possible to edit a content template using the WPBakery Page Builder.

Thank you for bringing this forward. I've shared this with the concerned team and will keep you updated through this ticket.

regards,
Waqar

[ROTOTOM]

Any update?

[Waqar]

Thanks for checking in.

This is already escalated to the compatibility team and is being worked on.
( ref: https://toolset.com/errata/can-no-longer-edit-content-templates-with-wp-bakery-page-builder/ )

I'm afraid, I don't have a time estimate to share at the moment, but, I'll keep you updated on the progress.

Thank you for your patience.

[ROTOTOM]

Any update on this?

[Waqar]

While the permanent fix for this is not scheduled yet, a quick fix patch has been added to the errata page:
https://toolset.com/errata/can-no-longer-edit-content-templates-with-wp-bakery-page-builder/

Please follow the steps suggested under the "Workaround" heading and let me know in case it doesn't work.

[ROTOTOM]

Thank you for your help. We tested and the "workaround" is working in Chrome, but not in Safari or Firefox. We are moving to another architecture next autumn but until this time we will need to continue using Wp Bakery with the content templates. Sorry for the inconveniences.

[Waqar]

Thanks for writing back.

I just tried editing the content template "Test" ( ID: 172207 ) in the latest Safari and Firefox browsers and it worked without any error.
( screenshot: hidden link )

This has to be cache-related and I'd request you to clear browser caches once more and then test the editing again.

[ROTOTOM]

We tested from two different computers, clearing caches several times, closing the browser and restarting the computer and the result was the same: it only works in Chrome.

[Nigel]

Hi there

I noted the problems you were having and went to have a look for myself on your site, testing in different browsers, and it didn't appear to work with any (Firefox, Safari, or even Chrome).

So I wanted to double-check that the patch with the fix had been applied correctly.

I installed a special plugin that displays in the admin toolbar which Toolset plugin the common code is coming from (it's called Toolset Common Status).

That showed the common files are being supplied by the Views plugin.

I don't have FTP access, so I added the Filester plugin to be able to apply the patch, but when I uploaded the file I'm not sure what happened as it has produced a fatal error on your site.

Without FTP access I can't fix the problem.

So—first—sorry that happened, you'll need to fix that error yourself using FTP.

Please simply delete the Views plugin (plugins/wpv-views).

I expect that should restore your site (minus Views).

Then install this version of Views on your site (upload via the Add New plugins page): https://toolset.com/patches/wp-views-patched.zip

Clear your browser cache and test editing the content templates again.

If you still have the problem, please confirm, and I'll take a copy of your site to investigate further, I want to get to the bottom of why the fix is working on our own test sites but not your site.

You can delete the Toolset Common Status and Filester plugins.

[Waqar]

{ticket status updated}

[ROTOTOM]

Hi Nigel, We did as you suggested in your message and recovered the site. But after installed the patched plugin nothing changed. We continue to see the wpbakery editor only when using Chrome.

Thank you for your help

[Nigel]

After I replied yesterday I did some more testing on a clean test site, and I can confirm that the patch to fix the issue does not work in Firefox (I tested it in Chrome and Safari, which both worked).

I've updated the erratum to mention this limitation, and passed details back to the developers so that they can revisit the problem and try to identify a solution which works in all browsers.

There's not much more we can do here to support you. I suggest you subscribe to the erratum comments, where any developments will be shared, and in the meantime you will need to continue to use the patch to be able to edit the templates with WP Bakery in Chrome. (Note that that partial fix won't be included in the upcoming releases, and you'll need to re-apply the patch after updating.)