Hi,
I am not sure what the problem is, but I cannot get the page builder to show two discrete columns. I get one column of any size on the left or right but then thinnest column appears below it, not beside it. I have tried all settings. Is this a known issue?
Thanks,
luca
Hi,
The theme’s blocks are designed and work better when using this page layouts: http://screencast.com/t/b6t7GCMG0W so please make sure that you set one of those layout for your page then also use the full width template(without sidebar) for a better view: http://screencast.com/t/OQzWeKCf
Other layout can also be used but not all blocks would behave well when using them and you would need additional styling to make them fit well on page.
Hope this helps!
Thanks
Hi Lucian,
Thanks for the reply. I believe it may be some sort of incompatibility with Nginx which is what my web server is running on. I may try switching to Apache to see if that fixes the problem.
Also, this appears to be an issue specific to the Visual Composer column function.
Thanks,
Lua
Hi,
We haven’t had any similar reports and we also haven’t made any tests using on an Nginx sever configuration, so I can’t offer you an exact answer on that, but if your web server causes this I suggest you also go trough you server configuration.
Please also try to remove and re-install the Visual Composer plugin and check if this happens again.
Thanks
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.
