Maksim Strekalovskikh

@arnaudbroes

Thank you for your prompt response!

I understand you, we are all not perfect people and no one is immune from mistakes and omissions. That’s okay. I’m always happy to help here ??

About manual change bugfix in the code. No problem!

I checked the manual bugfix on a test copy of the site in advance – there are no problems, everything was applied as required. Transferred a manual bugfix to a production site – everything is also okay.

I checked it through the sitemap verification tool in “Yandex Webmaster” – it didn’t find any problems, and here the problem can be said to be solved.

I sent the sitemap to Yandex for rechecking, we’ll wait for Yandex to remove this issue from the problems, I’m sure that it will be no problem.

Thank you very much for your help again and interest in this problem, my friend! ??

I’ll also wait for the next update, where the bugfix will be finally applied.

And I’m sorry that I had to bother you again about this problem.

Have a nice day!

Regards,
Maksim Strekalovskikh

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

Hello, @arnaudbroes!

I saw update 4.2.7.1, which contains a bug fix, and immediately updated the plugin. Thank you for the update.

But, it seems that the changes in the sitemap didn’t happen after the update. Namespace has remained with ?https?.

In the plugin code through ?Trac?, I see a change in the code in the following path – /all-in-one-seo-pack/trunk/app/Common/Views/sitemap/xsl/default.php

I also see that there is an /all-in-one-seo-pack/trunk/app/Common/Views/sitemap/xml directory and there is also a default.php file. But then I noticed that there were no changes and the line with the namespace remained ?https?.

Maybe I’m doing something wrong? Maybe I set settings incorrectly? Or is it still a mistake?

I will be glad for any answer.

I also leave a link to the problem sitemap itself, if needed – https://xn—-dtbnd1aigbg4k.xn--p1ai/post-sitemap.xml

If you need any additional information, I am ready to provide.

Regards,
Maksim Strekalovskikh

Hello, @arnaudbroes!

Thank you for your interest and confirmation of this issue.

I’ll be waiting for version 4.2.7.