Closed jacobdgm closed 1 year ago
My guess is that OldCantus has some JS that sends off Ajax requests to fetch and display concordances (or melody concordances, in the case of #993). Someone is visiting cantusdatabase.org and the old JS script is cached, which is triggering a call to an Ajax API that no longer exists. Or something like this. So, I'm guessing we don't need to do anything about this, but it requires more investigation before we can make this conclusion.
When you go to a chant page (e.g. https://cantus.uwaterloo.ca/chant/693915), if you view network activity, clicking on "Display all concordances..." initiates a request to https://cantus.uwaterloo.ca/display-concordances/693915. I think we've found our answer - we don't need to implement this. Closing.
Similar to #993, I noticed a request to
/display-concordances/664335
. cantusdatabase.com/display-concordances/664335 causes a 404, whereas cantus.uwaterloo.ca gives us