chelseycontier

That sorted it, thanks so much for your help!

Hi Margaret,

Apologies for the long delay in getting back to you. It does appear that there was a user with the username “_”. We’ve now removed this user, along with several other users with similarly strange usernames. Unfortunately the error persists: the first user on the list is the only one that loads before hitting the critical error I previously reported.

I’ve emailed across the WP CLI output of the command you sent across previously, though I’ve done it for the first user on our staging site (where the same issue is present).

Let me know if there’s anything else you need from me!

Chelsey

Hi Margaret,

Thanks for sending that command over. I’m happy to look into running that and getting you the output, but it’s not individual users where we’re seeing the critical error. Rather, it’s the user list: https://smile.d.pr/i/TYpgPs — apologies if I wasn’t clear about that before. I’ve loaded up a few user pages (e.g. https://oursite.com/wp-admin/network/user-edit.php?user_id=25), and they all display as expected. I can still get you the output of that CLI command if that’s helpful, just let me know what you’d like me to do.

Chelsey

Hi Margaret,

Appreciate you trying to get to the root of the problem! We do have WP-CLI on our hosting – what commands would you need us to run?

Chelsey

Hi Margaret,

I’ve just sent over what I could get for you. Let me know if there’s anything else you need.

Chelsey

Hi Margaret,

Thanks for getting back to me. Yes, it’s a WP Multi Network, so there’s one master network under which sit 2 WP Multisite networks.

I’ve emailed the output of that query as you requested. Let me know if there’s anything else you need from me!

Chelsey

Thanks Maybellyne, it would be great to have this error disappear. I’ll look forward to hearing updates on progress towards a bugfix.

Thanks very much Peter. I’ve just sent the diagnostic report as you described.

The file storage fallback isn’t working for us – we need mysql because of our multi-sever configuration.

Let me know if there’s anything else you need from me!

Cheers,
Chelsey

Thanks for clarifying that.

Is there a reason why Yoast doesn’t override theme meta description tags?

Removing the meta description from the theme leaves our sites with no fallback if we need to disable or remove Yoast. From our perspective, this goes against the idea of WordPress being ‘pluggable’: WP plugins are optional add-ons, even if many (such as Yoast) are advisable for running an optimised site. It doesn’t make sense to us that our themes should omit basic SEO fields in order to rely on a plugin.

Would it be possible to request that the Yoast team reviews this decision in an effort to allow theme builders to include fallbacks in their themes?

Hi Maybellyne,thanks for getting back to me.

No, that code is in the header.php file of the theme we’ve built. Despite having values set in the Yoast meta description field for various posts and pages on the site, both the theme’s meta description and the Yoast meta description values are rendered on the page, meaning the pages aren’t optimised as expected.