We are not experiencing that issue in any of our clients' websites. It must necessarily be some other add-on you have installed. Maybe you installed an add-on not working correctly with vB 3.7, I have seen that error in other clients' boards when they were using vB 3.6 and 3.5 add-ons in vB 3.7; it is caused by a code change in vB occurred in one of the 3.7 Beta releases. Needless to ask, but just in case: are you running 3.7 Gold?
Let us know.
|