22690 comments found.
Hi,
The element “Empty Space” is stripping down valid measurements such as “em” or “rem” that are used for mobile/tablet/desktop spacings, and is simply converting them all to pixels. All spacings on our websites are now messed up.
2rem converts to 2px
Please can I get an estimate on this fix?
Thank you
Hello, This issue has been identified as a bug and we are planning to release an update this week with a fix for it.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
The latest update of WP Bakery to version 8.0 seems to have downgraded some features that used to be very useful.
1. The shape divider feature on content elements no longer exists, causing a lot of the shapes I used on my website has now disappear
2. Once the plugin have been updated to WP Bakery 8.0, all my background colour on row elements that used to be full width have been squeezed to a boxed element. I need to go through each row element on every single page of my website and adjust it to become a stretched row. This is causing a lot of hassle.
3. The colour element on text box. This is super frustrating when I need to type any texts that is white in colour on a white background. I would prefer the previous feature where I can set the text colour that was located just below the text typing area.
I hope WP Bakery team can reconsider and get these problem fixed.
Thank you 
Hello,
1) The shape divider is not a standard feature of WPBakery Page Builder. It looks like it is something added by theme or a third-party plugin, on your setup.
2) There were no changes made to the row layouts in the latest update. Please use support.wpbakery.com and share your temporary website credentials so our support team can investigate your issue and help you out.
3) We will add this suggestion onto our list so that it can be checked further.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Does anyone have a problem with the color picker adding the #111111 color to all the existing custom headings? It started with the 8.0 version on all our websites. We had to revert the plugin to the previous version to fix it.
Hello, Yes, this issue with custom headings has been identified as a bug and it will be fixed in the next release.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Few things about the new release update:
1. You fixed the Save Changes bug that was plaguing the back end. Thank you.
2. Images now on Chrome that are set to size “full” are squishing the height down in half (300×300 spaced out image now is 300×150). Please fix
3. Text Editor now dumps in an “ ” after every edit. Pretty frustrating to have to go into the text editor every time and remove this. Every save adds another   to the stack too. This bug was prevalent before when adding videos via WP Media and has since been fixed. Same issue now plagues Text :/
Hello, Unfortunately, we have not encountered such issues or received any reports of it. The support team will be glad to investigate it further to locate their exact cause. Please use support.wpbakery.com and share your temporary website credentials so it can be debugged further.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Hi!
There’s an issue in the file “class-vc-modification.php”. Actually it outputs a non-standard script type “text/html” in the following line: <script type=”text/html” id=”wpb-modifications”> window.wpbCustomElement = 1; </script>
This causes trouble with caching plugins as it can’t be parsed correctly. Can change it for now, but that’s not working for updates for sure.
Please fix that. Thanks in advance!
Hello, Please use support.wpbakery.com and share your temporary website credentials along with the steps that can be followed to replicate the issue, so our support team can investigate it further.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Vc_Post_Admin->save() does not property check if the user is saving in quick edit mode aka $_POST[‘bulk_edit’] – so it’s running for no reason, which is especially bad when bulk editing a lot of posts.
It also causes an issue where _wpb_vc_js_status gets deleted.
- AJ
Hello, It will be helpful for us if you can share the steps that you are following to replicate the issue so that we can execute them at our end to check it further.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
If you forward my comment to the developers they should know exactly what to do 
But here are steps:
- Open the file at js_composer/includes/classes/core/class-vc-post-admin.php
- Locate the save method on line 96
- Inside the function before the closing bracket add the following:
error_log( 'this code should not run here' );
- Go to your WP admin and quick edit or bulk edit any posts.
- Open your error log file and you can see the text “this code should not run here” printed in the logs.
WPBakery should be adding checks so that the safe function doesn’t run when making quick or bulk post edits on the site because it’s not necessary. It also causes the _wpb_vc_js_status custom field to save when it shouldn’t. This means if you edit a post with WPBakery, then later you quick edit that post the next time you open the post it won’t open with WPBakery enabled because when you quick save the post it will have reset the value of _wpb_vc_js_status.
As I mentioned, I would be more then happy to submit pull requests with these fixes so your developers don’t even have to worry about it. But the private repo seems abandoned.
- AJ
Hello, Thanks for sharing further details. I got a confirmation from our development team that the private repo will be updated soon and you can then submit the pull requests there.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Hi, We have updated the private repo.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Hey guys.
the 8.0 version no longer works with vh (vertical height). I have to enter px (pixels). Why?
Hello, We have identified this issue with the empty space element and it will be fixed in the upcoming release.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Thank you!
Thanks for the update!
Just wanted to mention a few things (not necessarily related to this update)
- Even though you are using a new color picker you still have wp-color-picker and farbtastic as script dependencies. Shouldn’t be necessary. There is also a bit of old CSS related to wp-color-picker still in the plugin that isn’t in use anymore.
- The 15px font size applied to ”.vc_navbar .vc_dropdown .vc_dropdown-list a” in the frontend editor doesn’t work correctly because core WP styles set the inner p elements to 13px – https://a.cl.ly/DOu1OGAN
- WPBakery loads the Roboto Google font only for use with the insert element window. Wouldn’t it be best to just use the core WP fonts (it’s very similar anyway). This way customers in China that can’t use Google fonts won’t have issues and it keeps things a bit faster by not having to make requests to 3rd party scripts. Alternatively you could dump the font inside the plugin, but that seems like added bloat for something that should just use the default admin font family.
- AJ
ps: I would be more then happy to submit pull requests with fixes. I love WPBakery and I don’t mind spending my time to help make it even better – but the private repo is quite outdated and perhaps no longer maintained.
Hello, Thanks for sharing the feedback. We will pass this on to the concerned authority along with your offer to submit the pull requests.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
It’s better for mobile now but the design options and the 3 dots next to it doesn’t work in Google chrome for android. Just letting you know.
Hello, Thanks for sharing. We will add it to our list to investigate it further and improve accordingly.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
I still get a PHP error when using PHP 8.2 as below. PHP 7.4 works fine without error but my hosting company is depreciating this.
ERROR (on latest plugin version): An error of type E_ERROR was caused in line 13 of the file /public_html/wp-content/plugins/js_composer/include/templates/editors/partials/vc_welcome_block.tpl.php.
Error message: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /public_html/wp-content/plugins/js_composer/include/templates/editors/partials/vc_welcome_block.tpl.php:13
Stack trace: #0 /public_html/wp-content/plugins/js_composer/include/helpers/helpers.php(1091): require()
1 /public_html/wp-content/plugins/js_composer/include/templates/editors/backend_editor.tpl.php(55): vc_include_template(‘editors/partial…’, Array)
2 /public_html/wp-content/plugins/js_composer/include/helpers/helpers.php(1091): require(’/home/customer/...’)
3 /public_html/wp-content/plugins/js_composer/include/classes/editors/class-vc-backend-editor.php(120): vc_include_template(‘editors/backend…’, Array)
4 /public_html/wp-admin/includes/template.php(1456): Vc_Backend_Editor->renderEditor(Object(WP_Post), Array)
5 /public_html/wp-admin/edit-form-advanced.php(723): do_meta_boxes(Object(WP_Screen), ‘normal’, Object(WP_Post))
6 /public_html/wp-admin/post.php(206): require(’/home/customer/...’)
7 {main}
thrown
Hello, If the issue persists at your end with the 8.0 update, then please use support.wpbakery.com and share your temporary website credentials so our support team can investigate your issue and help you out.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
THANK YOU WP BAKERY as literally one of my ALL TIME 3 GODSEND Plugins EVER IN THE WORDPRESS WORLD!!! Elementor still so frickin Unstable, most every site I’ve built with themes based upon constantly breaks with white page ‘critical errors’ from PHP, hosting, theme or other plugin updates YOU GUYS ARE ROCK SOLID for what like 10 years I’ve been using my Fav Themes based upon (Like SALIENT, MoveDo, Crocal, etc) #GRATEFUL100 #PRICELESS
Hello, Thank you for the kind words. We’re thrilled to know that WPBakery has been a reliable part of your journey for so many years. Your trust and appreciation mean the world to us, and we’re grateful to have you as part of our community.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Absolute best editor for wp. Period. I do have an issue that I’m seeing lately where I can choose my fonts and the weights in the ultimate add-ons google font settings in The7 theme but when I use the wpbakery “headings” object and use the drop down on the typography tab to choose one of those fonts, the different weights/styles that I selected for that font don’t show up, just the standard three, underline, italic and bold. I used to be able have all the styles, such as for Open Sans, 100, 200 – 800 etc.
Hello, Thanks for the kind words. The core plugin and addons both load fonts differently. Due to this, the fonts from one are not available in the other. We have a big update coming up in our next version 8.0, that will allow users with active support to load custom font libraries including Adobe fonts and Google fonts (including missing fonts).
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
I’m sorry, my mistake, the widget I use is the Ultimate Addons Headings widget, not WPBakery’s widget, I’ll post this on their section. WPBakery is simply the best worpdress plugin for professionals who design websites!
Hello, a long-awaited rant over here: When will you have a decent code editor for the html widget? Do you REALLY find an #AAAAAA 11px Courier New font on a white background any legible? I am literally burning my eyes every time I need to create my own code on the website just to create stuff because your widgets are so poor in customization.
I don’t mean to diminish your product pros, because it is a pretty good tool in several terms, but hey, I need to take care of my eyes and my work environment, and your terrible selection of contrast and colors of the HTML widget is driving me insane and forcing me to install a backend UI editor and then have a custom code for every website we use Wpbakery.
Hi, The purpose of the Raw HTML and Raw JS elements was to allow quick copy-pasting of code snippets directly onto the page. The current styling is designed to display more code with a quick glance for convenience. However, we have noted the need for improved display styles for these elements and other code input areas. Enhancing these areas is on our roadmap to make them more user-friendly for those who frequently interact with them.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
I, like everyone else here, am having the same “save changes” bug. No matter what browser, I go into the editing window, make my changes, go to save and nothing happens. I have to copy my work, close the window, open again and paste and then save again. Has been happening for months now. Please fix.
Hello, If the issue started after the latest release (7.9), then it has been identified as a bug and will be fixed in the next release. However, if the issue existed before the latest update, then it might be something different. In such a case, please use support.wpbakery.com and share your temporary website credentials so our support team can investigate your issue and help you out.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
I figured out that the Conditionals for User Roles are not working sufficiently. When you say “Include User Roles A & B” AND “Exclude User Role C” it shows the content if first condition is fullfilled. This is not what the logic would expect.
Hello, Please provide us with the steps that can be followed to replicate the issue so that it can be investigated further.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Well, I use the “Display logic” to make conditional visibility. When I say “If EVERY condition below is met” and choose condition 1 as “role includes A & B” and condition 2 as “role excludes C” it should mean, that all users in A & B & NOT should see the part what won’t happen. In my installation every A & B will see this, independent of C … this is a fail when you say “EVERY CONDITION BELOW IS MET”
Hello, It would be helpful if you could drop a ticket via the customer center: https://support.wpbakery.com/ and share the code that is being used. This will enable us to replicate the issue and investigate it further.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Any timeline on the upcoming update to fix the bug with Safari?
Hello, The issue with the backend editor not rendering correctly in the recent safari version was added for our upcoming release. However, while debugging it the development team found that the actual cause of issue is the bug in WordPress release with safari: https://core.trac.wordpress.org/ticket/62082 It will be fixed in the WordPress 6.7 release.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Save Changes issue is still ongoing with version 7.9
Hello, Please use support.wpbakery.com and share your temporary website credentials so our support team can investigate your issue and help you out.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Stop putting notices and advertisements within WordPress installs
Hello, You can disable the notice in the dashboard by using the close option in it’s top right corner. This option will be saved and it will not display the notice when you log in again.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
That’s not the point. Plus subsequent “ads” will still show up.
Hi the save button bug come back with the 7.9 version ! Can you fix it ? It’s really borring. THX !
As someone before told you :
The save button doesn’t always work. E.g. you create new text content, write something down and want to save it. Unfortunately. You press save and nothing happens. But if you press close and then edit this text content again and then click save, the save button works and it takes over the content. It’s very annoying. Is there a workaround so that it always works? The error only exists since the update to 7.7 and also to 7.7.1
Hello did you see my message ??
Hello, Please use support.wpbakery.com and share your temporary website credentials so our support team can investigate the issue further.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
J’ai le plugin au travers d’un theme acheté… Je ne peux pas, j’ai déjà essayé. Mais de toute les façons je ne suis pas le seul j’imagine à avoir ce problème. Dans les versions précédente vous aviez déjà eu ce bug.
Hello, This bug was present in one of the previous releases. However, it was fixed in it’s next update. Since the issue on your setup still persists with the latest version of the plugin, it will be helpful if we can debug it further to locate it’s exact cause on your setup. The plugin which comes with the theme does not have a license of it’s own. Due to this, it’s support access is restricted. Purchasing the direct license of the plugin will allow you to access the support portal. The direct license will also provide you with added benefits as mentioned here: https://kb.wpbakery.com/docs/faq/what-are-the-benefits-of-direct-license-for-wpbakery-page-builder/
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Hello, Team!
Your plugin has bug with the “Custom JavaScript before body” option regardless of used theme, check the screencast with Twenty Twenty-Four theme: https://somup.com/cZ66oKH33A
When the fix will be released?
We are aware of this bug and it has been added to our To Do list. This will be fixed in a future release.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
This item was featured on CodeCanyon
Power Elite Author
Contact the Envato Market Help Team
