Visual Composer Non-Compatibility

Nope, I guess not.

Just tried it, and it still shows the Visual Composer codes.

Hi

Indeed the developer mode will only cause your AMP pages to be invisible from search engines until the time you’re ready to disclose them, and add also validation buttons.

If Visual composer – or rather WP Bakery, does not transform its codes into a normal page content, the common reason is that it’s not installed as a regular plugin but instead as part of your theme.

On AMP pages your theme is not used at all so it’s a bit as if WP Bakery is just not there.

To workaround this, you should go to the Plugins management and Theme management sections of the “Comments and plugins” tab of weeblrAMP configuration and make sure that:

– the WP Bakery plugin is not disabled on AMP pages
– the theme is not disabled on AMP pages

See documentation on this page: https://www.weeblrpress.com/documentation/products.weeblramp/1/going-further/comments-plugins/index.html

Did not mention it but of course, you’ll have to be running the current WP Bakery plugin, not an outdated version.

Hope it helps

Best regards

Hi,

Yes, I tried all of the above options and it still just showed the VC codes.

It seems the problem I’m going to have – according to your reply – is that I’m using a theme that has VC built in, and it’s only updated when the theme gets updated.

Mind you, better that the errors arose now, than me coming in here with codes problems when a new version of VC is available and waiting for the theme to update, yes?

Hi

Using the latest version is not an issue per se, codes not being replaced by WP Bakery should not happen, unless you have:
– disabled your theme
– or disabled the WPBakery plugin
on AMP pages.

As it does happen, advising to use the current version, the one we test with, is the first thing that comes to mind if only to work on a level field.

And as this does happen, there’s something else going on, most likely caused by the way your theme is built/how it interacts with WordPress. Another common cause is of course interference with other plugins, so trying to disable them one at a time may provide useful information.

Best regards