URL collision detection

This is great. My only problem is that I have a few warnings that arise which I can safely ignore, and don’t want to trigger a panic. Is there any way of “having my cake and eating it too”?

As it’s not directly related, I opened a different topic, but here’s an explanation of the warning I’m currently getting: Warning triggered by "File.TranslationBaseName" in "where" query