Search Results for 'bakery'

Just updated the js-composer plugin following the directions from:

https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/

My Visual composer is still broken, showing the exact same behaviors as before: Trying to drag an column item bugs it out.

Should I update the entire theme instead?

Theme docs also helpful
https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/

Yes; you can update the plugin by itself.

Theme docs are super useful also:
https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/

• This reply was modified 11 years by simchris.

I can update the WPBakery Visual Compose plugin without updating the entire theme?

http://www.international-pilot.com

Hello

I’ve been trying to get my site back to normal after carrying out the update but failed. I’ve just restored the site using a backup and it’s still not working properly.

The Visual Bakery page builder is not showing at all. I’m unable to correct a problem with an extra Big Slide appearing under the correct one!

Could you take a look at it please and advise? I can give you the admin log-in.

Cheers!

DC

Thanks for getting back to us.

Just to be clear, to get the update for WPBakery’s VC I will have to re-download the theme files from Envato Marketplace once you made the update?

I assue it will have to be done this way, because in order to get updates fro WPBakery one must ‘register’ the plugin with them, but this one came with the theme.

Also, how will we be notified of a theme update? Through the WP update manager?

Thanks.

yes, i have updated to WordPress 4.1 .. WPBakery Visual Composer update alredy available od codecanyon.. Shall we update it or just hold?

OK SOLVED!!!! It took me hours…. literally two days of work to narrow this down. Basically there are two database entries that could be put into the WP_OPTIONS table that specifically relate to WordPress Bakery’s Visual Composer.

In my case the two database entries specifically set parameters for the Columns and Rows of WPB’s Visual Composer. Of course components of “Pages” built on this theme use the columns from the Visual Composer.

Deleting those two entries will fix the problem.

This is likely going to be rare for most, unless you are moving directly from Newspaper and had configured some Column and Row functions in the Visual Composer.

I found this by installing a fresh copy of WordPress onto the same NGINX system and comparing the database entries in the old and new instance.

I imported the old database tables into the new one to see which one broke it. Once the options table was imported that caused the rendering issues. Going through hundreds of lines, I found the two responsible.

Easy way to find them is search for an “Option Name” with %___% wild cards in phpmyadmin. Use this specific term “wpb”.

You may get several options listed in rows in the output. The ones with Column and/or Row specifically in the Option Name should be deleted.

Actually you “can” delete all related options but keep the “wpb_js_templates” option as that is common to both a fresh install and a legacy install.

Well, now rendering is fixed for pages and columns and rows work as expected! Yay.

PS: This has nothing to do with NGINX. I confirmed the exact same issue is present on both Apache 2.4.10 with MPM-Prefork and PHP-FPM.

OK SOLVED!!!! It took me hours…. literally two days of work to narrow this down. Basically there are two database entries that could be put into the WP_OPTIONS table that specifically relate to WordPress Bakery’s Visual Composer.

In my case the two database entries specifically set parameters for the Columns and Rows of WPB’s Visual Composer. Of course components of “Pages” built on this theme use the columns from the Visual Composer.

Deleting those two entries will fix the problem.

This is likely going to be rare for most, unless you are moving directly from Newspaper and had configured some Column and Row functions in the Visual Composer.

I found this by installing a fresh copy of WordPress onto the same NGINX system and comparing the database entries in the old and new instance.

I imported the old database tables into the new one to see which one broke it. Once the options table was imported that caused the rendering issues. Going through hundreds of lines, I found the two responsible.

Easy way to find them is search for an “Option Name” with %___% wild cards in phpmyadmin. Use this specific term “wpb”.

You may get several options listed in rows in the output. The ones with Column and/or Row specifically in the Option Name should be deleted.

Actually you “can” delete all related options but keep the “wpb_js_templates” option as that is common to both a fresh install and a legacy install.

Well, now rendering is fixed for pages and columns and rows work as expected! Yay.

PS: This has nothing to do with NGINX. I confirmed the exact same issue is present on both Apache 2.4.10 with MPM-Prefork and PHP-FPM.

You don’t need a license key for this theme.
You may find it useful to peruse the “documentation” for the theme.

See the links on right side of this page “Documentation > Newsmag” for more help.

Specifically, this help doc will answer your questions on licensing:
https://forum.tagdiv.com/how-to-update-visual-composer-plugin-wpbakery/

You cannot “auto update” the version of Visual Composer which is “bundled” with the theme, as it’s a bulk license, not an individual license per user. The only way to update it is to wait for next theme update, which will have the tested/approved bundled/licensed version with it.

• This reply was modified 11 years by simchris.

Bumps don’t do anything.

The theme cannot suddenly cause something to stop working.

1) did you update something else recently that might have broken Visual Composer?

2) did you try removing the visual composer plugin (js_composer) from your plugins folder, then reinstall the version which comes with the theme?

YOU SHOULD BE USING THE VERSION WHICH IS INCLUDED WITH THE THEME FOR SITE TO WORK PROPERLY AND IT DOES NOT NEED A LICENSE. REMOVE YOUR LICENSED VERSION AND USE THE ONE INCLUDED WITH THE THEME, WHICH NEEDS NO LICENSE KEY.

See the theme docs for more info on using Visual Composer with the theme and licensing information:
https://forum.tagdiv.com/update-the-visual-composer-plugin-wpbakery/

If something “suddenly” stops working, this is due to action on your part or something you have installed, updated, or modified. The theme isn’t secretly changing things behind your back to turn things on and off. It’s not technically possible.

• This reply was modified 11 years by simchris.

I use 4.6, but on theme panel I see Version: 4.5d.

Active plugins,

tagDiv speed booster;
WPBakery Visual Composer.

I try to switch off all plugins, same problem.