3.7.3 config.php file type NEW

[Stevo]

According to the upgrade instructions shipped with 3.7.3 there is a file config.php.new. in the includes folder.

However the file in the includes folder is just config.php and not config.php.new but when you look at the properties it says "File type NEW" and when you add the details and save it still says file type "NEW" and not a "php" file.

So I'm worried that if I load it it will not be recognised as a php file.

In any event the instructions shipped with 3.7.3 are not consistent with the contents of the 3.7.3 product and this confusion/inconsistency should be remedied.

[Lynne]

I think it must be some setting on your computer which has it showing the way it is. I just downloaded 3.7.3 this morning and the file was called config.php.new. What OS are you running?

[Diggazz]

Just upload it and in your ftp client use the rename command and delete the .NEW


With the .NEW extension the name becomes config.php without the .new extension the name is just config

Hope this explains it a bit

[SNN]

Just upload it and in your ftp client use the rename command and delete the .NEW


With the .NEW extension the name becomes config.php without the .new extension the name is just config

Hope this explains it a bit
Do NOT do this unless you want to reconfigure the config.php file.
Just ignore the config.php.new and remove it from your new vBulletin download. If this were a major release (3.8+) then you might not want to ignore it, but besides that, in minor versions it is not needed to upgrade.

[n.sinha.p]

It's just the windows settings that is playing with you. To resolve, follow these:


Open any folder or explorer window
Go to "Tools" > "Folder Options..."
Click on "View" tab
Uncheck the checkbox against "Hide extensions for known file types"
Click "OK" & refresh the folder.

Now you would be able to see config.php.new file. Remove .new from extension and play with it as you like.:)

[Diggazz]

Do NOT do this unless you want to reconfigure the config.php file.
Just ignore the config.php.new and remove it from your new vBulletin download. If this were a major release (3.8+) then you might not want to ignore it, but besides that, in minor versions it is not needed to upgrade.

This is incorrect you should always replace all files unless its a PL, its what the instructions tell you to do

You stated you filled out the info then just do as i said in my previous post

[Zachery]

This is incorrect you should always replace all files unless its a PL, its what the instructions tell you to do

You stated you filled out the info then just do as i said in my previous post
Yes, all files, of which there is no config.php file, there is however a config.php.new.

I'll see what I can do about making sure the update doc included refrences this.

[Floris]

The config.php file already on the server (if you are upgrading) has your database details.

Since you always make a backup prior to upgrading, you can replace the config.php with config.php(.new) from the latest version. And write over the variable names from the backed up config.php.

Just uploading an unedited config.php will result in the upgrade not working of course since it is missing the specifics such as table prefix (if set) and the database details.

[Stevo]

Thanks guys/gals for all the help. You are the best!!!!

I just did the upgrade to 3.7.3 and it went smooth as silk :D

Really cool thank you vB :)

[Floris]

Glad to have helped. Enjoy your new version!