Paddy Landau

Thank you, @georgiganchev

I’ll do that.

@auctollo — I look forward to it!

Thank you for your advice. I’ll contact them.

Thank you for your reply and suggestion, @kybernetikservices .

I have done as you suggested, and identified the culprit: Ultimate Membership Pro (UMP). When I disable UMP, the sitemap works correctly.

Unfortunately, I need UMP for the website.

What can you suggest that I do next, please? I am keen to use your plugin, but I can’t get rid of UMP.

Thank you

That works, thank you!

Can you mention your php and wordpress versions?

Sorry, I should have thought to do so.

• WordPress version 6.6
• PHP version 8.3.9
• MySQL version 8.0.36-28

Thank you, that makes it clear.

Thank you, @zougou

@wpmudevsupport11 — Thank you for this. I would like to apply this to my own website. I’m not a programmer, so I’m rather puzzled as to where to place the code that you have indicated.

Can you tell me where to place it, please? Or, what keywords to use to look it up?

(It would be nice if Forminator had a built-in option to block both links and HTML code in text areas!)

Thank you

Thank you, @pdosev

@delyandelov — Perfect! That worked on all of my sites, thank you.

Thank you, @pdosev

I’ve implemented my suggestion in my .htaccess files, which should solve that problem.

This is a low-priority request, I would imagine.

@georgiganchev — Thank you, Georgi

I appreciate all the time and effort that you and your team put into the plugin.

@plamenm — Thank you. I do understand that this is a warning, but if the program is receiving an invalid argument, it could mean invalid execution.

I shall disregard this, but it’s the only the thing on any of my entire sites (WordPress, using various themes) that ever create php_errorlog. So, it’s a bit weird.

@georgiganchev — Thanks for your reply, Georgi.

This is really interesting.

Looking at the files in /wp-content/themes/Divi, I see that there was an automatic update 1:37:09 a.m.

The error was reported at 1:37:10 a.m.

So, the security plugin must have run at the same time as, or immediately after, the updates, indirectly leading to this error.

I hope that this answers your question.

By the way, the error is reported in php_errorlog in the account’s root folder.

• This reply was modified 2 years, 10 months ago by Paddy Landau.