Support » Fixing WordPress » Block/Visual Editor Doesn’t Work

  • Resolved Jim

    (@jwmc)


    The Block Editor is not working for me. When I try to create a new page, the ‘+’ button is greyed out. Adding paragraphs does not add new blocks, ‘i’ shows only one block.

    The Block Navigation button opens to show ‘Classic’. If I click that, a ‘More Options’ menu appears that contains ‘Convert to Blocks’. Doing that then shows HTML, e.g.:

    <!-- wp:paragraph -->
    <p>Can't create blocks<br>
    asdfads<br>
    aasdfds</p>
    <!-- /wp:paragraph -->

    But the More Options menu has a choice ‘View as HTML’.

    I have flushed all caches and tried development mode on CloudFlare. My user settings have a nickname and ‘Disable visual editor’ is unchecked, but I toggled those settings to make sure. I resaved permalink settings.

    I disabled all plugins with the Health and Troubleshooting plugin. Nothing has worked.

    In the javascript console for the edit page, the following appear:

    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
    JQMIGRATE: Migrate is installed, version 1.4.1 load-scripts.php:8:542
    onmozfullscreenchange is deprecated. components.min.js:12:80762
    onmozfullscreenerror is deprecated. components.min.js:12:80762
    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 don’t really understand this. I am dead in the water here – please help!
    WordPress is 5.2.

Viewing 15 replies - 1 through 15 (of 18 total)
  • Moderator t-p

    (@t-p)

    Please try the basic troubleshooting suggested in this 5.2 master list: https://wordpress.org/support/topic/read-this-first-wordpress-5-2-master-list/

    Jim

    (@jwmc)

    Thanks for reply. Near as I can tell I did everything in that list. Results are in my original post (except trying default theme, which I also did).

    Moderator t-p

    (@t-p)

    Site Health Check:
    Building on the Site Health features introduced in 5.1, this 5.2 release adds two new pages to help debug common configuration issues.

    Check it and see if any issue.

    Jim

    (@jwmc)

    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 5 months ago by  Jim.
    • This reply was modified 5 months ago by  Jim.
    Moderator t-p

    (@t-p)

    Have auto updated your site?

    If so, try MANUALLY updating. Download WordPress again and unzip it, and use that to copy up. Access your server via SFTP or FTP, or a file manager in your hosting account’s control panel (consult your hosting provider’s documentation for specifics on these), and delete then replace your copies of everything on the server EXCEPT the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings. (NOTE: do not delete the wp-content directory or your wp-config.php file). Please read the Manual Update directions first.

    Backup: If you haven’t already done, always backup everything (including your database) before doing any actions, just in case something really goes wrong. You can never have enough backups!

    Jim

    (@jwmc)

    Ok, thanks, will try that. May take me up to 2 days before I can do it.

    Jim

    (@jwmc)

    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.

    Moderator t-p

    (@t-p)

    For the new Block editor to function, the REST API should be available. Is REST API available on your site?

    Jim

    (@jwmc)

    Hmmm, not sure how to test that. But when I go to
    https://forestpathology.org/wp-json/wp/v2
    I get a whole lot of output. How can one tell if it looks right?

    Moderator t-p

    (@t-p)

    The new Site Health Check in WP 5.2 can report that to you:

    Dashboard > Tools > Site Health

    Jim

    (@jwmc)

    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 5 months ago by  Jim.
    Moderator t-p

    (@t-p)

    very first tab titled “STATUS”

    Jim

    (@jwmc)

    Right, please see second paragraph of my post. Nothing wrong with REST API.

    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.

    Jim

    (@jwmc)

    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

Viewing 15 replies - 1 through 15 (of 18 total)
  • You must be logged in to reply to this topic.