• Resolved sgrenholm

    (@sgrenholm)


    I uploaded my local site to a ‘live’ dev site. I made no content changes – and certainly no code changes. The live site looks as I expected. But when I went in to edit any post or page (not just the /africa one), the editor immediately throws the following TypeError exception, and I can’t edit at all.

    That is bad enough. But the same error appears on Create Post, disabling new posts – and of course completely eliminating the usefulness of a blog site.

    I do not see this error in my local environment. Can anyone help with advice on what this issue is?

    This is WP 6.1.1 using Twenty-Twenty-Three. Only difference I know about is the default db used on the dev host is MariaDB, and my local used MySQL.

    Oh, and I am quite new to WordPress!

    TypeError: (0 , E.__experimentalUseSlotFills) is not a function
        at Un.Slot (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/edit-post/index.min.js?ver=5e678e88b06c72901493:25:688)
        at wt (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:47623)
        at $s (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:120736)
        at wl (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:88644)
        at bl (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:88572)
        at yl (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:88435)
        at il (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:85259)
        at fl (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:85646)
        at zn (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:32460)
        at El (https://dev.californiahcvtaskforce.org/wp-content/plugins/gutenberg/build/vendors/react-dom.min.js?ver=18:1:93359)

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter sgrenholm

    (@sgrenholm)

    I am proven, once again, to be an idiot.

    My fault here was I had the Gutenberg plugin enabled. But I did not use it, either in my local env or in my dev environment.

    It did not seem to make a difference in my local env, but disabling it in the hosted dev env fixed the problem.

    Keeping this here in case anyone else runs into this…

    Moderator Kathryn Presner

    (@zoonini)

    Glad you solved the issue by deactivating the Gutenberg plugin, thanks for reporting it!

    You’re definitely not an idiot! Having Gutenberg active should not be causing errors like that, and I haven’t been able to replicate it so far on my test site.

    If you’d be interesting in doing a bit of troubleshooting on that, I’d still be happy to look at it with you. I’d probably start by asking if you were running the latest version of Gutenberg, which is 15.1.1, and whether the issue occurs with all plugins other than Gutenberg deactivated. You can use the Health Check plugin’s troubleshooting mode for this, which will not change your live site. If the problem goes away, reactivate your plugins one by one (while still in troubleshooting mode) to find the culprit.

    If you’re satisfied just keeping the Gutenberg plugin inactive and going about your site launch, I’ll totally understand, though! Just let me know.

    Thread Starter sgrenholm

    (@sgrenholm)

    I could never replicate the problem using Gutenberg 15.1.0 on my local site. I upgraded it to 15.1.1 – still ok.

    On my hosted dev site, I had previously removed the 15.1.0 version. I just installed 15.1.1 and everything seems good – I can’t replicate the error creating/editing Posts or Pages (which was the problem before.)

    The earlier problem was in a newly created WordPress installation where the plugins were created from a Duplicator zip. As I mentioned, at that time, the site looked ok but the edit/create functions triggered the error. Maybe the plugin load order caused the earlier problem (?). But now, loading Gutenberg at the end with all other plugins still activated, no problem.

    I have the Health Check plugin but as everything is good now – even with the Gutenberg plugin 15.1.1 loaded – I would have to revert to 15.1.0 and try different load orders to see if I can trigger the problem again. I probably won’t do that!

    But if you want, I can provide a list of my plugins so someone else can do the combinatorics…

    Moderator Kathryn Presner

    (@zoonini)

    Thanks for the explanations @sgrenholm. I think if everything is now working fine, we can leave things. ?? Cheers!

    Thread Starter sgrenholm

    (@sgrenholm)

    No one likes unsolved mysteries…

    I believe I discovered the error of my ways. What I failed to remember is that this occurred after an export/import of the site (using Duplicator). And when exporting the site originally, Duplicator ‘warned’ me that some elements were large. One of these was

    //wp-content/plugins/gutenberg/build/components

    And I chose to filter those from the exported site data. And, of course, I forgot that I had done so.

    So, even though I wasn’t explicitly using the Gutenberg plugin, having it activated after import without those components caused the error.

    And thus, the eternal refrain “Don’t Do That.”

    Moderator Kathryn Presner

    (@zoonini)

    Good find, @sgrenholm – glad the mystery is solved, thanks for sharing what happened!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Type-error in edit-post’ is closed to new replies.