Erro gerando no Divi quando o Yoast está ativo

Hi @thicoec2020 ,

As this is an English support forum and we can only provide support in English (for the benefit of other readers), we’ve translated your post using GoogleTranslate to understand your issues. For future communications, please reply in English.

==================
Hello, I am facing a problem that I believe is related to Yoast SEO. Whenever I try to build pages in Divi loading pre-defined layouts, I get an error 500 in the path wp-admin.admin-ajax.php and I noticed that this error only occurs when Yoast SEO is enabled and in the tests I did, when I disable it, I can load the layout normally. I recorded a video to help better identify the problem. https://www.loom.com/share/51b52cf2dc1045e2bc2cb38e8e1b783b

In addition, analyzing the debug.log, I found the following message:
PHP Notice: register_rest_route was called incorrectly. The REST API route definition for yoast / v1 / get_head is missing a required permission_callback argument. For REST API routes that are public, use __return_true as the permission callback. Read how to debug WordPress for more information. (This message was added in version 5.5.0.) In /wordpress/core/5.5/wp-includes/functions.php on line 5225.

I have already contacted Elegant Theme and my host, made several attempts at diagnostics and resolutions such as deactivating plugins, updating themes, installing the jQuery Migrate Helper plugin and nothing worked. The error only disappears when Yoast SEO is disabled. Can someone help me?
==================

We are sorry to hear about the issues you are having. Thank you for providing a video that shows the problem.

We can see that you are already using Yoast SEO 14.8.1 and your WordPress 5.5. That’s very odd. Can you please perform a complete conflict check? The fastest way to do this is to deactivate other non-Yoast plugins and switch to a standard theme like Twenty Nineteen. 

Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.

Also, if you go to SEO-General-Features and scroll to the bottom and disable the Rest API, does the issue resolve?

We look forward to your response.

@thicoec2020 Regarding the ‘cURL error 28’ , this error is related to the use or Ryte. The Ryte check is a single call to the Ryte services. They, in turn, try to reach your website to see if it’s accessible / indexible by robots. If they see your website, this check passes. If you’re on a development / staging website, they probably can’t see your website and this health check will report an error.

The cause of these errors can lie anywhere on the route between your website and the Ryte servers.

• Your own website / server can have (security) protocols or even plugins or code in place that prevent this request from completing.
• The route over the internet from your website to Ryte can be broken somehow (extremely unlikely, but still).
• Some system in between your website and Ryte does not allow / process this call, maybe due to security reasons / because your website is on a blacklisted server.

While it’s not a nice error to see, it’s difficult to pinpoint why this happens. And it’s almost impossible for someone who is not the website owner / host to determine this.

Having said that, this is an error that does not influence your site rank in any way. If the error would say that your website can’t be found by search engines, that would be reason to investigate. You can read more in this article ( https://yoast.com/yoast-seo-ryte/ ) and there are even a few links to run this test manually.

Additionally, if you wish to disable the Ryte check we have instructions on how to do this here: https://kb.yoast.com/kb/disable-indexability-check/

@thicoec2020 Since the issue is generating a 500 error, that type of error will be logged on the server along with a more specific reason for the error.

You may not have access to the server error log where the details of the 500 error are located, but if you ask for this information from your hosting provider they should be able to provide it upon request.

We would recommend for you to check with your hosting provider and see whether they are able to review their log files for the server and provide more specific information for the 500 errors.

Can you also please confirm what version of PHP/SQL your site is using, and whether the environment also meets all of the plugin requirements listed here?: https://yoast.com/help/plugin-requirements/