problems duplicating for upgade
 

hi all, ive recently looked into upgrade our board from 3.7.1 to 4.2.3 i duplicated it on the dev site and and duplicate database, all works ok until i get to a certain stage of the upgrade and then it throws up a error while upgrading referring to the original site, is this because thats the url where the licence points?

no one can access except me as ive .htaccess etc, even if i try and upgrade on my offline server i get another error much earlier

i only want to do this incase of problems and would rather not mess up our board as theres 377,000 posts lol

any help appreciated as always thanx

Could you give us the exact error that is being displayed? (Maybe check the error logs of your web-server/PHP as well.)

When creating a test site of your live forum you need to make sure that you change all the settings in config.php and in admincp that point explicitly to the live site.

yep did this pointed the attachments to the dev site and re configured config.php:)

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

ok ill try and find it dave, it only shows the error in ie and not chrome its stage 89 of 110 i think in 4.0 when it trys to move the pictures to the attachments from the database this is on the live dev server which i only have access to, very annoying as i say i dont want to bugger the live live site, also dave do you do skins? i need our current 3.7 skin replicated in 4.2.3 once running?

found log error

PHP Warning: chdir() [<a href='function.chdir'>function.chdir</a>]: open_basedir restriction in effect. File(/var/www/vhosts/.org/httpdocs/boards/) is not within the allowed path(s): (/var/www/vhosts/dev.****org/:/tmp/) in /var/www/vhosts/dev.org/httpdocs/header.php on line 19, referer: http://dev.org/boards/

line 19 of header.php

chdir("/var/www/vhosts/dev.org/httpdocs/boards/");

Hmm that seems fine.

What if you run the upgrade in Chrome but you open up the "Developer Tools" in Chrome (F12) before you start. Then click on the network tab and keep it open, then run the upgrade. If there's an error again, you should notice one of the network requests timing-out or displaying an error. Click it and view the response so you can see the exact error that is being displayed.

Off-topic: yes, I do convert themes from vB3 to vB4.

cool may have sorted prob too

schoolboy error i have a dup of the dup and had not changed the attachment storage place to dev

doing now looks ok atm

can i pm u regarding custom work what are rates like? may have a few bits to sort

regards mick

Yes, you're more than welcome to PM me or email me at dave[at]technidev[dot]com.

awesome buddy thanx:up:

just noticed a problem no attachments are being displayed in the new 4.2.3 there pointing to the right place on the duplicate on the test site

the orig 3.7 is fine

anyone had this before

You probably encountered a bug in the vBulletin upgrade, it's not uncommon to happen.
Read all replies in the following thread, it will surely help you out: https://vborg.vbsupport.ru/showthread.php?p=2552602

interesting dave wish they told me that before have to duplicate all again and upgrade again as i didnt backup :eek::eek::eek:

has anyone tried 4.2.4 beta 1?

cant get to grip with the guide atm so not sure how i can so it

When you re-attempt this be sure to:

- Disable all old 3.x mods.
- If vBSEO is installed, remove it completely. This mod may prevent a cloned i.e. test site from being made, I've seen odd issues with vBSEO more so when removing it or making changes.

*Also note: This should be a cloned copy of the backup, if it goes well then you can use it as live site otherwise live site is still up and running in 3.x format. Do not work on a live site ever and so far seems you knew not to do that - what they meant was it failed this time so you must repeat process using new copy of database (because old copy you had is now outdated by a few days, even if you did get it to work it would be old data and missing all new members, threads, and posts from the live site) so with that said, you must run another backup and try to upgrade that not the old one you had issues with. *I would make one new good backup, then use it as much as possible until you have it upgraded properly, then you will know every issue you ran into and how to fix - that is when you close the live 3.x site, run a final backup then upgrade it and fix all the errors you know will come up becuase you already cloned this and upgrade a "temporary" clone site to ensure it worked properly.

If you do not disable the old mods issues can arise. I've also seen attachments and css stored as files act oddly, usually reversing how it stores either before upgrading sorts the issue then you can simply switch back to the previous storage method after the upgrade completes.