If I remember correctly, this has to do with an update to PHP on your server; it happened to us also.
I think the advise you'll get here, is to either 1) upgrade vBulletin, or 2) edit the indicated .php files at the line(s) indicated in the error messages and make the suggested replacements; that's what I did initially, before we then upgraded our version of vBulletin.
|