Josivandro Avelar

Apparently yes, but I had to disable wp-cron and create a custom cron job to control the spikes.

• This reply was modified 1 year, 4 months ago by Josivandro Avelar.

I did the steps in the video. The response it returns is the same as what appears in the demo.

https://imgur.com/gallery/kQ4cv8z

• This reply was modified 1 year, 4 months ago by Josivandro Avelar.

I submitted the requested information to the form.

The problem is with the plugin installed; I tested in maintenance mode and this problem appeared from the beginning.

I was able to solve the problem through this workaround. Thank you for your attention!

I solved the problem. It was code in the child theme’s functions.php file that was conflicting with Elementor and another plugin. This was detected via the Health Check & Troubleshooting plugin, where I noticed that the parent theme was able to open Elementor, and the child theme could not.

I adjusted the child theme’s functions.php code and Elementor worked again.

I checked the situation here and that was it. What I did was replace the separator with a hyphen (-), which is already accepted in the validator.

From this simple change that was made in Yoast SEO, the feed returned to feed Google News and in this way, the problem is solved.

Thank you for your help!

I managed to solve the problem by adjusting the canonical tag and now the post titles have returned to appear normally from the next ones and the ones that are updated.

In fact, the one in the header conflicted with a canonical tag that already existed, which has already been fixed.

More or less that. In this case, there is a parked domain, which is josivandroavelar.com (without br), so there are two distinct domains:

https://josivandroavelar.com.br/post-1
https://josivandroavelar.com/post-1

And the canonical URL, in this case, is josivandroavelar.com.br, so the results for josivandroavelar.com, in a way, don’t figure in the search – at least all the results pointed to a canonical URL.

Yes, it has the same content.

The canonical property code was manually installed in the child theme’s header file, without using a plugin. This is because the site has a second parked domain that currently redirects to this site. At the moment I disabled this redirect at least on the other pages of the site and it may be that the error is there. Maybe he could be giving some kind of conflict that ends up giving rise to this problem.

I did a new test and the error keeps happening.

Web stories are only displayed if the function to disable non-essential JavaScript is disabled, and it continues even after the update.

The errors that prevent the display are detailed here: https://imgur.com/TWPIiRb

Yes, I tested it by deactivating all other plugins and activating through combinations. The problem happens when you activate the AMP plugin, plus the function of deferring non-essential JavaScript. When this function is disabled, web stories with images from third parties appear normally.

The plugin team itself tested and found the problem, as can be seen here.

I sent the data through the form and did the test by the Health Check plugin. When doing the test, I arrived at the following diagnosis that, at the end of the day, is at the same time as solving the problem, a discovery of incompatibility between plugins that reflects in Web Stories and that may happen in other plugins.

What affects the display of external images in Web Stories is an incompatibility between AMP and Jetpack Boost. If you disable one or the other, these images are displayed. But if both are activated at the same time, these images are not displayed, only the images from the website (uploads).

Thus, it would not be a problem specific to web stories. I will pass on the information about this incompatibility in another topic, in the Jetpack Boost plugin.

I reopened the plugin page today to carry out the process and I verified that the problem was solved and the page already opens normally.

I removed protection to enable debugging.

I tried the full width mode, but it didn’t work; the website continues to show margins on the home page.

The site theme is Versal, but here I use a child theme on it.