Sorry, should have said the function causing the error seems to be random (it will work sometimes). I don't think it is a cache problems with the browser as it still throws an error even if you force a reload from the server. | [reply] |
The browser doesn't know about modules :)
check, the module, is maybe being cached by the server (mod_perl, and maybe differently by each child).
| [reply] |
Sorry, your suggestions are above me. How would I check if mod_perl is caching the module. If it is a cache problem, why is the routine that causes the error keep changing?
Sometimes it is one, other times it is four, or when it fancies it six.
| [reply] |