"File does not contain expected contents" - How to fix?

[mark.hs]

I recently upgraded from 5.3.2 to 5.4. After the upgrade I went to Diagnostics > Suspect File Versions. A few files (examples: fcm.php and fcmqueue.php) showed as still being v 5.3.2. I manually uploaded the flagged files from the install package to my server and then ran the upgrade one more time. After I was done I went back to the diagnostics screen and now the files that once said wrong version now say "File does not contain expected contents". I opened each file and the code looks normal.

Any idea how to fix this or what might be going on?

[Wayne Luke]

To remove this error, you need to replace the files with the ones found in a clean download for your version and license. If you use files from another version, they will not match. If you use the files from another license, they will not match. The version number and license ID for each and every file should be listed at the top. If the md5_sums_vbulletin.php file in /core/includes is out of date, your files will not match.

[mark.hs]

Wayne,
License Number and Version number are a perfect match on all files which say "file does not contain expected contents"

I opened md5_sums_vbulletin.php and it also has the correct version and license number. You said if this file is "out of date", your files will not match. Is there something I need to do to update this file specifically? Maybe this file has outdated info, is there a way to update it?

[Wayne Luke]

It should be updated every time you upload a new version of vBulletin files. You would have to make sure the new files actually overwrite the old ones. The modified date should be updated if they were updated.

[mark.hs]

I think this is a good old fashioned false positive. The files are all correct, the contents are all correct. I've seen posts from v4 users who had the same issues, if they uploaded a few files manually after the upgrade, the checksums do not match and the files are reported as not containing expected content. Hopefully this will go away with the next upgrade.

Mark

[Mark.B]

Download a fresh copy of the 5.4.0 package from the members area. Unzip it and upload ALL the files to the server, making sure they overwrite what is already there. Then run the diagnostic again.

[mark.hs]

Mark,
Downloading a fresh copy, overwriting everything did the trick. The files are no longer being listed with errors. Thank you for the help.