I did the complete upgrade (3.6.7 to 3.6.7PL1). My 3.6.7 was using php3, the upgrade uses php. My admin link calls .php3, bringing up the old admincp. I changed the link to call the newer .php file. The problem is, I have no patience to rename all the files from php3 to php, and I was not provided an option to upgrade using php3. What to I do?
Here are the complete instructions to change to .php from .php3:
1. Download the .php version of the vB zip file.
2. Upload ALL the files, except the images and install.php. Make sure you upload these iin ASCII fo
rmat and overwrite the ones on the server.
3. Make sure you have uploaded the install/*.xml files frok the .php version you downloaded. Then run install/finalupgrade.php and run through the steps.
4. If you have any custom template., you will need to either revert these templates or manually change any references to .'php3' to '.php'. You can also use the Help 'Find and Replace in Templates' feature under 'Search in Templates' but be very careful with this option.
Steve Machol, vBulletin Customer Support Manager
"Have Copy, Will Paste" (when appropriate)
Please do not email or PM me for vBulletin support. I will be more than glad to answer your questions on the vB Forums and in the support system.
Just remember that what happens in localhost, stays in localhost.
Thanks Steve. I did try to simply change the footer links in the forum for admin, which appears to work for now. I think what I did was change the link to point to the newer php file while in the 3.6.7 cp., which, for obvious reasons didn't work. So this time I did the same from the PL1 admin and it seems to be just fine, calling on the appropriate php files now. I'm guessing this is a workable solution.
I ran my rss update feed and it worked. However, I tried it one more time a few moments ago and received the following error:
Fatal error: Cannot redeclare construct_icons() (previously declared in /usr/local/apache2/htdocs/bulletinboard/includes/functions_newpost.php3:21) in /usr/local/apache2/htdocs/bulletinboard/includes/functions_newpost.php on line 138
It would appear that the older newpost.php3 is being called up again, though as I previously mentioned, it worked fine right after the upgrade. Anyway, one of the cleanup chores I'm looking at now are the duplicate files (the new php and the old php3).
The 'fix' I identified in the above reply seems to function. The rss error problem hasn't really gone away, however, the rss feeds are working. go figure. I think that sense it is working, I won't attempt any changes, fixes, etc. Thanks.
Reply With Quote
Bookmarks