WPBakery Page Builder plugin and Visual Composer both will start working again. If you don’t have latest version of WPBakery Page Builder plugin or Visual Composer, then simply download “Class Editor” from .Īfter installing, activate it and you will see Gutenberg editor has been disabled and you are back to the life :). It will automatically revert it back to the classic editor. If you have latest version of WP Backery Page Builder, then the option to disable Gutenberg editor is available in general settings of WPBakery Page Builder plugin. Because Gutenberg Editor is not compatible with these wordpress plugins.įollowing are the option to fix this problem. SolutionĪs you all know in latest wordpress 5.1.0, the Gutenberg Editor (aka Block Editor) has been introduced which has replaced the classic editor.Ĭlassic Editor was compatible with VC composer and WP Backery Page builder before the new release. Because many websites are affected by this upgrade and VC Composr and WP Backery Page builder are not working anymore. Many developers are looking for solutions which can save their time and effort. Well, everyone who is using Visual composer or WPBakery Page Builder plugin and upgraded to WordPress 5.0.1, must have experienced the compatibility problem. ![]() Security patches are backported to the 3.7 branch, so these BC breaks also apply to versions 4.9.9, 4.8.8, etc. ![]() The Security team tried very hard to mitigate all of the vulnerabilities without any back-compat breaks, but unfortunately there were a few cases where that was not possible. In an official statement of wordpress they wrote more about compatibility issues ĥ.0.1 was just released to fix several security bugs. In this update wordpress team has fixed several security issues. Recently WordPress has released its latest version 5.0.1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |