Jim

Now we’re getting somewhere. Apparently I had not tried another browser. The editor seems to work properly in Safari, but still not in Firefox.

I enabled script debugging per the article you cited; still didn’t work in Firefox.

My first post reported the javascript console contents for the edit page, but there is much more with script debugging on. Hopefully you will be able to spot one or more relevant issues:

Request to access cookie or storage on “https://fonts.googleapis.com/css?family=Noto+Serif%3A400%2C400i%2C700%2C700i&ver=5.2” was blocked because we are blocking all third-party storage access requests and content blocking is enabled. post-new.php
Request to access cookie or storage on “https://secure.gravatar.com/avatar/83cbe34a8f5a60d6b05f4e117ea71ab2?s=26&d=mm&r=g” was blocked because we are blocking all third-party storage access requests and content blocking is enabled. post-new.php
Request to access cookie or storage on “https://secure.gravatar.com/avatar/83cbe34a8f5a60d6b05f4e117ea71ab2?s=64&d=mm&r=g” was blocked because we are blocking all third-party storage access requests and content blocking is enabled. post-new.php
JQMIGRATE: Migrate is installed with logging active, version 1.4.1 jquery-migrate.js:23:2
onmozfullscreenchange is deprecated. components.js:6575:33
onmozfullscreenerror is deprecated. components.js:6575:33
JQMIGRATE: jQuery.fn.load() is deprecated jquery-migrate.js:45:4
console.trace() jquery-migrate.js:47:5
jQuery 2
<anonymous> https://forestpathology.org/wp-content/themes/generatepress/js/admin/block-editor.js?ver=2.2.2:87
JQMIGRATE: ‘ready’ event is deprecated jquery-migrate.js:45:4
console.trace() jquery-migrate.js:47:5
jQuery 9
<anonymous> https://forestpathology.org/wp-content/plugins/profile-builder/features/content-restriction/assets/js/content-restriction.js?ver=2.9.9:29
jQuery 4
Warning: Unsafe lifecycle methods were found within a strict-mode tree:
in StrictMode (created by Editor)
in Editor (created by ComponentWithSelect)
in ComponentWithSelect (created by Context.Consumer)
in WithSelect(Editor)

componentWillUpdate: Please update the following components to use componentDidUpdate instead: FillComponent

Learn more about this warning here:
https://fb.me/react-strict-mode-warnings react-dom.js:500:7
Warning: Can’t call setState on a component that is not yet mounted. This is a no-op, but it might indicate a bug in your application. Instead, assign to this.state directly or define a state = {}; class property with the desired state in the t component. react.js:276:7
Request to access cookie or storage on “https://cdnsure.com/assets/style” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.
post-new.php

​

I already posted everything I could get out of Site Health. I can’t see anything about REST API. In which tab and section should it be?

Edit – I found it under Site Health > Status > Passed Tests. It doesn’t show directly on the Status screen unless it’s a problem. Rest API is reported as passed.

• This reply was modified 7 years, 1 month ago by Jim.

The site seems to stay auto-updated (despite the critical error and WP_AUTO_UPDATE_CORE noted previously). I first went to Dashboard > Update where it says:

You have the latest version of WordPress.
If you need to re-install version 5.2, you can do so here:

Does that do the same thing as manually replacing the files? It was successful, but did not fix the problem.

SO, I went ahead and did it manually per the instructions you Kindly linked to. Also cleared all the caches. Still no joy.

I guess you’re referring to Tools > Site Health (I also have the plugin Health Check & Troubleshooting).

In Site Health I see four sections, not sure which you’re referring to.

1. Status: I have one critical issue, background updates not working as expected (WordPress security and maintenance releases are blocked by define( ‘WP_AUTO_UPDATE_CORE’, false );). I tried it again with this tool, no fix.

2. Info doesn’t seem to provide debug info that I can see.

3. Troubleshooting: Looks like this does the same as the plugin Health Check & Troubleshooting, which I already used to deactivate all plugins, which didn’t fix it.

4. Tools: all files passed the File Integrity Check. Don’t think there’s any problem with email.

By the way, we have another site in the same hosting account (SiteGround); it’s behaving the same way.

• This reply was modified 7 years, 1 month ago by Jim.
• This reply was modified 7 years, 1 month ago by Jim.

Sorry, it actually was published, but I gave you the preview link instead of permalink. Hopefully this will work:
https://forestpathology.org/temp/

• This reply was modified 7 years, 7 months ago by Jim.

Yes, thank you. You can go to https://forestpathology.org/wp-login.php.
You don’t need an actual login, just enter anything and the reCaptcha task window will pop up, at least it does for me.

You can see a screenshot of my reCaptcha settings here:
https://forestpathology.org/wp-content/uploads/2018/11/Google-recaptcha-settings.png. As noted, my Google account is also set for invisible.