vB4.2.3 config.php
 

Is there *not* supposed to be a forum/includes/config.php file included with vB4.2.3? Was looking through the 'upload' folder and didn't see one....

It's named config.php.new, I think so that it won't overwrite an existing config.php.

One reminder though... if you're on lets say 4.1.2 or for example a slightly older version of vBulletin please rename config.php.new to config.php and copy/hand key in the correct details never just leave the existing config.php.new and I don't care what anyone else says simply rename it then key in the details to ensure you have a 100% updated config.php file at the time of your upgrade = on par.

I've seen issues occur from using an older config file in the past, it may or may not happen to you it depends on how vast a difference between versions exist when you actually go to upgrade.

nope it's not in there at all

also any idea what max php version 4.2.2PL4 will work with?

after going through backup d/b, ftping 4.2.3 i went to run upgrade script and get an error message that i have 5.3.28
so... i go re-ftp 4.2.2PL4 files up overwriting everything, and get my forum going again and at the same time send my host a query about when they plan to upgrade.... a bit later i get a reply from them that I can CHOOSE my php version in my cPanel *banged head on keyboard... i forgot allllll about that it's been so long since THAT was necessary...
anyway, I'm going to try redoing everything in the morning but was going to change my php version to the one 4.2.3 needs if it won't destroy 4.2.2PL4....

--------------- Added [DATE]1435551277[/DATE] at [TIME]1435551277[/TIME] ---------------

oh Superman... I ALWAYS use the new config file AFTER I upgrade (I edit it before I upload it)
that's why i was asking about it being in 4.2.3 there is NO config.php.new file in the package I downloaded............

- Then you sir, are one of the few and far between that had a corrupt download directly from vbulletin.com... sometimes the vBulletin.zip downloads are not 100% complete and or missing files in the zip its rare but I've seen it happen first hand myself this one upgrade this one time lets just say we all laughed when we realized! Now with all that being said, simply re-download your 4.2.3.zip from vbulletin.com members area - once you extract the zip it should be config.php.new in the /includes/ folder.
- You should be on at least php 5.4 if running 4.2.3 imo.
- Some servers you can specify via .htaccess as well if setup to do so.

Edit: Ahh good then, glad to hear it and see my note above regarding corrupt downloads from vbulletin.com its rare but still happens from time to time, I literally had a client send the .zip last week it would not work he had to re-download again before we could push his upgrade through. *Also I downloaded 4.2.3 a day or so back and I just checked and can confirm config.php.new is in fact in /includes/ so it was a corrupt download on your end imo.

Thanks for the info, I downloaded it a week back and just now getting around to doing the upgrade.

I still need to know if 4.2.2PL4 will work with php5.4 so i can set the version in my cPanel at host prior to running the upgrade which won't be until tomorrow. I wanted to go ahead and at least do that so my 'overnight' members can post till I disable in the morning

4.2.2 will work with php5.4 yes, you may or may not need to include the variables in the top of the config.php to mask errors sec let me find it... ahh here it is see Paul's post, #2 for the values to add at the top of your config.php file IF errors show etc.

http://www.vbulletin.com/forum/forum...-been-released

urp
I just downloaded the zip again, extracted it and there is no config.php.new in there!
see attached png of the file names in the includes folder
https://vborg.vbsupport.ru/external/2015/06/1.png

--------------- Added [DATE]1435554836[/DATE] at [TIME]1435554836[/TIME] ---------------

Thanks I see what to add, but where the hell do I add it in the file? any particular line number?

Try a different browser, here is the config for 4.2.3

It may in fact be missing, but that image shows the files sorted by type with all the php files together, and sorted that way, the config.php.new would be under ".new" not ".php".