We are doing maintenance on a huge legacy system that was written over 10 years ago. It is all written procedurally with no concept of OOP. There are lots of includes and redirects all over the code. The problem is that it is extremely difficult to find where a specific event is calling a given cflocation.
Is there a way stop all cflocations from happening and instead create an error or something so we can find it? I was thinking it might be possible to add something to an onRequest method that might catch a cflocation and prevent it from working.