22686 comments found.
Hi,
There is a compatible issue with Slider Revolution v7.0.8. When editing a page, it shows some warnings:
Deprecated: Function getArrSliders is deprecated since version 7.0.0! Use get_sliders instead
Deprecated: Function getTitle is deprecated since version 7.0.0! Use get_title instead
Deprecated: Function getAlias is deprecated since version 7.0.0! Use get_alias instead
You should check the file \js_composer\include\classes\vendors\plugins\class-vc-vendor-revslider.php. Also in that file, you should not call the RevSlider class. It may be deprecated in future.
Best regards,
We have identified this as a bug. It 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.
Hi, I am experiencing a recurring PHP Warning in my error logs related to WPBakery Page Builder (js_composer) specifically on my WooCommerce Cart and Checkout pages.
The error is: PHP Warning: Attempt to read property “post_title” on null in …/wp-content/plugins/js_composer/include/helpers/helpers.php on line 615
Context:
The Cart and Checkout pages are correctly assigned in WooCommerce settings.
These pages are built using the standard WordPress Block Editor (Gutenberg), but WPBakery is active on the site.
It seems helpers.php at line 615 is trying to access the $post object before it is fully initialized or while it’s null on these specific dynamic pages.
My support license is currently expired, but I am willing to renew it immediately if your team can confirm that this issue is solvable or if you can provide a specific fix/patch for this compatibility conflict. I want to ensure my site remains stable before proceeding with the renewal.
Hello, We are unable to replicate this issue on our setup. The support team will be glad to investigate it further. To do so, please drop a ticket via the customer center: https://support.wpbakery.com/ and share your temporary admin login details in 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.
i can’t update the plugin on the site, i have a message telling i must activate WPBakery Page Builder license while the license is activated and added in your site here https://support.wpbakery.com/licenses
Hello, Such an issue can occur if the license was not correctly activated. You can deactivate the plugin license under the licenses section of your account and then reactivate it as per: https://kb.wpbakery.com/docs/getting-started/activation/
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 deactivate the license because i have just a button activate WPBakery Page Builder
Hello, Please feel free to drop a ticket via the customer center: https://support.wpbakery.com/ so that the support team can check it to guide you 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.
Using code like this correctly works:
add_filter( 'vc_css_editor_border_radius_options_data', function( $data ) {
$data['var(--rounded-xl)'] = 'Extra Large';
return $data;
} );
Can you let me know if this is ok to use or should the extra border radius options be restricted to pixels?
I just want to ensure if I use something like this it won’t break in the future or cause any issues currently (seems to be fine).
Thank you!!
Hi, It is absolutely fine to use. There are no plans to change or remove this filtered value in future updates.
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!
Most specifically I’m not referring to the filter itself, but to using var() as a value for the border radius or should the values always be pixels?
Thank you!!
Hello, Using var() as a value for border radius is fine because the value isn’t parsed. There is no transformation to the value.
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 contains sprintf strings with incorrect placeholders. Please fix.
Here are the four window.sprintf() calls and their format strings: Call site | Format string | Argument ------- checks.js:356 | textLengthSuccess | "The text contains %s words. Good job!" textLength (number) ------- checks.js:379 | passiveVoiceError | "%s of the sentences contain passive voice, which is more than the recommended maximum of 10%" percentage + '%' (e.g. "25%") ------- checks.js:414 | paragraphLengthError | "%s of the paragraphs contains more than the recommended maximum of 150 words." longParagraphsCount ------- checks.js:440 | sentenceLengthError | "%s%% of the sentences contain more than 20 words, which is more than the recommended maximum of 25%." longSentencePercentage.toFixed() The passiveVoiceError string is the main culprit. It ends with ...maximum of 10% — that trailing % with no format specifier after it is what triggers [sprintf] unexpected placeholder. The sprintf parser sees % and tries to parse a placeholder but finds nothing valid after it. The sentenceLengthError has the same problem: ...maximum of 25%. — the % before the period is also an unescaped literal percent. In PHP, %% produces a literal %. WPBakery correctly used %s%% at the start but forgot to escape the trailing % characters. A classic bug.
Hello, We have shared your findings with our development team, and the behavior has been noted. It will be evaluated further for potential improvements in the future.
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, just a deprecation notice, FYI (running on 8.7.2 and latest WP 6.9, on PHP 8.4):
[25-Jan-2026 09:48:30 UTC] PHP Deprecated (trace): ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /wp-includes/formatting.php:4496 #0 /wp-includes/formatting.php:4496 ltrim() #1 /wp-content/plugins/js_composer/include/templates/editors/popups/partials/element_teasers.tpl.php:32 esc_url() #2 /wp-content/plugins/js_composer/include/helpers/helpers.php:82 require() #3 /wp-content/plugins/js_composer/include/templates/editors/popups/vc_ui-panel-add-element.tpl.php:60 vc_include_template() #4 /wp-content/plugins/js_composer/include/helpers/helpers.php:82 require() #5 /wp-content/plugins/js_composer/include/classes/editors/popups/class-vc-add-element-box.php:251 vc_include_template() #6 /wp-content/plugins/js_composer/include/templates/editors/partials/footer.tpl.php:16 Vc_Add_Element_Box->render() #7 /wp-content/plugins/js_composer/include/helpers/helpers.php:82 require() #8 /wp-content/plugins/js_composer/include/templates/editors/partials/backend_editor_footer.tpl.php:14 vc_include_template() #9 /wp-content/plugins/js_composer/include/helpers/helpers.php:82 require() #10 /wp-content/plugins/js_composer/include/classes/editors/class-vc-backend-editor.php:199 vc_include_template() #11 /wp-includes/class-wp-hook.php:341 Vc_Backend_Editor->renderEditorFooter() #12 /wp-includes/class-wp-hook.php:365 WP_Hook->apply_filters() #13 /wp-includes/plugin.php:522 WP_Hook->do_action() #14 /wp-admin/admin-footer.php:78 do_action() #15 /wp-admin/post.php:369 require_once()
And this warning also:
[25-Jan-2026 09:48:30 UTC] PHP Warning: Trying to access array offset on true in /wp-content/plugins/js_composer/include/templates/editors/popups/partials/element_teasers.tpl.php on line 32
Regards!
It appears that the issue may be caused by third-party code on your site. To troubleshoot, please try the following steps:
Deactivate all plugins except WPBakery Page Builder.
Switch to a default WordPress theme (such as Twenty Twenty-Four).
Check if the issue still occurs.
If the issue is resolved, reactivate your plugins and theme one by one to identify the source of the conflict.
Kindly let us know if the problem persists after these steps.
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 is correct, thank you!
Hi. Wordfence recently reported this regarding WPBakery. Obviously nothing serious, but still thought you folks would like to know that Wordfence considers this an “issue”. [Dec 07 04:42:20:1765078940.562720:3:error] Unable to determine version for plugin js_composer
Hello, Please ensure that you are running the latest version of WPBakery Page Builder, which is 8.7.2. In most cases this type of notice occurs when Wordfence is temporarily unable to read the plugin version string.
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 Rohan. I trust you guys as I’ve been using several paid versions of the WPBakery plugin for over a decade, but just wanted to let you know in case it meant anything. 
All the best!
Frank
Hi, with WPBakery 8.7.2 and PHP 8.3 I got following warnings in my log:
- Warning: Undefined array key “plugins” in /wp-content/plugins/js_composer/include/autoload/vc-pages/welcome-screen.php on line 130
- Warning: foreach() argument must be of type array|object, null given in /wp-content/plugins/js_composer/include/autoload/vc-pages/welcome-screen.php on line 131
Hello, This behavior is quite unexpected since WPBakery 8.7.2 has been tested with PHP 8.3 and should not generate those warnings under normal conditions. To look into this more accurately, it would be helpful if you could open a ticket through the Customer Center and share temporary admin access 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.
The elements Lightbox, Tabs menu and akkordion are not working since updating to wordpress 6.9. Seems like the stylesheets are not loading any longer. Please fix this asap!
Hello, We tested the elements that use lightbox such as image gallery, tabs, and accordion elements on our setup running WordPress 6.9, and they seem to be working fine without an issue.
If you are still experiencing problems on your site, please feel free to submit a ticket through the Customer Center: https://support.wpbakery.com/ and include temporary admin access. This will allow our support team to check the setup directly.
Knowledge Base ·
Official Support ·
Facebook ·
Twitter
Don’t forget to join our newsletter. Be first to get news and inside secrets from WPBakery team.
A bit pitty that true the support you can’t add a bug report when the support has expired. Since version 8.7, I can’t edit anymore: https://ibb.co/23NzFwDr
The issue appears to be caused by a third-party plugin conflict rather than a bug in WPBakery itself. To troubleshoot, please try the following steps:
1. Deactivate all plugins except WPBakery Page Builder.
2. Switch to a default WordPress theme (such as Twenty Twenty-Four).
3. Check whether the issue still occurs.
If the problem is resolved, reactivate your plugins and theme one by one to identify which one is causing the conflict.
Please let us know if the issue persists after trying these steps.
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 very easy to say. Everthing worked until I updated wpbakary to version 8.7.
Hello, aside from the fact that the current licensing model is truly outrageous regarding the “Automatic Updates” function, I also discovered today that it’s no longer possible to transfer an old license from one account to a client account. This means a new license has to be purchased for each website using my client’s account. I know you won’t change anything about this, but I wanted to share this with others because I find it simply unacceptable how you’re handling this.
Hello, We understand your concerns. Regarding license transfers, this feature is currently not supported because licenses now operate under a subscription-based system. Each subscription is tied to the WPBakery account used at the time of purchase.
However, it is possible to update or change the email address associated with an existing 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.
Are there any Black Friday sales this week? thanks
Our Black Friday sales are available at https://wpbakery.com/black-friday/.
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 WPBakery have an agency-level Support Plus option? I’ve purchased a WPBakery license via Envato nearly 40 times between a couple of different Envato accounts, and not having access to one-click updates in the WP Dashboard is cumbersome, while purchasing Support Plus for each license is financially burdensome. Curious if you have solutions for those of us in this situation.
Hello, Thank you for reaching out and for being such a long-time user of WPBakery. We really appreciate your continued trust in the product.
We do offer a bulk Support Plus option, but it requires that all licenses are under single WPBakery account.
This allows the system to apply Support Plus in bulk and handle renewals together.
If the licenses were purchased across multiple accounts, then unfortunately, they cannot be renewed as a single group. In that case, their support tenure needs to be renewed separately from the respective accounts.
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 uses only one or many websites
Hello, A regular license can be used on one website.
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 want more website licenses, but here only the regular license provides
Hello, If you are looking to purchase more than one license, then we have license packs available on our website, which are suitable for 5 and 10 sites. Additionally, we also have agency plans for 20+ licenses.
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 updated editor the following:
'mouseenter .vc_shortcode-link': 'cacheElement',
Can potentially cause many ajax requests if the user is slowly browsing the Add Element window.
I can see the functionality is also disabled for the grid builder elements:
// our grid builder elements produce fatal errors when cached.
if ( this.isGridBuilderElement( tag ) ) {
return;
}
But it’s not currently possible to disable for custom elements if required.
Would you guys consider adding a filter so the ajax caching can be easily disabled globally or add the ability to define a parameter for the element so it can be disabled on a per-element basis? I can help with the commit if necessary.
Thank you!
- AJ
Hello, Thanks a lot for sharing. As it is a feature request, please feel free to submit 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.
Whenever I set a row to full-width, I encounter the following CSS: .vc_row[data-vc-full-width-temp] {margin-left: calc(-50vw + 50%); right: 0;}. For example, with a content width of 1200px and a browser width of 1400px, the margin-left becomes -100px, and the margin-right is -15px. This results in inline CSS that applies padding-left: 0px and padding-right: 85px to the row, which causes the elements inside the row to be misaligned and not centered. I see other people mentioning this issue; you mentioned you couldn’t replicate it, so I wanted to provide more details for you. You can see for yourself at https://aviator.cmg.agency/restaurant/menus/.
I forgot to mention that the CSS is from /wp-content/plugins/js_composer/assets/css/js_composer.min.css?ver=8.7.2
Claude helped me fix the issue. The7’s vc_row file hasn’t been adjusted for your new method of handling full-width rows.
Hello,
We are getting the same issue that @WPExplorer is reporting in this comment:
https://codecanyon.net/item/wpbakery-page-builder-for-wordpress/242431/comments?page=1&filter=all#comment_31774452Our Visual Composer fields will no longer save any changes at all. Like we open a text field, change the text, save, and it immediately does not save and instead reverts to the previous content. And we know it’s specific to VC “BackEnd Editor” because if we change the exact same area to the default WordPress Code View and make the change and then save, it saves fine.
Hello, Our support team will be happy to investigate this further. Please open a ticket via the Customer Center: support.wpbakery.com and include temporary admin login details so we can check the issue directly 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.
Bonjour,
My name is Kym. I am wanting to purchase a number of plugins and scripts for my marketing agency and I would like to know if I am able install it via the WP Snippets AI plugin: https://wpsnippets.ai
If not, will it work with the Code Snippets plugin: https://wordpress.org/plugins/code-snippets
Also, is it compatible with Yoast SEO: https://yoast.com
Merci, Kym
Hello, Thanks for reaching out! We haven’t tested WPBakery Page Builder specifically with the WP Snippets AI or Code Snippets plugins, but WPBakery itself doesn’t rely on either of them.
It installs through the Plugins → Add New → Upload Plugin section in WordPress, and updates can be received automatically once the license is activated.
WPBakery is compatible with Yoast SEO, but it’s worth noting that Yoast’s content analysis may not fully read shortcode-based content, since WPBakery stores layout elements as shortcodes. For the best SEO experience, WPBakery includes its own built-in SEO feature designed to read the page content correctly.
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 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.
This item was featured on CodeCanyon
Power Elite Author
Contact the Envato Market Help Team
