Rohan Khandeparkar

Hello,

There can be such an issue if the page is built using Visual Composer and then edited using the default WordPress editor. This is because the Visual Composer elements which are stored as HTML can break when the same page is saved via another editor as each editor handles the HTML content in a different manner.

Thanks,

Hello,

The server memory limit is the global value.
The plugin checks for the local memory limit set for the particular website.
Please make sure that it is set to 256M as well.

Thanks

Hi,

The Page shared is built using the WPBakery Page Builder plugin: https://wpbakery.com/
Please note that WPBakery Page Builder and Visual Composer Website Builder: https://visualcomposer.com/ are two independent plugins.
The former works using shortcodes while the latter works using react-based rendering.
You can check the detailed differences between the two here: https://help.visualcomposer.com/docs/getting-started/visual-composer-vs-wpbakery/
As the website is built using WPBakery Page Builder, we can recommend contacting it’s support.

Thanks,

Hi,

Please make sure that the pages are selected under: Visual Composer -> Role Manager, for the editor to be able to add/edit them.

Thanks,

Hi,

That is strange as it is displayed in the browser inspector. I would request you to kindly drop us a ticket via the official support channel:?https://help.visualcomposer.com/support?regarding the issue.

Thanks,

Hello,

The issue is due to this li tag which is added within the ul: https://i.imgur.com/5tnueX2.png
You can edit the text block in which the list is added and remove the extra li added to it.

Thanks,

Hi,

I would request you to kindly drop us a ticket via the official support channel: https://help.visualcomposer.com/support regarding the issue.

Thanks,

Hello,

Please make sure that the elements such as global template are downloaded from the hub and are available in add element area.

Thanks,

Thank you for taking the time to leave us a review.

Hello,

The limited support majorly covers any pre-sale questions. We also actively maintain the free version and support issues such as bugs, fatal errors, etc. arising from it.
There is no restriction on the number of tickets in premium support. It covers any issues related to the plugin.
You can check our support policy: https://help.visualcomposer.com/support-policy/ to see what exactly premium support covers.

Thanks,

Hi,

Thanks for trying the Visual Composer plugin. The free version of the plugin comes with limited support and covers any pre-sale questions.
The premium version comes with priority support for any issues related to the plugin. The support is exclusively provided via the ticket system which is accessible at: https://help.visualcomposer.com/support/ using a premium license.

Hi,

The warning message is coming from WPBakery Page Builder plugin.

Please note that the WPBakery Page Builder: https://wpbakery.com/ and Visual Composer Website Builder: https://visualcomposer.com/ are two independent plugins.

The former works using shortcodes while the latter works using react-based layouts. You can check the differences between the two here: https://help.visualcomposer.com/docs/getting-started/visual-composer-vs-wpbakery/

Hello,

The plugin used on your setup is WPBakery Page Builder.

Please note that the WPBakery Page Builder: https://wpbakery.com/ and Visual Composer Website Builder: https://visualcomposer.com/ are two independent plugins.

The former works using shortcodes while the latter works using react-based layouts. You can check the differences between the two here: https://help.visualcomposer.com/docs/getting-started/visual-composer-vs-wpbakery/

Thanks,

Apologies for the inconvenience caused.

1. We had such an issue with undo feature a long time back if the undo button was clicked repeatedly. This was fixed in 42.0 update.

2. The row height depends upon the amount of content present within it. It can be also adjusted by adding an empty space element within a row.
3. The vertical spacing between the elements is set to 30px by default. This is to give them breathing space when displayed on the page. This can be easily removed by setting the margin-bottom to 0px under the design options of the element.
4. The page content is stored in the database. As long as any plugin install or update does not affect the database, the page content will remain the same and will display as it was saved.
5. The database size depends upon the amount of content added to the site. This can also vary depending on the type of content such as images.
6. The Visual Composer is coded as per the WordPress development guidelines and it works fine with most plugins that follow these guidelines. We also ensure to test it with major plugins to ensure compatibility. However, there can be js conflicts with plugins if they are not updated for a while.

Hi,

The screenshots are of the WPBakery Page Builder plugin.
Please note that the WPBakery Page Builder: https://wpbakery.com/ and Visual Composer Website Builder: https://visualcomposer.com/ are two independent plugins. The former works using shortcodes while the latter works using react-based layouts. You can check the differences between the two here: https://help.visualcomposer.com/docs/getting-started/visual-composer-vs-wpbakery/

Thanks,