Tim Nolte

@r81d3r version 1.7.10 was just released and this issue should be fixed now.

• This reply was modified 1 year ago by Tim Nolte.

We’ve had another report with some more details for this issue and I believe we may have identified the issue. I think when we do our testing we are using a Development environment and not a Production environment and this is cause different JavaScript to be loaded. I’ll be looking into this more tomorrow.

Our Devs aren’t able to reproduce that. can you please give us more information about your WordPress version, what other plugins you have installed, and what your hosting setup is like?

hmm, this is interesting as it is in my case this is causing the ability to connect Google Analytics to fail with no ability to choose and account or GA4 property.

Thanks!

I would think that perhaps the fix for this would be just to first include a check for the directory before trying to create it.

if ( ! is_dir( TRUNCLOGGING_DIR ) ) {
        mkdir(TRUNCLOGGING_DIR);
}

@dcid as we’re beginning to continue with our roll-out of the plugin is there any status update on this issue?

@jamesosborne apologizes for the delay. I have used the form to submit the Site Health information.

We have yet to roll out our next round of patching for the site so it is possible that this issue might be resolved in the latest version, however I’ve not had this issue on any other sites with the exact same hosting and site setup as the site with the issue.

So, I suspect this has to do with the differences between the hooks and APIs that used between the WordPress app vs using the Dashboard via the web. I think a lot of what Jan posted in his recent blog post is also at play(https://jan.boddez.net/articles/the-block-editor-custom-meta-and-activitypub). I want to say that I’ve had issues like this in the past, and my only solution was to begin posts in the app and then just save them as a draft and then finally publishing them from the web via my phone.

@pfefferle I would think that this issue would happen using the iOS WordPress app as well if that is what you have.

Unfortunately, this site is behind Azure Active Directory single-sign-on so I can’t really give you Dashboard access. For now we’ve simply disabled the SEO controls for Pages as our client hasn’t been using them at this point. We’ll have to investigate further once the client wants to begin using them.

We do already have a premium license that we could possibly use for support but we won’t pursue that for now.

It’s a really bizarre issue as sometimes, for certain people it will randomly start working, but then break again after later attempts. It’s also not all Pages but consistently some of them. I even attempted to roll back Yoast SEO and WordPress Core to earlier versions with it also remaining broken. It’s also happened across multiple browsers so it is just baffling to say the least.

Even though I haven’t hit the 200 properties limit yet I’m in agreement with @montythebrave that it simply being the fact that you can no longer use the plugin if your account has more than 200 properties is not really a proper response.

I’d like to flag this as an issue that needs to be explored for a solution. I understand there are limits in the API but then there needs to be an alternative solution. If there would be a way to configure the property identifiers via a configuration attribute(either in the web interface or via a constant) then at least we’d have a workaround for limits in the API.

Here is about the only thing that seems at issue

blocks.js?ver=1e16b1d8cd192ec1a469:13893 Updated Block: core/heading

blocks.js?ver=1e16b1d8cd192ec1a469:13893 Updated Block: core/image

react-dom.js?ver=18.2.0:22849 Uncaught TypeError: n.models.Page is not a constructor
    at post-edit.js?ver=f2c775a6667e3c9c92183bf09f93dc73:12:37585
    at fire (jquery.js?ver=3.7.1:3223:31)
    at Object.add [as done] (jquery.js?ver=3.7.1:3282:7)
    at post-edit.js?ver=f2c775a6667e3c9c92183bf09f93dc73:12:37575
    at data.js?ver=2b5bb06caaeb5048ed96:3093:45
    at Array.forEach (<anonymous>)
    at notifyListeners (data.js?ver=2b5bb06caaeb5048ed96:3093:25)
    at Object.emit (data.js?ver=2b5bb06caaeb5048ed96:3117:7)
    at globalListener (data.js?ver=2b5bb06caaeb5048ed96:3185:13)
    at data.js?ver=2b5bb06caaeb5048ed96:3354:9
(anonymous) @ post-edit.js?ver=f2c775a6667e3c9c92183bf09f93dc73:12
fire @ jquery.js?ver=3.7.1:3223
add @ jquery.js?ver=3.7.1:3282
(anonymous) @ post-edit.js?ver=f2c775a6667e3c9c92183bf09f93dc73:12
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:3093
notifyListeners @ data.js?ver=2b5bb06caaeb5048ed96:3093
emit @ data.js?ver=2b5bb06caaeb5048ed96:3117
globalListener @ data.js?ver=2b5bb06caaeb5048ed96:3185
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:3354
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:2853
dispatch @ data.js?ver=2b5bb06caaeb5048ed96:1031
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:1770
(anonymous) @ redux-routine.js?ver=154d0b98be93c015ec5a:875
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:1690
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:1760
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:2765
(anonymous) @ editor.js?ver=d4a7ac425a2df2d760ab:4003
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:1768
(anonymous) @ redux-routine.js?ver=154d0b98be93c015ec5a:875
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:1690
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:1760
(anonymous) @ data.js?ver=2b5bb06caaeb5048ed96:2765
(anonymous) @ editor.js?ver=d4a7ac425a2df2d760ab:12555
commitHookEffectListMount @ react-dom.js?ver=18.2.0:23160
commitLayoutEffectOnFiber @ react-dom.js?ver=18.2.0:23278
commitLayoutMountEffects_complete @ react-dom.js?ver=18.2.0:24698
commitLayoutEffects_begin @ react-dom.js?ver=18.2.0:24684
commitLayoutEffects @ react-dom.js?ver=18.2.0:24622
commitRootImpl @ react-dom.js?ver=18.2.0:26833
commitRoot @ react-dom.js?ver=18.2.0:26692
performSyncWorkOnRoot @ react-dom.js?ver=18.2.0:26127
flushSyncCallbacks @ react-dom.js?ver=18.2.0:12052
flushPassiveEffectsImpl @ react-dom.js?ver=18.2.0:27070
flushPassiveEffects @ react-dom.js?ver=18.2.0:26994
(anonymous) @ react-dom.js?ver=18.2.0:26779
workLoop @ react.js?ver=18.2.0:2653
flushWork @ react.js?ver=18.2.0:2626
performWorkUntilDeadline @ react.js?ver=18.2.0:2920

react-dom.js?ver=18.2.0:18697 The above error occurred in one of your React components:

    at https://gateshosting-accelerateed.ddev.site/wp/wp-includes/js/dist/editor.js?ver=d4a7ac425a2df2d760ab:12496:3
    at https://gateshosting-accelerateed.ddev.site/wp/wp-includes/js/dist/editor.js?ver=d4a7ac425a2df2d760ab:12081:5
    at WithRegistryProvider(Component)
    at SlotFillProvider (https://gateshosting-accelerateed.ddev.site/wp/wp-includes/js/dist/components.js?ver=130f16b14b15a9666b83:36374:3)
    at provider_SlotFillProvider (https://gateshosting-accelerateed.ddev.site/wp/wp-includes/js/dist/components.js?ver=130f16b14b15a9666b83:36396:5)
    at Provider (https://gateshosting-accelerateed.ddev.site/wp/wp-includes/js/dist/components.js?ver=130f16b14b15a9666b83:36531:3)
    at Editor (https://gateshosting-accelerateed.ddev.site/wp/wp-includes/js/dist/edit-post.js?ver=57aa460a64bb0e4ae963:9253:3)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.
logCapturedError @ react-dom.js?ver=18.2.0:18697
update.callback @ react-dom.js?ver=18.2.0:18730
callCallback @ react-dom.js?ver=18.2.0:13933
commitUpdateQueue @ react-dom.js?ver=18.2.0:13954
commitLayoutEffectOnFiber @ react-dom.js?ver=18.2.0:23401
commitLayoutMountEffects_complete @ react-dom.js?ver=18.2.0:24698
commitLayoutEffects_begin @ react-dom.js?ver=18.2.0:24684
commitLayoutEffects @ react-dom.js?ver=18.2.0:24622
commitRootImpl @ react-dom.js?ver=18.2.0:26833
commitRoot @ react-dom.js?ver=18.2.0:26692
performSyncWorkOnRoot @ react-dom.js?ver=18.2.0:26127
flushSyncCallbacks @ react-dom.js?ver=18.2.0:12052
flushPassiveEffectsImpl @ react-dom.js?ver=18.2.0:27070
flushPassiveEffects @ react-dom.js?ver=18.2.0:26994
(anonymous) @ react-dom.js?ver=18.2.0:26779
workLoop @ react.js?ver=18.2.0:2653
flushWork @ react.js?ver=18.2.0:2626
performWorkUntilDeadline @ react.js?ver=18.2.0:2920

react-dom.js?ver=18.2.0:12066 Uncaught TypeError: n.models.Page is not a constructor
    at post-edit.js?ver=f2c775a6667e3c9c92183bf09f93dc73:12:37585
    at fire (jquery.js?ver=3.7.1:3223:31)
    at Object.add [as done] (jquery.js?ver=3.7.1:3282:7)
    at post-edit.js?ver=f2c775a6667e3c9c92183bf09f93dc73:12:37575
    at data.js?ver=2b5bb06caaeb5048ed96:3093:45
    at Array.forEach (<anonymous>)
    at notifyListeners (data.js?ver=2b5bb06caaeb5048ed96:3093:25)
    at Object.emit (data.js?ver=2b5bb06caaeb5048ed96:3117:7)
    at globalListener (data.js?ver=2b5bb06caaeb5048ed96:3185:13)
    at data.js?ver=2b5bb06caaeb5048ed96:3354:9

@maybellyne so if you notice my last comment and my updates the priority hook is not actually the issue and doesn’t have any impact on this. I was mistakenly switching between to different environment when I was trying to test that. This issue is specifically due to the Yoast SEO metabox trying to be presented on the Block Editor screen. Turning off the SEO settings for pages, so the metabox doesn’t attempt to render fixes the issue. Turning back on the SEO settings for Pages causes it to be broken again.

This is with the latest version of WordPress, even attempts to rollback to older versions of WordPress didn’t resolve the issue. This is also testing with a number of Yoast SEO plugin versions.

So actually, I was on the wrong environment when testing disabling the hook. I’m still in a situation where having the SEO tools on for some Page editing is still breaking the Block Editor. Turning it off allows the Block Editor to work.

This code we are using follows what is documented.

https://developer.yoast.com/customization/yoast-seo/filters/change-metabox-prio-filter/