Upgrading from 1.0.2 to 3.20 Question
 

Hey Chuck,

Now that PhotoPost and Classifieds are running more or less successfully on my website, I'm ready to tackle my upgrade of ReviewPost 1.0.2 to the newest releast 3.2.

I gave it a quick go a few minutes ago, and immediately ran into that SQL error that said the there was no table named "rp_usergroups."

When searching this forum I had seen that someone ran into this problem some time ago and when I asked you about it you said it was some other problem of his. That this wasn't a problem.

Here's what I did and what happened:

I ran upgrade.php and right away it posted an error that there was no rp_usergroups table. (version 1.0 seems to have called this table "usergroups" not "rp_usergroups". All the other tables were called rp_ --- at least I think they were.)

I decided to try to "fix" it so I renamed that table to rp_usergroups and ran upgrade.php again. But that brought more errors. I decided to keep going and I got more errors all the time. Finally, at the end, the program looked like it was working but had two sql table errors on the index page AND I couldn't log on (it wouldn't recognize my username/pw combo).

So, I just reverted everything back to the old working version for now so I could ask you about how to proceed.

So, let me ask you one more time. Before running upgrade.php should I rename the table "usergroups" to "rp_usergroups"???

And what should I do if I encounter other sql upgrade errors? Stop and refer them to you. OR just keep going? Since this is a working website I'd prefer to not cripple it for too long.

Thanks
Paul

The upgrade script looks for the tables based on your table prefix you have entered in the reviewpost config-inc.php file.

I have not encountered any 1.02 reviewpost sites but that was before my time with the company so can't say but looking at line 214 of the script I see this and note the change I made in bold

Now your upgrade should go smoothly just run each step ONLY ONCE and make sure before you begin to take a backup of your database cause the last upgrade changes the file structures and all so make sure you have a backup in case you run it twice by mistake etc.

You lost me. Are you telling me to do something? If so what?

Add rp_ to usergroups?

Change line 214 to what is in the code box?

What is it that I should do to make it so that "Now your upgrade should go smoothly"????

line 214 in upgrade.php should be as posted above

OK, but this still leaves the question about changing the table name from usergroups to rp_usergroups before attempting the upgrade.

Please... yes? or no?

NO the issue was the upgrade script was explicitly looking for usergroups instead of $gtable which is set above line as the proper prefix.

OK got that. But I still got:
Performing MySQL command: ALTER TABLE rp_usergroups ADD modaccess smallint(3) NOT NULL default '0' ... Error: Table 'tdpri.rp_usergroups' doesn't exist
Performing MySQL command: ALTER TABLE rp_usergroups ADD reviews smallint(3) NOT NULL default '1' ... Error: Table 'tdpri.rp_usergroups' doesn't exist

So I tried it with usergroups renamed to rp_usergroups and that went fine until... I did get some other errors when going through the various version updates.

When I did the update to 2.5 sql phase I got these errors:

Unknown table -- rp_stylesheet

rp_online -- can't drop "userid"
rp_products -- can't drop "approved" and "date"

for all these errors it said "make sure this table exists."

I know that rp_stylesheet and rp_online doesn't exist. rp_products does exist and approved and date fields do exist too.

I didn't go past this part of the upgrade script. Instead I stopped, dropped all the rp_ tables and restored the original 1.0.2 tables.

I can simply go forward with these errors, but I thought it might be better to stop and ask before doing that.

Thanks

I think your running an older reviewpost that you think. In the upgrade script 1.0 it creates a table iponline with the prefix your site uses.

You just need to go forward and run EVERY UPGRADE ONCE. Especially from the beginning if your iponline table does not exist.

Ok, Here's the details on my upgrading of the SQL from 1.0 to 3.2

First, I renamed usergroups to rp_usergroups. It really seems to need that.

Here are the errors received on the way:
1.0 to 2.0
None

2.0 to 2.1
None

2.1 to 2.52
None

2.5x to 2.8
Performing MySQL command: DROP TABLE rp_stylesheet ... Error: Unknown table 'rp_stylesheet'

Performing MySQL command: ALTER TABLE rp_iponline DROP INDEX userid ... Error: Can't DROP 'userid'. Check that column/key exists

Performing MySQL command: ALTER TABLE rp_products DROP INDEX approved ... Error: Can't DROP 'approved'. Check that column/key exists

Performing MySQL command: ALTER TABLE rp_products DROP INDEX date ... Error: Can't DROP 'date'. Check that column/key exists

2.8x to 2.9
Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 645

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 646

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 647

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 648

2.px to 3.0
Performing MySQL command: ALTER TABLE rp_usergroups ADD reqmod INT(3) DEFAULT '0' NOT NULL, ADD uplimit INT(3) DEFAULT '0' NOT NULL ... Error: Table 'tdpri.rp_usergroups' doesn't exist

erforming MySQL command: ALTER TABLE rp_categories ADD thumbnail INT(15) DEFAULT '0' NOT NULL ... Error: Duplicate column name 'thumbnail'

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 810

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 811

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 812

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 813

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 814

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 815

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 816

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 817

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 818

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 819

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 820

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 821

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 822

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 823

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 824

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 825

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 826

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 827

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 828

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 829

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 830

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 831

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 832

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 833

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 834

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 835

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 836

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 837

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 838

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 839

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 840

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 841

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 842

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 843

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 844

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 845

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 846

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 847

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 848

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 849

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 850

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 851

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 852

