4.1.9 has dozens of "unexpected contents'
Collapse
X
-
Ah... very good - it's actually Forums Home Page Options which is close enough to be impressive It says "index" although I'm not sure what the setting should be just to keep the forums/ URL and not forums/index.php that I've had for years.Comment
-
The issue is that in vB4, we expect this to be forum.php.
Your index.php file is not the forum.php file. Rename your current forum.php to index.php and remove the current index file you have. Should sort that issue.Comment
-
Could my FTP software be the problem? Anything is possible. But considering I'm far from the only one experiencing the same error message and it occurs ONLY with the latest builds of vBulletin and not previous versions I've uploaded, suggests something here may have changed. All I want to do is help solve this issue and provide reasonable notice to customers about common issues we are encountering here so that we can help resolve problems in a more efficient fashion.
I have no idea why you fail to be able to just have a polite conversation with customers about how to deal with issues that crop up from time to time and instead resort to some childish ritual of attempting to prove how you might be technically correct. Can we just dispense with this attitude already?Comment
-
Zachery - thanks. The issue for me is that I've had that URL for the past 10 years with vBulletin. This sorts things out and seems to work consistently. I'm assuming that I should keep the entry the same and just rename the file. Again, thanks for the help as always.Comment
-
Maybe we should have some sort of note re index.php, forum.php above the Suspect File Versions results?
or maybe change the wording to something more like
File not recognized as part of vBulletin, if you have manually added this file this warning is normal
File does not contain expected contents, if you have manually edited this file then this warning is normal.Comment
-
Actually, even on an upgrade, that setting will change itself to forum. The only way it changes is if someone edits it.Comment
-
Maybe we should have some sort of note re index.php, forum.php above the Suspect File Versions results?
or maybe change the wording to something more like
File not recognized as part of vBulletin, if you have manually added this file this warning is normal
File does not contain expected contents, if you have manually edited this file then this warning is normal.
As usual, thanks again for being so quick with a response and attempting to help solve the issues. Seriously, it's by far the best part of this company and I'm only sorry to have to see you guys put in so much more work than is necessary.Comment
-
Yes, of course .....
Do a search yourself for "unexpected contents" and you'll also find someone who says that a lot of sites are tripping up... and the result is the same "unexpected contents" error.
As already pointed out in this thread, that refers to a specific issue fixed last month - but then I think you already knew that.
I have no idea why you fail to be able to just have a polite conversation with customers about how to deal with issues that crop up from time to time and instead resort to some childish ritual of attempting to prove how you might be technically correct.
Let me remind you of your "polite" conversation at the start of this thread.
I figured out the problem. As is 100% typical, it's once again a vBSI major fail.
Can we just dispense with this attitude already?Baby, I was born this wayComment
-
As already pointed out in this thread, that refers to a specific issue fixed last month - but then I think you already knew that.
I'm going to make you feel the same way a customer feels -- search the forums. I've already described this major fail in the past several times but it hasn't been remedied. You've also got more than enough clues in this thread to figure it out. In fact, I'd say it's so obvious and staring you in the face. But you've spent more time denigrating a customer than actually trying honestly and diligently why an experienced vBulletin customer had problems with an upgrade and just trying to remedy that problem. This is just par for this course. Have a nice day.Comment
-
slinky, paul is correct on the error. It is not the same as one blank index.html file. This system (to check files) was added (at my request) to warn you that some files may not be correct and may cause a problem if you try to upgrade. The error you're seeing is telling you those files do not match the md5 sums that were generated when they were downloaded. You can try reuploading them, or you can check them manually to ensure they're okay. Any small change to those files, extra white space, odd line break, will cause the md5 check to fail. It must be 100% the same as it was generated for your zip file. If you want, you can easily ignore the error and continue the upgrade.Comment
-
None of this is documented - and it is a standard upgrade. The current upgrade instructions in the read me tells you to write over all the files that Zachery told me to change. In addition, if you set up the renaming of files as per Zachery's instructions, you'll also get error messages in the diagnostics checks that the files aren't authentic even though they are. The result is that if one thing doesn't confuse you, the other eventually will if you verify. You'll screw this up every time you upgrade - but this time it was the diagnostic check that threw me off too. After plodding through the forums, I also discovered that:
(a) It was actually myself who ended up writing the instructions for the benefit of everyone here on how to maintain the above for the release of 4.0.garbage and released them here which many used
(b) It nailed me on another upgrade and I forgot about having to do this so I raised a great deal of attention as to how important it was to include this in the documentation. I also raised a great deal of attention as to why nobody bothered doing this the first time.
(c) After several months have passed, this standard upgrade procedure was STILL NOT included in the manual. What would it have taken - 5 minutes???
I rarely ever need notes for doing standard product upgrades that are CORE. I don't like modifying core files for the same reason everyone else doesn't want to hack core code. I DO have notes for when I have to modify plugins and other items that are NOT core. The Read Me file should be updated more than once every 2 years. And I never planned on upgrading vBulletin ever again after 4.1.5p1 - but the defective design here forced me to upgrade yet again or I would lose Facebook Connect.
In addition, as punchbowl said above, wouldn't it have been wiste at some point to fix the "warning" so those of us who use the Suite as a Forum Only (because the rest is still junk) so that we can set the preferences differently? This is CORE. And my core upgrade, by its nature, STILL results in an error in the Suite diagnostics and will leave you wondering what is wrong now.
I have a million things I need to do every day. The last thing I have to do is write Read Me files for vBulletin. I've spent a TON of time "whining" about other graphics that caused thousands errors in my logs because I realized that nobody here at VBSI bothered to fix any of the reports in the JIRA. After I raised a ruckus about it during the last time, most of them finally got done over a year after 4.0.G was released. I don't get paid for these things that any fifth grader could do but fails to get done here. The goal here is to sell us crap we don't need, not deal with stuff they already got customer money for in advance. This is not GPL freeware.
PS - I snipped the hellacious upgrade those of us who relied upon VBSI's statement that the style system was done in VB 4.1. They keep forcing me to do upgrades due to defective design. So to answer your point: my life would have been a lot "happier" if I never heard of VB 4, didn't rely upon the failed promises by VBSI here, and had kept everything on Vb 3.8.x -- just like Internet Brands did with their sites.Last edited by slinky; Wed 4 Jan '12, 2:20pm.Comment
-
slinky, paul is correct on the error. It is not the same as one blank index.html file. This system (to check files) was added (at my request) to warn you that some files may not be correct and may cause a problem if you try to upgrade. The error you're seeing is telling you those files do not match the md5 sums that were generated when they were downloaded. You can try reuploading them, or you can check them manually to ensure they're okay. Any small change to those files, extra white space, odd line break, will cause the md5 check to fail. It must be 100% the same as it was generated for your zip file. If you want, you can easily ignore the error and continue the upgrade.
Now with regard to the "MD5 error" due to changes to those files - I didn't change anything. I uploaded the files using two different clients and only that folder failed with all the JS. I've never had these errors before and no other software has them either. Uploading prior versions of vBulletin did not yield these errors either. Hence I leave you with that but wonder why others are encountering similar messages on perhaps different files.
What's aggravating is to see the major contrast between well run software companies and the mismanagement here in production and all of it is tied into the same thing. The developer releases the version and we get:
(a) updated read me file which includes the *complete* process to install and upgrade
(b) a link to a manual that will have the same, perhaps even more comprehensive
(c) release notes which may include common issues that have been encountered by users for licensees to be aware of during install or at least some announcement in the forum that lists all the common issues encountered.
This is organization. This is what I'm used to. The complaint about having to search the forums for stuff like this has been going on since the dawn of vB 4.0. And be biggest joke of all is that you'll be releasing VB 5 before you even have documentation done for VB 4 - because it has been deemed unnecessary for a long time now and not a priority.
EDIT: Zachery - I'm probably more agitated with VB for the reasons you read about concerning the failure to document and address non-errors in the upgrade procedure once in two years. This isn't your job. Making sure this gets done is the job of the persons leading this project who never make their presence known here.Last edited by slinky; Wed 4 Jan '12, 2:22pm.Comment
Related Topics
Collapse
-
by chris76423I recently purchased vBulletin and installed it.
When i run Diagnostics -> Suspect File Versions i get a mismatch on those 2 files:
LoggerConfigurationAdapterXML.php File...-
Channel: Support Issues & Questions
-
Comment