adroofing08

Perfect! That did the trick, thank you so much!

Apologies for the quick update but as I’m looking through the table more I’ve come across a few more that seem to be from this plugin as well:

wpo_ips_semaphore_lock_attach_doc_to_email_* – 2,233 rows

Some of these also include reference to YITH Request a Quote. I would want to know if there’s any possible way for us to ensure these are removed after their processes are completed? In about a 10 minute span 15 of these rows were made and none removed.

Thanks again!

Hi Maybellyne,

Yes, I used that plugin as well as just doing a full deactivation conflict test on a stage site. It ended with Yoast and Twenty Twenty Four active only the the sitemap was still having the issue. It showed the same whitespace error with all other plugins deactivated.

Hi Maybellyne,

We are already on v22.8, the conflict test was done on that version. Google Search Console told us when the sitemap was last scanned with the error which was the 15th – I believe just after the v22.7 update.

I did some additional testing. The XML file does have a whitespace before it. After looking through Yoast’s documentation on it possibly being a conflict I ran a full conflict test.

I started deactivating smaller plugins first and the sitemap began to work. I quickly reactivated the plugins one by one and it stopped working. I narrowed it down to 3, disabled them all and the sitemap was still broken. After more testing with the initial group I came to the conclusion that none of them were causing it. They are currently all disabled on our stage site and the problem persists. The only plugins I left enabled for the test were Elementor, WooCommerce & Gravity Forms. I know GF had a previous conflict causing this issue and I was able to rule out that plugin.

I then isolated Elementor & WooCommerce and the problem persisted. This led me to the theme which I swapped to the WordPress default. After all that the issue still persists. Not sure why the sitemap started working halfway through the conflict test. I had been clearing the cache after each disabled plugin to ensure I wasn’t getting outdated results.

At least for us there seems to be no conflict with other plugins/themes. This issue began around May 15th, the same day we updated to Yoast 22.7. Reverting to 22.6 also did not work however. With all of this in mind I’m not sure what the issue could be. Any help with this additional info would be appreciated! ??

Hi Shameem,

I did think it may have something to do with the HPO system. We swapped to that about 3 weeks ago but this issue just cropped up without any updates.

From what I saw in the new DB structure there doesn’t seem to be an author other than the customer – is that correct?

Here are the reports:

• System Report
• Fatal Error Log

As for the conflict test, I went ahead and disabled all plugins on a dev site besides WooCommerce and a Login as User plugin to view it from the sale’s team account. The “Mine” does not appear.

Because there is no author column in the DB is there another way this could be tracked by who it was created by rather than by customer?

Hi Shahed,

We have access to view our server’s cron log. Currently it is turned off with nothing in the log.

Hi Shahed,

We’ve regenerated the feed and that does seem to work but it seems like every week it reverts back to the incorrect URL. I checked in the cron logs and there isn’t another job that would be running weekly. Do we need to just regenerate every single week when this happens or is there something else we can do?

To clarify, the file automatically regenerates daily, but the broken link only happens after the regeneration on Wednesday.