Viewing 12 replies - 1 through 12 (of 12 total)
  • Does this occur with a new page or only with an existing one? If the latter, what kind of blocks are in it?

    Thread Starter Niko Vittaniemi

    (@nikov)

    This occurs on an existing one and if i try to add a completely new page the same error seems to happen. The existing ones only have title and a paragraph blocks, some have the image block also but same thing. Seems to also affect posts so the editor in itself seems to be malfunctioning.

    I have tried to recreate this and see no problems. I used WordPress 6.4.1 without any plugins and with the new default theme TwentyTwentyFour. PHP in version 8.2.

    Can you have a look under Tools > Site Health to see if any anomalies are mentioned there?

    Thread Starter Niko Vittaniemi

    (@nikov)

    Thanks for looking into this @threadi o/ It seems that it has fixed itself now. So possibly some server related possibly firewall issue that was cleared? Anyways the website and the editor in pages and articles is working as it should.

    Thanks again and have a great weekend o/

    I am also having this issue on a site. Another site with the same configuration has no issues. Have re-installed WP, disabled plugins, etc. Console errors:

    JQMIGRATE: Migrate is installed, version 3.4.1
    private-apis.min.js:2 Uncaught Error: You tried to opt-in to unstable APIs without confirming you know the consequences. This feature is only for JavaScript modules shipped with WordPress core. Please do not use it in plugins and themes as the unstable APIs will removed without a warning. If you ignore this error and depend on unstable features, your product will inevitably break on the next WordPress release.
    at s (private-apis.min.js:2:1835)
    at blocks.min.js:3:90430
    at blocks.min.js:10:49752
    at blocks.min.js:10:49790
    s @ private-apis.min.js:2
    (anonymous) @ blocks.min.js:3
    (anonymous) @ blocks.min.js:10
    (anonymous) @ blocks.min.js:10
    post.php?post=294&action=edit:175 Uncaught TypeError: Cannot read properties of undefined (reading 'setCategories')
    at post.php?post=294&action=edit:175:11
    (anonymous) @ post.php?post=294&action=edit:175
    private-apis.min.js:2 Uncaught Error: You tried to opt-in to unstable APIs without confirming you know the consequences. This feature is only for JavaScript modules shipped with WordPress core. Please do not use it in plugins and themes as the unstable APIs will removed without a warning. If you ignore this error and depend on unstable features, your product will inevitably break on the next WordPress release.
    at s (private-apis.min.js:2:1835)
    at commands.min.js:7:42855
    at commands.min.js:7:47536
    at commands.min.js:7:47576
    s @ private-apis.min.js:2
    (anonymous) @ commands.min.js:7
    (anonymous) @ commands.min.js:7
    (anonymous) @ commands.min.js:7
    block-editor.min.js:26 Uncaught TypeError: Cannot read properties of undefined (reading '__unstableGetBlockProps')
    at block-editor.min.js:26:197666
    at block-editor.min.js:41:191704
    at block-editor.min.js:41:191747
    (anonymous) @ block-editor.min.js:26
    (anonymous) @ block-editor.min.js:41
    (anonymous) @ block-editor.min.js:41
    private-apis.min.js:2 Uncaught Error: You tried to opt-in to unstable APIs without confirming you know the consequences. This feature is only for JavaScript modules shipped with WordPress core. Please do not use it in plugins and themes as the unstable APIs will removed without a warning. If you ignore this error and depend on unstable features, your product will inevitably break on the next WordPress release.
    at s (private-apis.min.js:2:1835)
    at block-library.min.js:12:31472
    at block-library.min.js:14:666406
    at block-library.min.js:14:666450
    Thread Starter Niko Vittaniemi

    (@nikov)

    @bmatthewwhite and @threadi this actually happened again since i asked for a restore of the backup before this was fixed. The same thing happened and i had to wait a day to get the editor loading up again.

    Looking at the server configuration i think the main problem could be cronjobs. On this server they are run in the night time so that could be the “real” reason. If there is underlying changes that needed to be changed. So @bmatthewwhite i would advice to wait a day for this to clear up.

    I guess this is pretty impossible to replicate since it requires a specific server setup where normal cron is not used or launches at night.

    Has the current problem been solved?

    Encountering the same issue on WordPress 6.4.2. How was the problem resolved?

    I had the same problem, clearing my browser cache fixed the issue.

    I had the same problem. I performed your manipulations (clean cache + cloudflare cache) + deactivate plugins, it does not seem to work. I saw in another forum that you had to install the gutenberg plugin. It works now!

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Uncaught error: You tried to opt-in to unstable API:s’ is closed to new replies.