vBulletin 3.x Parse error: syntax error, unexpected $end in /home/content......../forums/vbseo.php on line 1451

[verbs]

Could someone point me in the right direction? My website hasn't been changed or been touched by me in forever, and all of a sudden yesterday my site goes down and I get this message:

Parse error: syntax error, unexpected $end in /home/content/v/e/r/verbinsky/html/forums/vbseo.php on line 1451


Help would be greatly appreciated? I have VB SEO 3.3.

Looks

[Andrés Durán Hewitt]

Hello Matt,

Please try reuploading vbseo.php file to your forum root folder.

[verbs]

Hello Matt,

Please try reuploading vbseo.php file to your forum root folder.

I did that and it countered with another error:

Parse error: syntax error, unexpected $end in /home/content/v/e/r/verbinsky/html/forums/index.php on line 521

[Andrés Durán Hewitt]

It seems your site has been hacked. Please try to download vBulletin package from Members Area and re-upload via FTP all files.

Also re-upload all vBSEO files. Make sure you are using latest vBSEO version.

[verbs]

It seems your site has been hacked. Please try to download vBulletin package from Members Area and re-upload via FTP all files.

Also re-upload all vBSEO files. Make sure you are using latest vBSEO version.

I backed up my VBulletin and VBSEO files a little while ago, should I just go ahead and re-upload those files?

[Andrés Durán Hewitt]

I've seen this problem yesterday with another user from another support forum (he was using vB 4.0.3). What I did:

* I downloaded latest vB 4 version from members area (4.0.7)
* I upgraded the forum and vBSEO to latest version
* I applied these security tips:

Easy Security Tips for vBSEO customers

You can ensure you have been hacked by downloading for example 'forums/index.php' file; when you're going to edit it you'll be able to see a base64_decode at the top of the file.

Please try to follow my suggestions.

[verbs]

I've seen this problem yesterday with another user from another support forum (he was using vB 4.0.3). What I did:

* I downloaded latest vB 4 version from members area (4.0.7)
* I upgraded the forum and vBSEO to latest version
* I applied these security tips:

Easy Security Tips for vBSEO customers

You can ensure you have been hacked by downloading for example 'forums/index.php' file; when you're going to edit it you'll be able to see a base64_decode at the top of the file.

Please try to follow my suggestions.

Yeah, that's pretty much what happened......I checked.

I've been dealying upgrading to 4.0.x since I'm not terribly technically savvy myself.....I probably should go ahead and do this...I'm not terribly computer savvy though, so I'll have to probably pay someone at VBulletin.com to do this for me; is there any risk of applying my backed up files in the mean time until I upgrade my site (this I know how to do)?

[Andrés Durán Hewitt]

I would suggest you upgrading your vBulletin instance and also all of your other plugins. It could be possible you are using outdated plugins that have reached EOL.

Try first upgrading your forum to latest vB 3.8.x version , maybe upgrading your forum to vB 4 or uploading your backup will give you worst issues. Try to set up a test environment.

[verbs]

I would suggest you upgrading your vBulletin instance and also all of your other plugins. It could be possible you are using outdated plugins that have reached EOL.

Try first upgrading your forum to latest vB 3.8.x version .

My VBulletin is 3.8.4 I believe, it's my VBSEO that is 3.3. I do have a bunch of plugins as well.

[Andrés Durán Hewitt]

I've seen you are using a very old vBadvanced version (2.2.1). It's your decision to upgrade to vBulletin 4 or not. If you are planning to do it, so plan it well in advance .

[Brian Cummiskey]

I can't fully load your homepage. It looks like you are running our of memory or processing time on your server before a page can even fully render.

If you haven't changed anything, I would suggest contacting your host to see if they changed your php build/etc on your server, as that may be the cause.

[Brian Cummiskey]

Seems to be loading correctly now.

[Andrés Durán Hewitt]

Also loads fine for me. Please let us know if you solved the issue.

Best regards.