22690 comments found.
I install it, and am not able to activate with the license key. it opens a new page and I have to login. with what?
Hello, If the license was purchased via codecanyon, then in this case you should import the license into your WPBakery account. To do so, you can login into: support.wpbakery.com/login If you are not sure about the login details, then use the reset password option and use the email id associated with your codecanyon account. Once logged in, navigate to licenses page and click on “import it” option at the bottom of the page. It will then prompt you to login into codecanyon to complete the import. You can then activate the plugin license as per: https://wpbakery.com/video-academy/activate-wpbakery-page-builder-wordpress-license/
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! Now not only when you use the Frontend Editor and save the CSS does a page refresh occur (which negates the purpose of using a Frontend Editor) but also when you use the Backend Editor, which didn’t happen before, it seems that the new developers have taken the worst path, ex: https://undsgn.d.pr/v/69RDAg
Hello, We are aware of the reload issue in the Backend Editor, and it is on our list of improvements so that changes can be saved without requiring a reload.
Right now, for the Frontend Editor, the reload is necessary as it ensures that live changes are properly displayed, especially for the options related to post such as featured image, slug, etc.
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 Rohan_WPBakery-Team! The major issue with the Frontend Editor is that the developers implemented the new features (featured image, slug, etc.) in the same window as the CSS. If these had been placed in their own separate window, there wouldn’t have been any problems, and the Frontend Editor would have continued to function correctly as it did before, without page refresh when saving CSS. I hope we can consider addressing this, as it was an update that made things worse rather than better.
Where am I supposed to get support for this plugin when it came with a theme? I note WPBakery suggest contacting the theme author, but that seems like a bit of a copout – the theme author doesn’t have the depth of knowledge to help I would assume?
Obviously WPBakery gets a license fee from these installations, so if they cannot offer support, then perhaps they shouldn’t license their software to be used in themes.
We are trying to work out why, in the editor, when switching between editing modes, that you have to save it each time – why can’t you simply switch between editors without losing the changes you made?
Hello, The plugin that comes bundled with a theme does not have its own license. The responsibility for providing support and updates lies with the theme developer, as they distribute and manage the bundled plugin.
When the plugin is purchased directly from us, it includes a full license that provides access to customer support, auto-updates, and other features (https://kb.wpbakery.com/docs/faq/what-are-the-benefits-of-direct-license-for-wpbakery-page-builder/), ensuring you receive direct assistance from our support team.
Regarding the issue you mentioned, it sounds like your setup might be running an older version of the plugin. In previous versions, switching between editors required reloading the page. Updating to the latest version should resolve this behavior.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Ok thank you. For your reference we seem to be using “WPBakery Page Builder (Modified Version) | Version 8.1 | By Michael M – WPBakery.com”.
As others have noted, when we purchased this plugin, you explicitly promised lifetime automatic updates, free of charge—both on the CodeCanyon plugin page and on your own website. That promise was clear and unqualified. Here’s the exact language from the plugin page, which is still accessible via the Wayback Machine for verification:
“Lifetime Update – Free of Charge We offer automatic updates, free of charge. Stay up to date with WPBakery Page Builder and receive our latest releases and enhancements.”
Now, you’ve quietly removed the word automatic and introduced a requirement for an “active support tenure” to access automatic updates. This is a clear policy change that impacts customers who purchased the plugin under different terms.
Developers are obviously free to change what’s promised however they wish for new customers moving forward, but those of us who bought WPBakery when lifetime automatic updates were explicitly included should not have our access restricted or forced into a support renewal to regain functionality that was part of the original purchase agreement.
The plugin is great, so it’s super disappointing to see this new development.
We understand your disappointment and truly appreciate your long-standing support of WPBakery.
To clarify, the lifetime validity of the plugin you purchased remains intact. You will continue to receive manual updates for life . The policy change only applies to automatic updates from the WordPress dashboard, which now require an active support tenure. This change was introduced starting with version 8.1 and includes access to our support portal, AI-powered tools, and additional features. We recognize that this may differ from the original offering, and we value your feedback. We will share your concerns with our team for further review.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Anyone considering this plugin be aware that WPB is now charging for common updates. A service that has always been free, no longer is – even for those who purchased the plugin with the expectation (based on the info provided on their site) that those updates would always be free. Virtually on other developer charges for automatic updates. Makes me wonder what else they’re being cheap about.
Hello, The plugin updates are free for a lifetime and can always be applied manually as per the second method outlined here: https://kb.wpbakery.com/docs/getting-started/update/ The automatic update feature is tied to an active support tenure, which is included for the first year after purchase. Once the support tenure expires, it can be renewed to continue benefiting from features such as auto-updates, AI-powered tools, access to support, etc. However, renewing support is entirely optional and depends on the features you wish to utilize.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
RTL is not working again. This is an ongoing thing. U just released a newversion and it is broken. How do we fix that? https://prnt.sc/c8FLpzpzOuQe
Hello, We just tested the reverse column feature for RTL languages and it seems to be working fine on our setup. If there is any issue with it at your end, then please use support.wpbakery.com and share your temporary website credentials so our support team can investigate it 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.
@WPBakery-Team – We’re still having the display issue with the updated version of 8.3.1. Do you have an ETA on 8.3.2 or a solution to display the builder in the back-end?
Thanks
Hello, If you are facing any issues with the page builder display, then feel free to drop a ticket via customer center: https://support.wpbakery.com/ and share your temporary login details in it, so that the 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.
siimple question and it should be a simnple anmswer. I just install this plugin on my website, but it was using another editor, so yours took over, but my menu dissappear. keep in mind, i only want to use this plugin to uopdate one page, and retain the other editor. how do i get my menu backlup on this page? the rest of the pages are showign the menu.
Hello, Under layout option in page settings, please make sure that you are using: Default WordPress Theme Layout and not the Blank page layout.
By default the menu display is something that is not controlled by the WPBakery Page Builder as it only works within the content area of the page.
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 can’t seem to find that setting. Is this under WPBakery? I also checked my page and I don’t see the page settings. I only see the page attribute. in my theme settings, I don’t see any page settings.
Nevermind. it works. You have to be specific. I finally found it, and it worked. Thankyou.
Purchased this plugin and have used it for years. Love it! But, recently, although we have the license registered, it still says our license has expired (which it has since), but we aren’t getting any updates. How do we continue to receive updates? I thought the updates were free for the life of the plugin and any support, AI, etc, was annual. Am I wrong?! Please help get us the latest updates.
Hello, The plugin license remains valid for a lifetime, and you are entitled to free lifetime updates, which can be applied manually as per the second method here: https://kb.wpbakery.com/docs/getting-started/update/ However, automatic updates are linked to an active support tenure. Your purchase originally included one year of support, and once it expires, auto-updates are disabled. You can still update the plugin manually at any time. If you wish to re-enable auto-updates, you can renew your support tenure from the Licenses section of your account.
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!
Version 8.3 of WP Bakery will throw a fatal error when trying to preview a post/page/CPT that doesn’t support revisions.
The wpb_update_id_with_preview_id function that was introduced is why. It doesn’t do a proper check on the value returned from wp_get_latest_revision_id_and_total_count.
Could you provide a fix?
Hello, This issue has been confirmed as a bug when revisions are disabled. It will be fixed in our upcoming release which will be out soon.
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, This issue has been fixed in the latest release which is 8.3.1.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Looks like 8.3 has a few fatal bugs. Had to downgrade back to 8.2 until the bugs are fixed.
Can’t seem to be able to report the bugs via their support site since I don’t have an active support license. Not sure how else to help notify the devs other than to comment on here.
So yeah, be careful for any potential buyers. If you have the option, don’t use 8.3 on a production website.
We have not received any reports of bugs with 8.3. Please tell us what issue you are facing or the steps to replicate the problem so we can help you.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Sure thing. Here’s the error I’m receiving when trying to preview a post.
Uncaught Error: Cannot use object of type WP_Error as array in /home/edited/domains/edited/public_html/wp-content/plugins/js_composer/include/helpers/helpers.php on line 1687
Call stack:
wpb_update_id_with_preview_id() wp-content/plugins/js_composer/modules/post-custom-layout/module.php:203 Vc_Post_Custom_Layout_Module::get_layout_from_meta() wp-content/plugins/js_composer/modules/post-custom-layout/module.php:106 Vc_Post_Custom_Layout_Module::get_custom_layout_name() wp-content/plugins/js_composer/modules/post-custom-layout/module.php:80 Vc_Post_Custom_Layout_Module::switch_post_custom_layout() wp-includes/class-wp-hook.php:324 WP_Hook::apply_filters() wp-includes/plugin.php:205 apply_filters() wp-includes/template-loader.php:104 require_once(’/home/edited/domai…/template-loader.php’) wp-blog-header.php:19 require(’/home/edited/domai…l/wp-blog-header.php’) index.php:17
Downgrading back to 8.2 fixes the above error.
Hello, This issue ha been confirmed as a bug on setups where revisions are disabled. It will be fixed in our next update that will be out soon.
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, This issue has been fixed in the latest release which is 8.3.1.
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 the newest version 8.3 ready for PHP 8.4? Will there be an official announcement in the changelog when PHP 8.4 support is fully implemented? What’s the timeline for full PHP 8.4 support?
Hello, The latest version of WPBakery Page Builder is likely to be largely compatible with PHP 8.4. However, since its compatibility has not been fully tested, there may be some minor issues. We will officially include PHP 8.4 compatibility in our release log: https://kb.wpbakery.com/docs/preface/release-notes/ once it has been confirmed and rolled out 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.
Thanks for the fast reply. Wouldn’t it be better to first do full PHP 8.4 support before adding AI features etc. (which I personally will never use and I hate everything with AI)?
Hi, I would like to know if it’s possible to display partial slides in carousel sliders, similar to a Peek View Carousel or Partial Visibility Carousel. This design improves usability, especially on touch devices, by showing a portion of the next item on the edge. It visually suggests that there is more content available for horizontal scrolling, enhancing user experience. This approach is widely used in e-commerce to encourage interaction. Does WPBakery currently support this feature? If not, would it be possible to add it in a future update? Thank you!
Hello, The standard elements of WPBakery Page Builder do not support such a feature. However, there are several image slider addons available on CodeCanyon that may offer the feature you are looking for. We recommend reviewing the addon descriptions carefully and confirming the functionality with the respective addon developer before making a purchase to ensure it meets your requirements.
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 have 20 licensed copies of WPBakery, and none of them are updating, so I’ve had to manually update each of them one by one. What’s going on with it? I am out of my support for them, so how do I fix this?
And you are updating the plugin almost EVERY week ugh
Hello, Plugin updates are released to introduce new features and address bug fixes. While we do not release updates on a weekly basis, any urgent bug fixes are prioritized and rolled out as soon as possible.
The plugin purchase includes lifetime validity with free lifetime updates, which can be applied manually as per the second method here: https://kb.wpbakery.com/docs/getting-started/update/
Additionally, each license comes with a one-year support tenure. An active support tenure provides extra benefits, such as auto-updates, access to the support portal, AI-powered tools, and more. However, renewing support is completely optional and depends on your preferences.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Since there are currently problems not only with the pricing model of the plugin but also with numerous functions, I wanted to ask how ready WPBakery is for June 2025. The new EU accessibility law will come in June. Will WPBakery make adjustments here or will the topic be completely neglected and WPBakery discontinued? Because accessibility is still very far away at the moment…
Hello, We are committed to ensuring that WPBakery Page Builder adheres to the latest web guidelines and regulations so that our users do not face any issues. The same applies to the accessibility laws. Our team will review the guidelines and assess any necessary changes to maintain compliance and enhance accessibility.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
OK, thank you very much for the answer. The law comes into force in the EU in June. Can we expect that WPBakery will be accessible by then?
Hello, Our team will be reviewing the requirements of the accessibility law to ensure compliance. If any changes are needed, we will work on implementing them before the law comes into effect.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
s
Hi! We would like to add to other comments we’ve read on this page. Since the latest updates, the Frontend Editor’s saving method for CSS and JS has become unusable. I share the frustration of other users. CSS updates in real-time are often out of sync with what is displayed, leading to inconsistencies between the written code and what appears in the editor. While writing JS code, the console fills up with errors due to the typing speed, which can be stressful for less experienced users who might think they made a mistake. Often, reloading the page is the only way to understand what has actually been saved, making real-time saving pointless and defeating the very purpose of the Frontend Editor. I hope you can soon publish a substantial fix for this part of the tool, which is now completely broken. Thx!
Hello, We have tested custom CSS/JS functionality on our setup but were unable to replicate the issues described. However, we’d be happy to investigate this further. If you could send us a message via our profile contact form with temporary login access and the exact steps to reproduce the issue, our team will take a closer look. We are always committed to fixing bugs and improving the plugin based on user feedback.
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! If the user writes CSS, it gets applied after a moment, as seen in the video. However, if the user doesn’t click “Update” and decides to leave the page, there is no warning to save the changes, and they get lost: https://undsgn.d.pr/v/Nfo5u7
Plus as noted by other users… “Are you going to bring back the ‘Save’ option for custom CSS/JS? I don’t want the page to be updated and reloaded every time I change my custom CSS/JS code. This is unbearable to work with.”
The new button that reloads the page maks real-time saving pointless and defeats the very purpose of the Frontend Editor.
Hello, Thank you for sharing the video. We tested this with several previous versions but did not notice any changes in the speed of applying CSS code within the frontend editor for the latest release. However, we will add this to our list for further review to explore potential improvements in implementation speed in future updates.
We are working on enhancements to page settings, which will include updates to custom CSS/JS based on the feedback received regarding recent changes.
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! Please note that we never mentioned a speed issues. The problem here is that you’ve implemented the saving of custom CSS using Ajax, and as shown in the video, there are moments when it goes out of sync. Furthermore, as reported by other users, the “update” button refreshes the page, which defeats the purpose of having a frontend builder.
Hello, By speed, we were referring to the time it takes for the applied changes to reflect once the related code has been added to the custom CSS section.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Updated WP Bakery to the latest 8.2 version but the shape divider feature seems to have disappear. Please can you advise?
Hello, The shape divider is not a standard feature of WPBakery Page Builder. It is most likely a custom feature added by the theme or a third-party add-on.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
When I manually download the files to upload and update the plugin to 8.2 via ftp, it continually shows the previous version 8.0.1 is installed. Why would the available download on themeforest not be the latest version? The plugin page on themeforest shows that the latest version is 8.2. Thank you.
I just realized the problem: after unzipping the “all files and documentation” option and drilling down to the plugin folder, you end up with a folder inside yet another folder of the same name. \js_composer\js_composer. There are no other files inside that “js_composer” main folder to make needing the second folder necessary. I was inadvertently uploading the main js_composer folder and not realizing there’s another folder in there that then lists the plugin files. Ugh.
Hello, Glad to hear that the issue is resolved. You can also download the latest version of the plugin from the downloads section of your WPBakery account: https://support.wpbakery.com/downloads
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,
WP Bakery 8.2 outputs the following error:
Fatal error: Uncaught ArgumentCountError: Too few arguments to function Vc_Autoload_Manager::{closure}(), 1 passed in /wp-includes/class-wp-hook.php on line 324 and exactly 2 expected in /wp-content/plugins/js_composer/include/autoload/hook-wpb-hide-title.php:13
There were no such issues with 8.1 or older.
Any solutions?
Thank you
Hello, We are unable to replicate this error on our setup. To assist you further, please submit a ticket via the Customer Center: https://support.wpbakery.com/ and include temporary login details. This will allow our support team to investigate the issue directly and provide you with a suitable solution.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Editing the hook-wpb-hide-title.php file and changing the code to the following, resolved the issue:
add_filter( 'the_title', function ( $title, $post_id = null ) {
// If the post ID is not provided, get it from the global post object
if ( is_null( $post_id ) && is_singular() ) {
global $post;
$post_id = $post->ID;
}
// Check if the title should be hidden for this post ID
if ( wpb_is_hide_title( $post_id ) ) {
return ''; // Hide the title
}
return $title; // Return the original title
}, 10, 2 );
This item was featured on CodeCanyon
Power Elite Author
Contact the Envato Market Help Team
