Jan 8th, 2012, 12:40 PM
Hmm.. curious!
First off, don't worry: this is purely a house-keeping test, so it doesn't point to anything sinister.
Secondly, do you have error reporting turned up high on your second installation? i.e. do you have the $g_default_error_reporting variable defined in your config.php file? If so, could you comment it out temporarily then re-test?
It sounds like maybe there's some invalid info being returned from the server. A minor warning or notice may well mess up the info for the JS. I *should* work fine, but that's my best guess.
What I'll do on my end is update the module to provide a better error message in case of invalid info returned by the server. Definitely something that's needed!
- Ben
First off, don't worry: this is purely a house-keeping test, so it doesn't point to anything sinister.
Secondly, do you have error reporting turned up high on your second installation? i.e. do you have the $g_default_error_reporting variable defined in your config.php file? If so, could you comment it out temporarily then re-test?
It sounds like maybe there's some invalid info being returned from the server. A minor warning or notice may well mess up the info for the JS. I *should* work fine, but that's my best guess.
What I'll do on my end is update the module to provide a better error message in case of invalid info returned by the server. Definitely something that's needed!
- Ben