Robert
Forum Replies Created
-
Forum: Plugins
In reply to: [BuddyExtender] WP Health (about updating)Thank you Michael for your answer.
I’m glad that you’re keeping an eye on this plugin for bug fixes and compatibility.
Thank you!
Robert
Forum: Plugins
In reply to: [Iptanus File Upload] PHP 7 incompatibility checkThank you, Nickolas and Bob, for your answer.
Then I will use this plugin with “peace of mind” with PHP 7.2
And a big thanks, Nickolas, for this nice and convenient plugin!
Robert
Forum: Plugins
In reply to: [Iptanus File Upload] PHP 7 incompatibility checkHi,
Same thing for me.
For you info,
I ran the “PHP Compatibility Checker” plugin and here is the error, according to this plugin :
48 | ERROR | Using ‘break’ outside of a loop or switch structure is invalid and will throw a fatal error since PHP 7.0
Is it something to fix? Or not a real error?
Thank you,
Robert
Forum: Fixing WordPress
In reply to: Problem after 5.0 update with the classic editorVery glad, supergeek6.
I was happy on my part to find the solution on the WPBeginner website.
Between you and me, I don’t really know, at the present time, why and how this solution is working “under the hood”!
Forum: Plugins
In reply to: [Yoast SEO] Incompatible with Classic Editor/Disable GutenbergHi,
For your info (if it may help somebody),
After updating to WordPress 5.0 I had a problem with Gutenberg (not loading the content of previous posts and could not use it to create new content) and classic editor (was not able to see the content in view mode, but OK in text mode).
I’ve tried with another theme. Same problem.
I desactivated all the others plugins. Same problem.Then on my side it was not a problem of incompatibility between plugins or theme.
But finally I solved the problem by adding a single line in wp-config.php
See at https://www.wpbeginner.com/wp-tutorials/how-to-fix-white-text-and-missing-buttons-in-wordpress-visual-editor/ where I found the solution.
Add the following line at the very top after the php opening tag in wp-config.php :
define(‘CONCATENATE_SCRIPTS’, false);Now both Gutenberg and classic editor behave normally.
About SEO plugin, I’m using “The SEO Framework”. No problem at the present time with this plugin + Gutenberg.
Forum: Fixing WordPress
In reply to: Problem after 5.0 update with the classic editorHi,
About unresponsive…
Have you tried with another theme to see if the problem remains?
Don’t forget to delete your cache (wordpress and browser, just in case)
And desactivate plugins, one by one, and check if the problem is still there.
As example, vaszeit says, about Yoast :
“After some playing around, I discovered that Yoast plugin prevents Classic Editor and Disable Gutenberg from working properly. When Yoast is enabled, I get a blank editor window, even though there is content there. I also can’t add anything to that window as it’s completely unresponsive/disabled. When Yoast is disabled, the plugins work fine.”
at https://www.ads-software.com/support/topic/incompatible-with-classic-editor-disable-gutenberg/IF Yoast is a problem at the present time, better to use another SEO plugin, such as
“The SEO Framework” plugin (I’m using without any problem).Forum: Fixing WordPress
In reply to: Problem after 5.0 update with the classic editorHi balancecharm,
You’re right, the settings are “Default editor for all users” and “Allow users to switch editors” in writing, when you activate the Classic editor.
But, you may install “TinyMCE Advanced plugin” to add functionality (such as which buttons (strong, italic…) to show in view mode).
It’s working for Gutenberg and Classic Editor.
Forum: Fixing WordPress
In reply to: Problem after 5.0 update with the classic editorHi,
For your info (if it may help somebody),
After updating to WordPress 5.0 I had a problem with Gutenberg (not loading the content of previous posts and could not use it to create new content) and classic editor (was not able to see the content in view mode, but OK in text mode).
I’ve tried with another theme. Same problem.
I desactivated all the others plugins. Same problem.Then on my side it was not a problem of incompatibility between plugins or theme.
But finally I solved the problem by adding a single line in wp-config.php
See at https://www.wpbeginner.com/wp-tutorials/how-to-fix-white-text-and-missing-buttons-in-wordpress-visual-editor/ where I found the solution.
Add the following line at the very top after the php opening tag in wp-config.php :
define(‘CONCATENATE_SCRIPTS’, false);Now both Gutenberg and classic editor behave normally.