22695 comments found.
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 );
Hello,
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.
Thanks.
Hello, Yes, we will be making changes to page settings and custom CSS, based on the feedback that is received.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
We have extended / renewed our support for another 6 months, but your support portal is not reflecting the same. Can we please get some assistance? Is there any email we can reach out to you at?
Hello, As the support tenure is renewed via codecanyon in this case you should import it 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.
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 Rohan, we already checked on support portal we see our licenses but the date of support is still showing old date and its not updated new valid support date as we extended our support and we are not able to update WP bakery from backend side as its said “1.1 Auto-update fails with message: “Automatic updates for the plugin are available to the clients with a valid support period – you can renew it here.” Can you please help
Hello, When I check in our system, it shows that your account has four licenses and all four have active support tenure that expires in Aug 2025. If there is still any issue, then please drop a message via the contact form of the WPBakery account, so that we can guide you further with 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.
hello i am using wp bakery for a long time and i have a question i have your premium version but i would ask how can i remove a post icon from a gallery cpt element
Hello, The gallery cpt is not a standard element of WPBakery Page Builder. It is most likely a custom element added either by the theme or a third-party plugin used at your end. You can check the standard elements of the WPBakery Page Builder plugin by creating an online demo here: https://wpbakery.com/try
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 for the reply… and i have a last problem at the text hero slider after the text how can i do that the slider go to the start again it stuck at the end and i cnat see the first heading anymore thanks for the helping
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.
Hello, I need to downgrade WPBakery to 7.9. Where can I download an older version? Many thanks Best
Please create a support ticket at support.wpbakery.com so we can send version 7.9.
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,
Another one. The vc_map takes “icon” as parameter and according to your documentation:
https://kb.wpbakery.com/docs/inner-api/vc_map/ It says:icon String URL or CSS class with icon image. More info here
So we have always been using the URL but in the recent updates the icons are not showing. Whats even worse, the URL is outputted in the CSS class:
https://d.pr/i/RKMbecWould you please fix this?
Arlind
Please create a support ticket at support.wpbakery.com with your site credentials and steps to replicate the issue 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,
After the last update, I get this fatal error:
[07-Feb-2025 10:03:04 UTC] PHP 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
Stack trace:
#0 ~/wp-includes/class-wp-hook.php(324): Vc_Autoload_Manager->{closure}()
#1 ~/wp-includes/plugin.php(205): WP_Hook->apply_filters()
#2 ~/wp-content/themes/kalium/includes/functions/core/hook-functions.php(1349): apply_filters()
#3 ~/wp-includes/class-wp-hook.php(324): kalium_single_page_heading()
#4 ~/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#5 ~/wp-includes/plugin.php(517): WP_Hook->do_action()
#6 ~/wp-includes/general-template.php(3064): do_action()
#7 ~/wp-content/plugins/js_composer/include/templates/pages/layouts/blank.php(19): wp_head()
#8 ~/wp-includes/template-loader.php(106): include('/homepages/19/d...')
#9 ~/wp-blog-header.php(19): require_once('/homepages/19/d...')
#10 /homepages/19/d258280905/htdocs/index.php(17): require('/homepages/19/d...')
#11 {main}
thrown in ~/wp-content/plugins/js_composer/include/autoload/hook-wpb-hide-title.php on line 13
The content in the editor is this: https://d.pr/n/CwWjfk
Any fix for this?
Arlind
It looks like third-party code is causing the issue at your end. Please try deactivating all the plugins except WPBakery Page Builder and especially switching to a default theme like Twenty-Nineteen to check the same. You can then activate them individually to find out which one is causing the issue. Let us know if the issue still exists.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Wordpress showing an update issue about a license.
The support tenure for the license is over on Jun 4, 2021 . The plugin purchase includes lifetime validity with free manual updates for life (as per the second method here: https://kb.wpbakery.com/docs/getting-started/update/). Starting from version 8.1, an active support tenure is required to enable automatic updates, along with access to the support portal, AI-powered tools, and additional features. You can renew support at https://support.wpbakery.com/licenses. If you do not need these services, renewing the support license is optional and entirely at your discretion.
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 paid for lifetime updates which I and others should be getting I never have any issues out of the plugin.
Hello, The plugin updates are valid for a lifetime. You can update the plugin manually as per the second method here: https://kb.wpbakery.com/docs/getting-started/update/
An active support tenure provides features that include auto-updates, without having to manually update the plugin.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
PHP 8.2 Compatibility Issue in vc_welcome_block.tpl.php
I’ve encountered a PHP 8.2 compatibility issue (even in the very latest version released today) in the vc_welcome_block.tpl.php file of the WPBakery Page Builder plugin. The error occurs because the count() function is called on a null variable, which throws a TypeError in PHP 8.2. Below are the error details:
Error Message: Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, null given in /wp-content/plugins/js_composer/include/templates/editors/partials/vc_welcome_block.tpl.php:13
Upon reviewing the code, the issue is caused by this line (Line 13):
$templates_total_count = count( $total_templates );
In PHP 8.2, this throws an error if $total_templates is null. To ensure compatibility, it would be best to check if $total_templates is countable before calling count(). For example:
$templates_total_count = is_countable( $total_templates ) ? count( $total_templates ) : 0;
Could you please update the plugin to address this? This would help maintain compatibility with newer PHP versions.
Thank you for your support!
Hello, Can you please check the latest version 8.2 at your end to see if you still face such an issue with it?
If so, please use support.wpbakery.com and share your temporary website credentials so our support team can investigate it further on your setup.
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 issue is still present in the latest version of WPB as mentioned in my original message. I can’t submit a support ticket as my support has expired and I dont plan on renewing. I have explained the issue, given you the file and line of code to check and provided you with a fix for this. Its not hard to spot that your current code is not compatible with anything newer than PHP 7.4. I dont know how providing access to my site (which I have already patched with the fix) would provide beneficial. Just check the code as mentioned. I am just trying to help one dev to another.
Hello, We have tested the latest version with PHP 8.2 and 8.3 on our setup but were unable to replicate the issue. This is why we want the access to setup where the issue was present to investigate it further. We will add this issue to our tracking list and continue monitoring for any additional reports to take the necessary action as needed.
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.. You have a problem with an element, “Icon Box” on mobile..
https://themeforest.net/item/impreza-retina-responsive-wordpress-theme/6434280/comments?page=1&filter=all#comment_31300571Hello, The Icon Box is not a standard element of the WPBakery Page Builder plugin. It is most likely a custom element added by the theme or a third-party add-on that is being used on your setup.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Please send my love to the WPBakery developer team for accepting my pull requests 
Hello, It’s great to hear, and we’ve passed your message along to the development team.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
IWD, viablethought and mster5 get right to the point. Now that some time has passed and the feedback on the missing auto-update function in numerous forums and also here in the comments was not good, I wanted to ask whether you have discussed this point internally and what the current status is? Sorry for my English. I translated the text here with Google Translator
Hello, After taking feedback from customers, this matter was discussed internally.
We acknowledge that manual updates may involve a few additional steps compared to automatic updates, but they remain a reliable way to honor our commitment to providing lifetime updates.
To accommodate the needs of our long-standing customers, especially those managing multiple licenses, we are offering bulk renewal discounts on support tenure. This ensures that users who prefer the convenience of auto-updates, along with other added benefits like access to the support portal and AI-powered tools, can do so at a more manageable cost.
If you’re managing multiple licenses and would like assistance with bulk support renewals, please don’t hesitate to reach out to us. We’d be more than happy to guide you through the process and offer the necessary support.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
DITTO
I urge you to take a close look at this feed and the overwhelming response from your long-time customers. The community has made its position very clear: requiring an active support license for automatic updates—a functionality that should be core to every WordPress plugin—is both unreasonable and unethical.
This policy forces users to resort to manual updates via cPanel or FTP, adding unnecessary complexity to a process that should be seamless. This change alienates your most loyal customers, many of whom have supported WPBakery for years, recommending it to clients and peers.
If you fail to address this, it will send a clear message that you neither value nor respect your customers’ feedback. Your long-term success depends on retaining the trust of your user base. Please reconsider this decision and restore auto-updates for existing licenses. Ignoring this feedback will undoubtedly lead to a significant loss of customers, myself included.
Hello, Thanks for being a long-time supporter of WPBakery. We truly value the feedback from our loyal customers, and your input is important to us.
Our commitment to providing lifetime updates for WPBakery Page Builder remains intact. Updates continue to be fully accessible through manual downloads from your WPBakery account. While we understand that the process of manual updates may require a few extra steps compared to automatic updates, it ensures that our promise of lifetime updates is upheld.
The option of automatic updates is tied to an active support tenure, which also includes additional benefits such as access to the support portal, AI-powered tools, and other enhanced features. This structure was introduced as part of the evolving WordPress ecosystem, allowing us to provide ongoing improvements and maintain compatibility with the latest developments.
We understand that for users managing multiple websites, convenience is a priority. To support our long-time customers like you, we’re happy to assist with discounted bulk renewals for support tenure, which can ease the process of accessing auto-updates and other features. Please feel free to reach out via the profile contact form, and we’d be glad to explore how we can best accommodate 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.
Hi,
I use WPBakery and it is fantastic. I also use the “List Post” function and connect it with ACF custom fields. Thus I have a problem with repeater fields from ACF. I stored in the repeater fields email address and want to to use that as query criteria. The problem is that when I define the custom_field with the ACF repeater field and the column where to find the email the request is not working
Can I somehow hook in to adapt the query?
Best, Christian
Hello, Please use support.wpbakery.com and share your temporary website credentials so our support team can investigate 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.
We are facing the same issues with the classic editor being loaded even if the WPBakery editor should be loaded as enervo already mentioned.
I also got this message twice in the javascript console: unreachable code after return statement
Looking into it, it is pointing to these locations: partObj = _.isUndefined( _localCapabilities[ part ] ) ? {} : _localCapabilities[ part ];
and
shortcodeValidateOldMethod: function ( shortcode ) { return true; if ( ‘vc_row’ === shortcode ) { return true; }
Both are within this tag: <script id=”vc_role_access_manager_script”>
So it seems, that there are some issues within this script which seems to be related to the role manager setting.
Hope that helps.
Hello, We have identified similar issues on some setups. We will be soon introducing functionality to set the WPBakery Page Builder as a default editor which will make sure that the classic editor will not load unless it is manually enabled.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Good day,
The latest update makes things tougher.
Before I could Classic Mode and Backend Editor seamlessly, but after the update the page reloads whenever the buttons are clicked.
This is also the same issue with adding CSS codes in the page setting. Before I could add the code and close the popup but now, I have to update the page first before the CSS codes can save.
Please, work on these issues.
Kind regards
We have added the issue with the page updating when CSS is saved in our To-do list. Our team is aware of this. It will be fixed in a future release. Regarding the issue with Classic Mode and Backend editor refreshing whenever buttons are clicked can you send a screen recording of the problem so we can understand what is happening?
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
Good day,
Please, click on the video screenshot link below
https://drive.google.com/file/d/16bVpNUU00nA2dsqVlzdG56K7G4xChrqM/view?usp=sharingKind regards
We will fix this issue in a future release. We hope for a fix in the next version 8.2 .
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from the WPBakery team.
This item was featured on CodeCanyon
Power Elite Author
Contact the Envato Market Help Team
