22688 comments found.
Hello, since version 8.7, I’ve had a major problem: I can’t edit previously created pages. The plugin gets stuck with the loading image. I had to rollback to version 8.6. I’ve tried updating to version 8.7.2, but the problem persists, my website have cocoon theme
Please create a support ticket at support.wpbakery.com with your site credentials so we can check and help you with this. You need to log in to support.wpbakery.com with the email address using which the license was purchased.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
My first license came bundled with the theme. Since I was having problems, I purchased a new license from wpbakery.com. The year of support included with the license has expired, and now that I’m having a problem following your update, I’ll have to spend another $59 to open a ticket. No thanks, that means I’ll have to choose a different editor when I update my site’s graphics.
Could you please share a screenshot of how the editor appears on your end? Also, have you tried switching to a default WordPress theme (like Twenty Twenty-Five) and deactivating other plugins except WPBakery to check if one of them is causing the issue?
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, please note that since the latest update, if I open the Row Custom Layout popup, I can no longer open the Row Settings popup until I manually close the first one. Here is a video for reference (basic theme installed, no other plugins than WPBakery): https://undsgn.d.pr/v/QM4wEY
Could you please advise?
Thank you in advance.
Hello, Thank you for sharing the details and the video reference.
We’ve tested this behavior across several past major releases, starting from version 7.8, and can confirm that it has worked in the same manner in all of them. This means it is not a new bug introduced in the latest update.
If you’d like to see such an ability as a feature in the future releases, we’d recommend submitting it as an idea here: https://support.wpbakery.com/roadmap-submit
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, thank you… My mistake: I initially assumed the behavior was consistent between the backend and the frontend. You’re absolutely right that this has always been the case in the backend. However, the behavior in the Frontend Editor has indeed changed with version 8.7.1.
Please see these two reference videos:
- Version 7.9 (same behavior up to 8.6): https://undsgn.d.pr/v/Pigx53
- Version 8.7.1: https://undsgn.d.pr/v/Ic1SgT
In previous versions the behaviour was very helpful for workflow. In the latest version, however, the second popup can’t be opened until the first is manually closed, which breaks the editing fluidity.
I understand this may not be classified as a bug per se, but since it is a regression in user experience for the frontend, I kindly ask that it be reconsidered internally, not just as a feature request but as a usability adjustment worth restoring.
Thank you again
Hello, Thank you for sharing further details. At present, both the backend and frontend editors exhibit the same behavior, which aligns their functionality. However, as per your feedback, I’ll add this to our internal list to review.
I’d also encourage you to submit this as a feature request, as such requests go through a voting process where users can support enhancements they find valuable. This helps us prioritize improvements that best serve the community’s needs.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
In the latest update, the following check:
'vc_edit_form' === vc_post_param( 'action' )
which previously worked, no longer triggers when first inserting an element on the page and the edit window opens immediately (aka not sections, rows, columns) as the action is now “wpb_add_element_edit_window_ajax_cache”.
This causes issues for example in vc_wp_custommenu element it won’t show the list of menus when first inserting the element: https://a.cl.ly/YEuE5xk1
So when you don’t have the element on the page and you insert it for the first time the ‘vc_edit_form’ action never triggers, thus the code used to get the menu items doesn’t run. If you refresh the page then ‘vc_edit_form’ does trigger.
Not sure if this is related to the bug I have where sometimes fields will reset (I’m having trouble recreating it consistently to record a video).
Any chance you could add a new helper function like wpb_is_element_edit_window() – this way we can easily check if currently in the edit element window.
Thanks!
- AJ
Sorry my video didn’t save correctly, here is the updated link: https://a.cl.ly/WnunLQ2P
Hello, We’ve reproduced the behavior you described and can confirm it as a bug introduced with the new update. It’s now on our fix list for 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.
Hi there! There’s a bug when you have 2 blocks and set the row to equal height and the content position to middle. Everything is set to top. Easy fix: .vc_flexbox_container_item, .vc_flexbox_container_item-inner, .wpb_wrapper { height: auto !important; }
Hello, Thanks for sharing. We are able to confirm this as a bug and have added it to the bug-fix list.
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 new WP Bakery is inserting empty HTML tags everywhere in the code, such as wrapping all HTML in paragraph tags and/or inserting br tags on every line break thus making all code completely invalid.
Hello, There was an issue with paragraph tag wrapping in the text block in the previous version of the plugin, which is 8.7.
This issue was fixed in the 8.7.1 release.
If you are still experiencing any issue on your setup, please open a ticket via the customer center and share the steps that can be followed to replicate it so that our team can investigate 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.
Thanks. The issue has indeed been fixed in the 8.7.1 release.
Not sure how to replicate it, but I’ve noticed in the latest version sometimes if you insert an element, edit it and then you click to edit the same element it resets the previously saved options.
Has anyone else reported this?
I’m guessing it’s related to the added caching mechanism.
I will try and recreate it so I can share a video.
- AJ
Hi, We haven’t received similar reports from other users so far. It will be very helpful if you could share the exact steps to reproduce the issue so our 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.
Here is a video using default WP theme and the text block: https://a.cl.ly/o0u0r5RY
Here is a video using a custom element: https://a.cl.ly/2NuDgn6b
If you notice it actually updates the shortcode because you can see it in the iframe, but clicking to edit again it’s loading the cached form without the previous edits.
I find it a bit tricker to re-create the issue with the default WPB elements and on the default WP theme – most likely because it’s faster as there are less shortcodes. But you can see it clearly in that first video.
I haven’t dug far enough in the code, but my guess is perhaps closing the element window after editing too quickly can cause the problem. Maybe related to waiting for an AJAX request or a setTimeout on the caching mechanism.
Thanks!
- AJ
Hello, Thank you for sharing the videos and additional details. We’ve tested the issue across multiple setups on our end following the same steps shown in your recordings, but we were unable to replicate the behavior.
That said, we’ll add this to our monitoring list to keep an eye on similar reports from other users. If it turns out to be reproducible under specific conditions, we’ll take the necessary steps to address it in an update.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Is there a way to disable the (i) tooltips on modules? They almost ways end up popping up when I am trying to add or edit a module field and in general, are more distracting and annoying than helpful. They end up blocking what I need to see. I think an improvement would have them placed at the far right or someplace out of the way to avoid this behavior, but a general setting to disable them completely would be good too.
https://snipboard.io/2qSGmM.jpg
function hide_tooltip_css() {
echo "
<style type='text/css'>
.tooltip-content {
display: none !important;
}
</style>
";
}
add_action( 'admin_head', 'hide_tooltip_css' );
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Hello, in version 8.7, when editing a text block in the code tab, saving doesn’t work after making some changes.
Please create a support ticket at support.wpbakery.com with your site credentials so we can check and help you with this. You need to log in to support.wpbakery.com with the email address using which the license was purchased.
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, thanks for the recent update. I’ve noticed a minor issue—although equal height columns and vertical alignment via flex are enabled, the columns aren’t aligning to the middle anymore as expected. Thank you.
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.
Sad to see people who purchased this plugin don’t get lifetime updates free of charge as stated on your item details page.
Hello, The plugin updates are indeed available for a lifetime and can always be accessed in manual form from your WPBakery account as per the second method here: https://kb.wpbakery.com/docs/getting-started/update/
Automatic updates within WordPress are tied to an active support tenure, which also provides additional benefits such as access to WPBakery AI, the font manager, template library, and direct support. However, this is optional and does not affect your ability to download and apply lifetime updates manually.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Nope on my site I have to upload the Wordpress plugin via my site I can’t update via my Wordpress dashboard
Hello, The manual updates are done exactly as you described. By downloading the latest plugin version from your WPBakery account and uploading it to your WordPress site. This method is always available and ensures you continue receiving lifetime updates.
The option to update directly from the WordPress dashboard (auto-updates) is part of the Support Plus package, which also includes AI, font manager, template library, and direct support. While convenient, it’s optional and does not affect your lifetime access to updates via manual installation.
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 is a bug with the CSS Box where if you don’t define a color for the border it will work the first time but it get’s reset when re-opening the window.
By default if the browser will use the currentColor if a border color is not defined, so we should be allowed to leave the border color option empty and allow the border color to come automatically from the text color.
Here is a video showing the issue using a default WP theme and no 3rd party plugins active: https://a.cl.ly/12u8l617
Since WPBakery has always saved the border width and style (even if a color was not defined) there could be many customers that did this and so the functionality should remain.
Hopefully this can be fixed in the next patch.
Thank you!!
- AJ
Doing some further testing, this seems to only be an issue with the border width is the same on all sides.
Hello, This issue has been confirmed as a bug, and it has been added to our bug-fix list so that it can be addressed in an update.
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 wanted to report an issue similar to what was mentioned some time ago regarding excerpts by another author. If I edit the title of a page or post using the Frontend Editor and add an apostrophe, the editor invariably adds a backslash, as shown here: https://undsgn.d.pr/v/oqivp4
Do you have any advice on how to handle this? Thank you.
Hello, This issue has been confirmed as a bug, and it will be fixed in the next update.
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 WPBakery Support Team,
We want to create an infinite loop with WPBakery carousel, so the rotation continues seamlessly. Currently, there is a large gap between the last and first item. Is there a built-in option or recommended approach in WPBakery to achieve a true infinite loop without this gap?
Thank you!
Hello, The current logic of the WPBakery carousel is based on the last carousel item reaching the first position, at which point the carousel resets to its original position. Because of this behavior, it does not support true infinite looping.
If you’d like, you can share this idea on our feature request board here: https://support.wpbakery.com/roadmap-submit so that our team can evaluate its implementation for future updates.
In the meantime, the available workaround would be to create a custom carousel element with infinite looping logic tailored to your needs.
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 WPBakery Support Team,
We’re experiencing an issue with the WPBakery carousel on mobile devices. The carousel displays oversized spacing (or padding) on initial load, creating large blank areas to the left or right. However, if the user taps the carousel, the spacing suddenly adjusts and behaves normally.
Here’s a video showing the behavior: https://drive.google.com/file/d/1Em4fTRNvdAhGqwSlzdW0-3XuD2yqlQTI/view?usp=sharing
We attempted various solutions (e.g., disabling lazy loading, adjusting CSS, re-initializing scripts), but the problem persists in multiple mobile browsers. Could you please investigate or let us know how to correct this?
Thank you!
Hello, Thank you for sharing the video. We can see the issue in the video you provided, however, we are unable to replicate it on our setup or on our image carousel demo page here: https://vcpreview.com/shortcodes/image-carousel/
To investigate this further, please open a ticket via our customer center: support.wpbakery.com and share your temporary admin login details along with the page URL where the issue occurs. This will allow our support team to check the configuration directly to 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.
I’m creating my theme from scratch and want to use your tools. I’ll be creating the theme on a subsite called new.detto.com.br and then moving it to detto.com.br. Can I purchase just one license and then migrate it?
Yes, you can buy a single license in this case. You can deactivate the license using the second method outlined in the following article: https://kb.wpbakery.com/docs/wpbakery-page-builder-how-tos/how-to-deactivate-and-reactivate-license/ and activate the license on your site by following the steps in this video guide:https://wpbakery.com/video-academy/activate-wpbakery-page-builder-wordpress-license/ while switching domains.
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, since the update to version 8.6 I noticed that in the cell layout it’s no longer possible to use definitions like span8 + span4. Instead, only fraction-based values such as 2/3 + 1/3 are supported.
This is unfortunately quite inconvenient, as the span notation was much clearer and more practical – especially when working with complex layouts. In version 8.5 this functionality was still working without issues.
Could you please check if it’s possible to bring back the “span” option, or let us know if there’s any workaround? Many users rely on existing layouts that are based on this system.
Thank you!
Sorry, it’s sorted now. It was the template, not the plugin.
Hi, we’ve noticed a problem since version 8.5. Content inserted in full-width rows doesn’t respect boxed formatting and is shifted to the left. The same thing happens in version 8.6. We found a fragment of the offending code in the file :/js_composer/assets/css/js_composer.min.css.
This statement:
.vc_row[data-vc-full-width-temp] { left: 0; margin-left: calc(-50vw + 50%); right: 0; width: 100vw; }
This statement causes the display problem with boxed content in full-width rows.
It appears to be a piece of temporary development code.
Removing the statement restores the display to its original state, as in versions prior to 8.5.
Hello, Thank you for sharing the details and pointing out the CSS fragment. We have tested this on our setup, but were unable to replicate the same issue.
To help you further, we would request you to open a ticket via our Customer Center: https://support.wpbakery.com/ and share your temporary website credentials there. This will allow our support team to investigate the problem directly in your environment.
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,
With one of your recent updates, there is a bug with the ‘textarea_raw_html’ field type. A shortcode using this field type, when inserted on a page, breaks the entire page when editing it in WPBakery, nothing opens in the admin, as if there is no content.
The issue is in the JavaScript file located at: wp-content/plugins/js_composer/assets/js/dist/backend.min.js This file needs to also handle the case for this field type.
The fix is relatively simple, all that needs to be added is shown here: https://monosnap.com/file/Q5OnVWPfDOQxf9wOICtg7s82L6LB2ZPlease check this and include the fix in one of the upcoming updates, as we are receiving a large number of reports about this issue across all our themes on all our ThemeForest profiles (Qode, Select, Edge, Elated and Mikado).
Best, Qode
Hello, Thanks for sharing the issue. However, we tried creating a custom element with ‘textarea_raw_html’ and then adding it to the page, but were unable to replicate the issue.
The element code used is: https://pastebin.com/U63BW3Ze
Can you please provide us with the modifications that can be made to the above code and the exact steps that can be taken to replicate the issue so that it can be tested 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,
It seems that newest version is working properly. Sorry for the inconvenience.
Best, Qode
8.6.1 also Tabs > Section settings don’t save anymore!
Hello, We tried testing it at our end, but the tab and section settings seem to be working fine. 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.
2 more issues in the latest update:
1. When using WPBakery but using Gutenberg like this: https://a.cl.ly/eDuD6Rwe – it’s still “listening” to shortcuts. Shortcuts should only apply in the context of WPBakery – aka the current focus is the WPBakery editor.
2. Since you’ve assigned shortcuts to Shift + T and Shift + C, using Shift to type a capital T or C no longer works as expected. To type uppercase T or C, I have to rely on Caps Lock instead of Shift, which creates an accessibility and usability problem. I haven’t tested all the shortcuts yet, but these two are definite issues I’ve identified.
Thanks!
Hello, 1) We tried using the shortcuts according to the setup shared by you. However, we were unable to replicate the issue. Can you please share the video of it from your end, as that will help us to better understand and replicate it.
2) The shortcut functionality is currently in its initial phase, and we are actively gathering user input to improve it. We will monitor the issue reported by you so that necessary steps can be taken 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’m not sure how to share a video of using keyboard shortcuts. All you need to do is open a page that has both WPBakery and Gutenberg enabled like the screenshot I shared then try using Shift + T to write a capital T for the post title and it won’t work and you can’t add a capital T in the title.
This is because in your code you use:
$( document ).on( 'keydown.vcshortcuts', handleInputShortcuts );
Instead of listening to keydown events while in the context of the WPBakery editor. This means whenever backend.min.js is loaded it’s going to listen to keydown events, even if you aren’t actively using the editor.
Hello, Thanks for sharing further details. We have confirmed this as a bug, and it has been added to our bug-fix list.
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
