Hi, and yeah, that's fair and a good idea. Sorry, this fell by the wayside. A more experienced programmer looked at it, couldn't figure it out (it's an older course, so can be tougher to maintain), and I did spend some time on it, and couldn't figure it out.
There were plans to move this course over to a newer platform, so the issue was closed, but that's been stalled and won't happen for a while.
I'll re-open the issue, will take another crack at it, and will if it can't be fixed properly will likely put in a note in 4.14.
I have just now put a note at the top of this forum topic, too.
Thanks for the suggestion!
update: likely figured out the issue, but it's tricky to fix. Will record the likely problem, but due to the fact it could break the entire course, am not going to fix for now. Will rely on the workaround at the top of the challenge, and will try to deploy a mention of this in the challenge, too! (course hasn't been deployed for a while, so that may take a bit of time as well)