>> Site Map >> Forums >> Patched 7.6.0.3.x
Forum module - topics in forum:
Patched 7.6.0.3.x - Questions, Comments and Bug Reports for nCo Patches
phpBB import script nukesql.php fails on Co_Ultra_Patched_31
I have phpbb 2.0.17 forum users / data i would like to import into nCo Ultra.
I have the data both as a dump of the original phpbb 2.0.17 forum and as data imported into nuke 7.8 (with BBtonuke2017) database.
I am using a fresh install of nCo_Ultra_7.6.0, with nCo_Ultra_Patched_31 applied straight after.
When running the script, it does the checks, and displays with the "import" link, but when I click it ( and go to nukesql.php?op=def_install ) I just get a white page.
Any ideas ?
TIA
Clive
Ok first thing you need to do is check to make sure that your prefix on your old tables make the current prefix of your database. If it does then it is easy if not you will have to change the name of the old prefix to reflect the new prefix that you have on your current install. Then you will need to go thru that sql file that you have of your users data write down all of the tables that you have on a notepad. Log into cpanel this is assuming what you are using go into MySQL Databases scroll down and click on phpMyAdmin then select your database. Choose the tables that you have the data for put a check mark in each box. Go down to the bottom and for action selected choose Drop then confirm that you want to drop those tables. Now at the very top click on your database name and then click on the SQL command button. Now you have 2 choices here you can copy all of the data from the sql file that you have of the old tables and paste in that box and click go. Or you can browse to that sql file and query they file to create the tables. Since you already have the data in a sql file I would choose to browse and query the file. This will create all of the tables from and input the data and values for those tables. Please remember to fully backup your site before doing this kind of work.
urg, not sure I 100% understand. To be honest you made it too simple - I know my way well around phpmyadmin and SQL generally.
Also, the lack of carriage returns kind of makes it difficult to absorb.
Not that I am complaining mind you, your help and advice is appreciated.
What I think you are trying to say is:
Don't use the import script
Take the phpbb forum fields (phpbb_*) and rename them to nuke_bb*
Then drop all of the nuke_bb tables in my nuke install and replace them with the phpbb ones.
What about the users table ? in nuke it is nuke_users but in phpbb it is phpbb_users ( which would be renamed to nuke_bbusers )
Now from looking I have just realised that the nuke admins are not in there, they are in nuke_authors, so I figure it'll be cool to waste the existing (empty except for anon) nuke_users table and replace it with the phpbb_users table.
Now the only problem I am left with is the NSN groups breaking with the 31 patch and I can get phpbb inside nuke to 2.0.17 and upload the data as you say.
I think I will probably give importing the phpbb data how you say a go tonight anyway - I have 2 spare databases on the server and SSH access, so it's easy moving data around via the mysql command line.
Thanks once again !
In theory that should work as I havent ever converted phpbb to bbnuke but as long as you have back ups wont hurt to try. If all of the values of the tables match for both the bb tables and the users tables you should be fine. You will have to play with an experiment a bit with this work out any errors that you will recieve. As far as the groups being broken I havent really played around with that module to give you an answer that will fix your problem. And yes I was saying to take the phpbb fields and renaming them nuke_bb.
well as I managed to import the data from phpbb 2.0.17 into nuke 7.8 (patched with bbtonuke 217 to make phpbb in nuke 7.8 version 2.0.17) then surely I have all the data I need already in a nuke-embedded phpbb 2.0.17.
Thanks for clarifying all of this. I think I may have just solved the NSN groups issue so the road ahead may be clear
