This is best practice due to _ naming convention usage.

I got that a few times. I think this happens if your code causes the output text to contain any special characters, like {} <> etc. Can't have anyone accidentally or intentionally injecting JS into the site and all. It worked fine once I fixed the code.

I just get: there was a problem with the server response every time.