Fixed IndexNow: Avoid sending requests when user is just moving threads from one node to another

[Chromaniac]

Affected version

2.3 Beta 6

So, I have been having an issue where posts from one user were not marking threads as unread in some nodes. I couldn’t find any reason for this behaviour, so I decided to create a new node and migrate all threads from old node to new one. This appears to have solved the problem for now.

But this did cause another problem. Server error log ended up with tons of entries related to IndexNow. I imagine that all threads moved from old node to new one created IndexNow requests which seems pointless as thread URLs and content remains same. The only thing changed was probably the meta data which can be updated in time by search engines.



Just posting this as a FYI as I am not sure what activities generate IndexNow hit. Devs might consider what can be done to avoid such a scenario.

 

[XF Bug Bot]

Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.3.0 Beta 8).

Change log:

Don't queue up IndexNow requests when moving a thread

There may be a delay before changes are rolled out to the XenForo Community.