Moderator
t-p
(@t-p)
What did you change/modify/update, etc., before this issue occurred?
I’ve been trying to make my site faster so I’ve been removing plugins I don’t use anymore, but other than deactivating/deleting plugins I haven’t really made any other modifications.
I did add this lines to my site root’s .htaccess because I wanted another non-WP script to not log me out so quickly:
php_value session.gc_maxlifetime 15000
Those are the only changes I can think of
Moderator
t-p
(@t-p)
I did add this lines to my site root’s .htaccess because I wanted another non-WP script to not log me out so quickly:
Have tried to undo that for troubleshooting purposes?
yes of course, but it didn’t make a difference
Moderator
t-p
(@t-p)
Troubleshooting with your browser: Your browser can help you identify JavaScript issues or conflicts and this article can assist you in doing that diagnosis. This could help identify Visual Editor issues as well.
The JS console shows there is some kind of loop (probably why it’s getting stuck) that keeps generating errors… but I don’t recognize a particular plugin causing it…
Here’s a screenshot of the JS console:
https://snipboard.io/xQibFs.jpg
Moderator
t-p
(@t-p)
but I don’t recognize a particular plugin causing it
Try deactivating ALL (yes all) plugins temporarily to see if this resolves the problem (plugin functions can interfere). If this works, re-activate them individually (one-by-one) to find the problematic plugin(s).
-
This reply was modified 3 years, 11 months ago by
t-p.
I had done that with the Health Check plugin… deactivated all plugins AND themes but if you think doing it via Health Check plugin is not reliable I’ll try manually deactivating them all
Well, the calls to the REST API are returning 403 messages, so yes, that is your problem. Without the REST API calls, the editor will not work.
So, you need to figure out why your server is rejecting the REST API calls. Look in the htaccess, look at the plugins, and generally figure out what changed to cause this to occur.
I did delete an old cache plugin. Is it possible that was the reason?
It is impossible for us to know why your server is returning 403 responses. I don’t think deleting a plugin would cause it, cache or no cache.
Generally, a 403 means something is intentionally blocking these requests. The htaccess is the first place I would look. Any plugins you have is another. Unless you really disable all plugins and check htaccess and such, there is no possible way to tell what is going on. You have to track down the cause.
Sometimes…
I just go in with FTP or a File Manager and manually rename the plugin directory…
That Health Check method usually works but sometimes going old school is best.
Occasionally I’ve done that, found the problem went away, turned each plugin back on one by one… and the problem doesn’t come back!!!
Go figure that one out.
And there are times when the theme clobbers things. That’s usually a function…
Finally, some really great plugins add a directive to htaccess (or several (or even many)) and something goes wrong.
You mentioned a few cache plugins… Those often rewrite the htaccess… and sometimes break it.
I have tried everything that was suggested here:
1. disable all plugins
2. disable theme / activate 2020 theme
3. remove everything from .htaccess (except the normale WP rewrite section)
4. rename the plugin folder via FTP
Nothing seems to fix the problem. The JS console keeps spitting out those errors on a loop any time I go into the editing page or a post…
I’mr really at a loss here
I just tried enabling the Debug mode in wp-config and the following errors appeared at the top of the page:
Deprecated: load_plugin_textdomain was called with an argument that is deprecated since version 2.7.0 with no alternative available. in /home/chaindlk/public_html/wp/wp-includes/functions.php on line 5008
Deprecated: add_option was called with an argument that is deprecated since version 2.3.0 with no alternative available. in /home/chaindlk/public_html/wp/wp-includes/functions.php on line 5008
Deprecated: has_cap was called with an argument that is deprecated since version 2.0.0! Usage of user levels is deprecated. Use capabilities instead. in /home/chaindlk/public_html/wp/wp-includes/functions.php on line 4998
Could this be related?
No, those are just warnings. However, they do indicate that you don’t have all your plugins turned off, and that you are possibly using old plugins or a theme that is using old plugins in it.
Specifically, this line:
Deprecated: load_plugin_textdomain was called with an argument that is deprecated
That happens when you have a plugin calling the load_plugin_textdomain function with a second parameter. The second parameter to that function was removed from WordPress in December 2008, and WordPress itself does not call it.
So, yes, you do have something else running on your site that isn’t a default part of WordPress. Given that it is loading plugin translations, it’s probably a plugin. Could be the theme, given that there are also old calls to add_option and has_cap as well.
Some kind of add-on is still running on your site. What add-on did you not disable?
What files exist in the /wp-content folder?
