everytime i try to upgrade using the upgrade.php
it goes to upgrade_370b2 ( version 3.7.0 Beta 2 )
and not to 3.7.2
if i try puting the finalupgrade.php link
it says : Your vBulletin (3.6.8) does not appear to be running the version that was downloaded (3.7.2).
This generally means your upgrade was not successful. Please ensure that you have uploaded the latest files and click here to try again.
If you are sure you wish to continue with this part of the upgrade, click here.
i've copied the 3.7.2 files twice already , copied all of them
when preparing to install i followed this : Updating the vBulletin Scripts on Your Web Server
Mike Pepper <pepper at w3pg dot com>May 27th '07, 09:44amAlternative (3rd) method to shorten server downtime.
Upload to a temporary copy of your vB production directory, then when the upload is complete, switch the directories and continue from there.
The actual upload, after you've prepared the files, is the longest part of the server downtime. The objective with this method is to complete the upload of new files before you have to take down ("turn off") your forums.
Here are the steps:
1. Complete all file preparation as per the previous step, "Preparing the vBulletin files for Upload".
Then, before you upload any files go to step 2 here.
2. On your production server, COPY the entire vBulletin directory (or "folder") structure to another temporary directory. Be sure to preserve all attributes of ownership, permissions, etc.
For example, if your vB forums are in a directory called "vbbs", then you might copy it to one called "vbbsupdate". Your forums in "vbbs" will keep running for now.
On *ix at the command line use (e.g.)
"cp -pr vbbs vbbsupdate"
3. Upload your prepared vB update files to your temporary "vbbsupdate" directory as described above in the "overwrite" method.
REPEAT: upload to your temporary directory; in this example the one called, "vbbsupdate".
4. Wait till the wee hours of the morning to minimize impact on your traffic.
5. Turn off your forums in the admin CP.
6. Back up your database so that the backup is as fresh as possible.
7. Switch the directories by first renaming your (e.g.) "vbbs" directory to "vbbsold" and then renaming your "vbbsupdate" directory to "vbbs" (changing the names to match your setup, of course).
8. Run the update script as described in the next step, "Running the vBulletin Upgrade Script".
Good luck. The few times that I've done it, it runs pretty smoothly.
although i didn't use the :
On *ix at the command line use (e.g.)
"cp -pr vbbs vbbsupdate"
i copied the forum directory to my pc renamed it and then copied it back to the server
it goes to upgrade_370b2 ( version 3.7.0 Beta 2 )
and not to 3.7.2
if i try puting the finalupgrade.php link
it says : Your vBulletin (3.6.8) does not appear to be running the version that was downloaded (3.7.2).
This generally means your upgrade was not successful. Please ensure that you have uploaded the latest files and click here to try again.
If you are sure you wish to continue with this part of the upgrade, click here.
i've copied the 3.7.2 files twice already , copied all of them
when preparing to install i followed this : Updating the vBulletin Scripts on Your Web Server
Mike Pepper <pepper at w3pg dot com>May 27th '07, 09:44amAlternative (3rd) method to shorten server downtime.
Upload to a temporary copy of your vB production directory, then when the upload is complete, switch the directories and continue from there.
The actual upload, after you've prepared the files, is the longest part of the server downtime. The objective with this method is to complete the upload of new files before you have to take down ("turn off") your forums.
Here are the steps:
1. Complete all file preparation as per the previous step, "Preparing the vBulletin files for Upload".
Then, before you upload any files go to step 2 here.
2. On your production server, COPY the entire vBulletin directory (or "folder") structure to another temporary directory. Be sure to preserve all attributes of ownership, permissions, etc.
For example, if your vB forums are in a directory called "vbbs", then you might copy it to one called "vbbsupdate". Your forums in "vbbs" will keep running for now.
On *ix at the command line use (e.g.)
"cp -pr vbbs vbbsupdate"
3. Upload your prepared vB update files to your temporary "vbbsupdate" directory as described above in the "overwrite" method.
REPEAT: upload to your temporary directory; in this example the one called, "vbbsupdate".
4. Wait till the wee hours of the morning to minimize impact on your traffic.
5. Turn off your forums in the admin CP.
6. Back up your database so that the backup is as fresh as possible.
7. Switch the directories by first renaming your (e.g.) "vbbs" directory to "vbbsold" and then renaming your "vbbsupdate" directory to "vbbs" (changing the names to match your setup, of course).
8. Run the update script as described in the next step, "Running the vBulletin Upgrade Script".
Good luck. The few times that I've done it, it runs pretty smoothly.
although i didn't use the :
On *ix at the command line use (e.g.)
"cp -pr vbbs vbbsupdate"
i copied the forum directory to my pc renamed it and then copied it back to the server
Comment