Warning: unlink() failed (No such file or directory) in /home/www/tdpri.com/reviewpost/upgrade.php on line 853

3.0x to 3.1 None

upgrade to 3.11
None

I'm getting errors pointing to the usergroup table.

I'm going to drop all the tables, restore the backup of the old and start again as you suggested without changing the usergroup table name.

I'll get back to you.

I ran into errors running the application on my browser after that above. All seemed related to usergroups. So I went back and restored the old database and tried upgrade.php again only this time without renaming usergroups. Here's what happened:

I got these two new errors on the 1.0 to 2.0 update:

Performing MySQL command: ALTER TABLE rp_usergroups ADD modaccess smallint(3) NOT NULL default '0' ... Error: Table 'tdpri.rp_usergroups' doesn't exist

Performing MySQL command: ALTER TABLE rp_usergroups ADD reviews smallint(3) NOT NULL default '1' ... Error: Table 'tdpri.rp_usergroups' doesn't exist

And then I got all the same errors as before. Plus one or two other rp_usergroups doesn't exist erros farther along the upgrade path.

And I'm getting the same errors on running the reviewpost website:

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/www/tdpri.com/reviewpost/forums/phpbb2.php on line 353

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/www/tdpri.com/reviewpost/forums/phpbb2.php on line 353

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/www/tdpri.com/reviewpost/forums/phpbb2.php on line 353

And there is no Admin link on the menu yet is shows me logged in. I'm guessing without usergroups that everyone is logged in.

Can I copy the usergroups table from Classifieds or PhotoPost and apply it to the Reviewpost tables?

Here's some more stuff I tried.

I noticed that there was no rp_users table. So I copied the table from Classifieds. And while at it I copied the class_usergroups table to rp_usergroups as well. Still no go.

I still get
Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/www/tdpri.com/reviewpost/forums/phpbb2.php on line 353

And it won't give me access to Admin (doesn't show option)

Then I deleted all my cookies.

But I still get the same errors on the reviewpost index page. Now it showed me logged out after deleting the cookies. But it wouldn't let me log in.

I logged in on my main phpbb website and went to reviewpost. Now it shows me logged in, but still not admin.

Looking at the rp_usergroups table in phpmyadmin it shows me as having cpaccess.

Looking forward to hearing some solutions from you about all of this.

Okay don't know what solutions I can post.

basically the only error you need to worry about is here

Now why your rp_usergroups table does not exist I can not say. Clearly the upgrade script has no issues since the query is this

There is nothing wrong with that query on the upgrade. Many people have upgraded from 2.8 2.9 to 3.2.

Basically your config file says your table prefix is rp_ which means rp_usergroups better exist and you say there are no errors in upgrade 1 yet upgrade one adds fields to the usergroups table in the same way.

I would suggest you go through the install making sure first you have the proper prefix set in your config. If your tables have no prefix make sure your config has the prefix set to empty. If your config has a prefix of rp_ then make sure all tables have rp_ in front and yes rp_users should exist as well so it looks to me like your missing tables.

Hey Chuck.

Yes, it does say that the prefix is rp_

I guess that this was a bug in version 1.0 because you had another user quite some time ago with the exact same problem rp_ for all db tables EXCEPT usergroups.

I'll run everything again. I have a good back up that is easy to apply.

What do you think about rp_users not being created during this upgrade? That table doesn't exist either in version 1.0.2 and this upgrade doesn't create it.

The rp_users table has existed in reviewpost since it came out in version 1.0

As to why your's does not exist I can not say but it is not the norm. The other user who reported an error on upgrade 1.0 I posted that fix above but we still come down to your issue why if you have a rp_usergroups table do you have an issue not altering that table on 2.9-3.0 upgrade.

I might have a reason why I didn't have rp_users. But it's just a guess.

OK, my install had everything as rp_ in the SQL tables except "usergroups". Now lets suppose the the same was true for "users".

After installing reviewpost 1.0.2 I installed phpclassifieds into the same database. And phpclassifieds had a user table and no prefixes. So, the phpclassifieds could have overwritten the reviewpost users table.

I was a real newby on SQL tables back then and I would never have noticed.

Now, why did reveiwpost 1.0 not put rp_ in front of those two tables when it put that prefix in front of all the other tables?

Humm, I posted a Sucess post, but don't see it now. Just so you know, I got it working. I detailed how in that missing post. But maybe you removed it on purpose so I'll not go back into all of that. Let me know if you need to know what I did to get it working.

I would assume to get it working you made sure all your tables had the proper prefix

Actually, I just copied my classifieds usergroup and user tables into rp_usergroups and rp_users tables. Then I dropped all the newly upgraded tables except those. Then I restored all the 1.0.2 version database files and reran upgrade.php for the 8th time.

Somehow, that did the trick. It's working fine.

Thanks
Paul

You cant interchange usergroup tables The reviewpost install file has the current usergroups table if you wanna try that one ;) No need to run an upgrade again just create the table and put the inserts in there and set permissions