New install PP7 and members data

[drare]

I have decided to leave the 6.2 version of PP and the 3.8.2 of VB.
I have made and test enviroment on my local PC with Wamp Server.
I made a new install of VB 4.0.1 in a new dbase and imported all data to the new dbase, this went very well.

Now I need to do the same with PP 7.1, I can make a new install, also in a new and seperate dbase from VB, no problem, but now I need import the users and all other data of PP from the old database, somehow I can't find the option to import this data like VB does, did I miss something?

How can I import PP data from the old database?
Gerard

[Chuck S]

Gerard

You dont import. You would clone your PP database and then run the upgrade script to get tables into 7.01 format although 7.01 only adds a couple settings etc

Why cant you just backup your database tables and restore them to the new server run install against those tables and upgrade?

The install will correct the settings in the settings table. The upgrade will add any missing settings. Thats really how I would do it.

[drare]

Chuck I did indeed made an duplicate of the pp_ tables into a new database, so all old data is in a new dbase, well I think my question has been answered, I can upgrade to 7.1without extra effort of importing data, hopefully the intergration with vB4.01 goes smooth.

Thanks Chuck.

[Chuck S]

yes indeed if you cloned the database you either update urls and server paths directly in the settings table to make it work right or run the install script to correct that stuff. You can then simply upgrade your copy to 7.01 and run the upgrade and integration with vb4 is auto sensing so no worries there.

[drare]

Chuck,

I've done a new install of VB4 and imported all data, so far so good.
I've changes config settings voor PP7 and did an upgrade, somhow I get these errors:

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/wfcfoos8/public_html/gallerij/forums/vb3.php on line 32

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/wfcfoos8/public_html/gallerij/pp-inc.php on line 4047

And my Admin login is not regognized by PP7, somehow I think it has to do with the intergration of VB4 and PP7, I saw on Lurofoto some XML files to intergrate with Vb4 (plugins) they did not come with the PP7 package, what do I do next?

Gerard

[Chuck S]

vBulletin Installation/Integration Common Issues and Resolutions.

Number 5 on our common vb3 issues FAQ

I would suspect here on install the correct table prefix of vb3 mysql tables was not entered.

[drare]

Yep, sorry I did see it, however I did everything described in this thread, but still I get the same error and no recogniton as administrator. I checked the prefix, it's ok.

Can't do anything :-(

[drare]

I downloaded the XML file manually and tried to import it in VB4, this is what it says:

XML Error: junk after document element at Line 2

I have vB version 4.0.1

[Chuck S]

what are we talking about here? You seem to be discussing something else outside the normal product support here as photopost does not use an XML file

Back to your post about your gallery. Please post a link to your photopost. If your getting this error

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in /home/wfcfoos8/public_html/gallerij/forums/vb3.php on line 32

either your user database settings are incorrect or on step 4 of the install the wrong vbulletin mysql table prefix was entered. This is a pretty explicit error.

[drare]

Chuck, I was referring to the mod: pro-7-0-plugin-vbulletin-4-0-a, you get an XML file.

But I made a big error, PP and VB have two seperate data bases, that was the problem I totally forgot this because the "old" installation has only one dbase.
I finally merged both databases again, now I'm recognized as Admin, finally, it was my own fault. Now I, going to try and to the mod as you described, sorry for any misunderstanding here.

I let you know if intergration is succesfull.
Gerard

[Chuck S]

Pretty much an absolute error when you hit mysql issues which is why I posted the same thing over again. Had to be what I was talking about and it was.