With the plugin loaded, when selecting a category from the “Most Used” tab, the selection is lost when the post is saved as draft or published. This appears to be an issue with the “Classic Editor” plugin as well as this one. Categories selected from the “View All” tab do remain selected on save. At least that is what my testing shows, affects all themes after updating to WordPress 6.7.
]]>This plugin generates these errors:
Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the disable-gutenberg domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.)
]]>Hey Jeff, thanks for your plugin and supporting the WordPress community!
Running the plugin on some sites in PHP 8.1+ throws some warnings surrounding the use of explode() when the string is null. Specifically, plugin-core.php:407, method: disable_gutenberg_explode($string) when trimming. Recommend either adding a default value $string = '' or some quick error checking in the method before using the variable on line 409.
Happy to submit a PR!
]]>After updating Safari to its latest version (18), the main column, where “widgets” appear after the text area, has gone crazy. See a screenshot.
I tested on Firefox 129 and everything is normal there.
]]>I am using the Disable Gutenberg plugin to disable it for some specific custom post types. For regular pages, Gutenberg is still used.
However, when I activate the plugin, some Gutenberg block types lose their CSS. For example, the “Media & Text” and the “Columns” block lose their responsive column settings. Instead, they just display above each other.
Is this a bug?
This plugin is incompatible with Breakdance Builder. It throws ERROR 500. Can you please fix it and make it compatible? Thanks
I have an issue and had to deactivate classic plugin to test. When reactivating your plugin the page I am having an issue with now opens in Gutenberg version of the classic editor instead of the true classic editor. How do I get the page back to the true classic editor.
]]>Hello, I see there is an option to disable gutenberg on custom templates but I’m wondering if it’s possible to disable gutenberg on regular templates from WP standard template hierchy like page.php, front-page.php, category.php, etc….
My thought is I’d like to disable gutenberg everywhere but then have a custom template where the user can use gutenberg. Ideally it’d actually be easier to have an “enable” on custom template option instead of only disable options.
Thank you!
]]>I’ve just noticed the latest WordPress update adds a section called ‘Patterns’ which is only used in the Block Editor.
Do you have any plans to disable this with the plugin in a future update?
]]>Hi!
There is a CSS file related to Gutenberg (I guess?) being loaded. This one: https://manualdousuario.net/wp-includes/css/dist/components/style.min.css?ver=6.4.3
Shouldn’t it be blocked by this plugin?
]]>So strange issue appeared on a site where we were able to install plugins from the WordPress repository. But if we tried to upload plugins manually we kept getting a 403 error. I disabled this plugin and was then able to upload plugins again. I then tried using Disable Classic Editor and was also still able to upload plugins. Running PHP 8.1 as a FYI.
]]>Hello, Im trying to unistall this plugin, and now, when I try to publish an article, the changes are not saved and it remains a draft.
How can I solve it?
]]>Hey there,
Thanks for this plugin, it’s one of the first we install on all our new WP projects.
I’d like to request that Semantic Versioning is used for release numbers, if possible. We install plugins through the wpackagist repository with composer which by default installs updates to the latest minor version.
For example, when you run composer require wpackagist-plugin/disable-gutenberg the latest version is locked in the composer.lock file, and the composer json will contain something like:
"wpackagist-plugin/disable-gutenberg": "^3.0",
Meaning running composer update will allow updates to any version >= 3.0 && < 4.0
A lot of our WP sites are currently using the ^2.4 range as this was the latest version when we installed the plugin. This means we can’t update to the latest version of the plugin by simply running composer update as we would like to, we need to manually edit the composer.json file and update the version constraint to ^3.0 first.
Looking at the version history for the plugin, it appears there are no backwards incompatible or breaking changes between 2.9 and 3.0, so theoretically the 3.0 release could have been 2.10. I understand this is entirely your prerogative but on the principle of “don’t ask you don’t get” I figured it was worth raising here ??
Cheers, Andy
]]>Hello,
there is a problem with the new wordpress 6.4 lightbox option. When the plugin is activated and I try to use some pages with Gutenberg, the lightbox doesn’t work.
]]>If I click the Add Media button in the post editor, a messed up media section appears below everything else, half hidden off the left side of the screen and so unusable, and also suddenly I can’t scroll the page at all. I have to reload the page in the browser just to get control back. Not sure what’s happening here? Thanks.
]]>Strange issue, and I’m not sure if you’ll be able to identify it without access to the website (which is currently under construction). It appears that the plugin is either removing or canceling out the css /wp-includes/css/dist/block-library/style.min.css file. When I deactivate the plugin, everything returns to normal.
The issue appears on the sidebar (ie: recent posts) where it looses all stylings as the CSS isnt loaded.
thanks!
Hi! We’ve been using disable-gutenberg for several years now. It’s worked great for us! But we’ve run into a snag that’s causing our automated deploy processes some trouble…
We use WP CLI to install our plugins for our self-hosted WP instances, but ever since disable-gutenberg 3.0+, the plugin throws a fatal error whenever we try to activate it via the command line:
PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, function "disable_gutenberg_dismiss_notice_activate" not found or invalid function name in /.../wp-includes/class-wp-hook.php:310I believe this is because the file defining the function disable_gutenberg_dismiss_notice_activate (in inc/settings-reset.php) is being required only if is_admin() is true. This explains how we’re able to activate the plugin on the WP backend, but not via the CLI!
We’re able to replicate this on a fresh WP install with no other plugins and the default themes:
1. wp plugin install disable-gutenberg will successfully install the plugin.
2. wp plugin activate disable-gutenberg will cause the fatal error.
3. Activating the plugin in the backend works without any problems!
I was able to successfully activate the plugin with WP CLI when I moved disable-gutenberg.php:100 out of the is_admin() check.
Thanks!
]]>[18-Sep-2023 22:06:25 UTC] PHP Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, null given in /app/wp-includes/class-wp-user-query.php:483Stack trace:#0 /app/wp-includes/class-wp-user-query.php(483): array_filter(NULL)#1 /app/wp-includes/class-wp-user-query.php(79): WP_User_Query->prepare_query(Array)#2 /app/wp-includes/user.php(775): WP_User_Query->__construct(Array)#3 /app/wp-includes/user.php(1668): get_users(Array)#4 /app/wp-admin/includes/meta-boxes.php(977): wp_dropdown_users(Array)#5 /app/wp-admin/includes/template.php(1443): post_author_meta_box(Object(WP_Post), Array)#6 /app/wp-admin/edit-form-advanced.php(688): do_meta_boxes(Object(WP_Screen), 'normal', Object(WP_Post))#7 /app/wp-admin/post.php(206): require('/app/wp-admin/e...')#8 {main}thrown in /app/wp-includes/class-wp-user-query.php on line 483I have a website updated to PHP 8.1 and wordpress 6.3.1. I’m getting the above error inside /wp-admin on the pages overview page, as well as inside individual pages.
Disabling all other plugins has no effect, it only resolves when I disable this ‘disable gutenberg’ plugin. Switching to a default theme also has no effect, the errors persist.
Downgrading to PHP 7.4 prevents it from being a fatal error, but the error is still present.
]]>hello,
I am facing an issue related to the “Disable Gutenberg” plugin in my WordPress setup. The primary problem revolves around the inability to change the Heartbeat API intervals when the “Disable Gutenberg” plugin is activated. Despite trying various approaches, I have not been able to modify the Heartbeat API intervals effectively.
Here is a concise breakdown of the problem and the steps I’ve taken:
- Manual Code in functions.php: I attempted to manually change the Heartbeat API interval by adding custom code to the
functions.phpfile of my theme. However, even with the code in place, the Heartbeat API intervals remained unchanged. - LiteSpeed Cache Integration: I explored using the LiteSpeed Cache plugin to manage Heartbeat API intervals. Despite configuring the LiteSpeed Cache settings to modify the intervals, the changes were still not reflected in the functionality. This suggests that the issue is not specific to the LiteSpeed Cache integration.
- Heartbeat Control Plugin: I also installed and tested the “Heartbeat Control” plugin, which is designed to provide control over the Heartbeat API intervals. However, even with this plugin active, I encountered the same problem: the Heartbeat API intervals did not change as intended.
What’s interesting is that when I completely disable the Heartbeat API, the plugin works as expected. However, I do not want to disable the Heartbeat API entirely, as it serves important functionality.
To gain more insight into the issue, I monitored the admin-ajax requests using the Chrome browser’s inspect network section. Despite observing these requests, I have not been able to pinpoint the exact cause of the problem.
I’m seeking assistance to identify the root cause of this compatibility issue and find a solution that enables me to change the Heartbeat API intervals without having to disable it entirely.
]]>Hi there! Just thought I’d note that the disable for templates field doesn’t seem to be working in wordpress 6.3. I made a template and added template-classic-editor.php to the field but it’s not effecting the pages editor. I’ve worked around by setting by page id which does work. cheers!
]]>Hi, I am using Generatepress premium. When I have your plugin activated the colour section of the theme customizer does not work (it is empty). If I deactivate the plugin it works again. It happens in all my webs with generatepress and this plugin and The WordPress new version 6.3 (that I switched to today). The webs with the previous WordPress version are fine.
Thanks
]]>Zuerst mal Danke für dieses Plugin, wir setzen es in allen Websites ein.
Kleiner Hinweis:
Seit Version 3.0 wird der Editor (bei allen Sites) automatisch im Text-Modus ge?ffnet. Auch wenn, wie üblich zuletzt im visuellen Tab geschrieben wurde.
Uh oh, here comes Doug with another suggestion… RUN, JEFF! ??
With the classic editor plugin, they have a setting to allow users to switch between the block or classic editor, and then on the pages/posts, they can switch between the two editor options.
I’d love to see Disable Gutenberg come with that same feature, if possible. Let me know if you need me to send you a screen shot or two (will do it directly).
Thanks, Rock Starr!
]]>When this plugin is activated, front-end ajax calls die because of a missing function.
Example error message:
[26-Mar-2023 12:04:42 UTC] PHP Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, function “disable_gutenberg_register_settings” not found or invalid function name in /mnt/web208/b3/15/51893315/htdocs/opajaap/betatest/wp-includes/class-wp-hook.php:308
PHP version 8.0.28
WP version 6.2-RC4
Is there a way to enable spellcheck for the tinymce?
I use WordPress to receive post from users and there are a lot of misspelling but the editor is not highlighting them
]]>Hi dear support,
thank you for your great Plug-In.
I got a javascript error on the “my account” page. So I looked it up, is says:
ERROR PeerJS: Error: Lost connection to server. peerjs.min.js:48:1689
????_print https://unpkg.com/[email protected]/dist/peerjs.min.js?ver=6.1.1:48
????error https://unpkg.com/[email protected]/dist/peerjs.min.js?ver=6.1.1:48
When I looked it up what is js is meant to be I found out that it is a Gutenberg cloud .. https://wptavern.com/gutenberg-cloud-plugin-for-wordpress-is-now-in-beta
We don’t need this and probably a lot of people dont need this. It generates js errors and server load, so my question is: Can you deactivate or implement a function to deavtivate this script?
Thank you in advance!
Hi Jeff
Thanks for the plugin, unfortunately it does not seem to be compatible with the Gravity Forms plugin.
In Disable Gutenberg settings, I have enabled Gutenberg for pages but have it disabled for posts. When I go into a post to edit, I am missing the Gravity forms “Add Form” button.
If I disable your plugin or install the Classic Editor plugin the button comes back.
I do not have any other plugins activated and am using the Twenty-Twenty theme.
Any help would be appreciated
Thanks
]]>Hi,
Problems with the footer. Created with Gutenberg Widgets.
The upper pic is when the Disable Gutenberg is not activated (all good). And the lower one is when I have activated the plugin. As you can see, there is some extra padding around the image and the social media icons are totally wrong. I tried to change the settings of the icons, but no effect. I have only checked the following settings: Disable for Post and Disable for Ohjelmat (CPT).
https://pasteboard.co/r4RgBDjd5Wvl.png
Thanks!
]]>I’m disabling Gutenberg for everything except one particular template. Do I also then need to enable the front end styles across the whole site to use those? Or will the front end styles only be enabled for that particular template?
]]>Yoast SEO does not work with?Disable Gutenberg
There is no way to edit the data?https://joxi.ru/4AkXGgPcVXqDwr in Seo Yoast?if classic editor plugins are enabled. If they are disabled, SEO Yoast works correctly.
]]>