Natalya

Thank you for responding so quickly. WordPress version 5.6, the notification is displayed in the administrative panel on the Web Express plugin settings page. i am sending you two screenshots: a notification and the fact that this option is enabled in the Cash Enabler settings. This problem has not been observed before.

screenshots

Hi, @beerallica , see the solution here github

• This reply was modified 4 years, 2 months ago by Natalya.

@wpxpo Thank you so much for your support! I already left a review for 5 points earlier.

The problem is marked as solved, but it is not actually solved. Here is the same request to the plugin developer WebP Express – Error when creating of the site map

Alex Seidanis I changed the limits to 180000 bytes in the WebP plugin, but this will fly off when updating. I contacted the developers of Rank Math, but apparently they didn’t understand what the error was. They thought I had gaps in the sitemap. Write to them too, then they’ll pay attention when they see that I’m not the only one with a problem.

Hello, dear Rank Math! Yes, I read this help before contacting the forum. There’s another problem. Most likely, the map is too large (posts contain a lot of images), and the processing limit set by the WebP Express plugin is 60000 bytes. I increased the limit in the WebP Express plugin to 180,000 bytes, but this is not quite correct. Please, can you tell me why the limits of WebP Express affect the creation of the site map by the Rank Math plugin?

Maybe this is important, I see this message in front of the map.
<!-- Alter HTML was skipped because the HTML is too big to process! (limit is set to 600000 bytes) -->

Maybe this is important, I see this message in front of the map.
<!-- Alter HTML was skipped because the HTML is too big to process! (limit is set to 600000 bytes) -->

“@type”: “Article” for some reason only works on pages, and now only “@type”: “BlogPosting” works in single posts.

Hi! I have the same problem too.

Yes, first of all I turned to this page, but there is nothing about adaptive width, only fixed size and user fixed. Yandex itself generates code with a width of null and a height of 0 when it selects an adaptive size. I will wait for their response.

I already created a static page to show you how the code works, and I realized that I was wrong. Before that, I tested with VW width and copied this code again. In General, I’m confused. I’m sorry, the code with the null width doesn’t really work. I wrote to Yandex support with a question about responsive width. I hope they will tell me what can be done. Thank you for your time.

The fact is that the Yandex code works without problems if we implement it on a regular site without the AMP plugin or with another plugin. The only problem is that it is the plugin that removes it because it adheres to certain rules. But Yandex doesn’t violate the display rules, it just implements dimensions automatically. In other words, when we specify width=”null” height=”0″, it will automatically set the size of this ad block that is currently available for display. If you made an exception for Yandex, it would be great!

The ad has been updated and unfortunately, the size of 100vw is displayed incorrectly. And Yandex automatically adds “layout=fixed”to the code.

Good! I will try.