Upgrading from v. 1.0.2 to v. 2.9.1

[Khashyar]

I reran the upgrade.php script, and clicked on: "2.5 to 2.8," and then reran it again and clicked on "2.8 to 3.0"

It seems that the upgrade.php script stopped at upgrading to version 2.5

Also, when I ran "upgrade from 2.8 to 3.0," I received these permission errors:

Preparing to update 2.8 database...
Performing MySQL command: INSERT INTO rp_settings VALUES (165,'Your SMF Cookie Name', 'smfcookie', 'Only needed for users of SMF forums', '', 5, 12) ... Successful!
Performing MySQL command: INSERT INTO rp_settings VALUES (198,'Use 24 hour time format?','timeformat', 'You can elect to have time displayed as HH:MMam or using the 24 hour clock', 'no', 32, 1) ... Successful!
Performing MySQL command: INSERT INTO rp_settings VALUES (205,'Show Last Reviews column on Index?','showrevs','','yes',16,3) ... Successful!
Performing MySQL command: INSERT INTO rp_settings VALUES (206,'Show Last Product column on Index','showlast','','yes',17,3) ... Successful!
Performing MySQL command: REPLACE INTO rp_admingroups VALUES (12,'Forum Settings') ... Successful!
Performing MySQL command: DELETE FROM rp_settings WHERE id=100 ... Successful!
Performing MySQL command: ALTER TABLE rp_products ADD numreviews INT(12) DEFAULT '0' NOT NULL AFTER lastpost ... Successful!
Performing MySQL command: REPLACE INTO rp_settings VALUES (84,'ReviewPost Version','pversion','','2.91',53,0) ... Successful!

Warning: unlink(./showgallery.php): Permission denied in /home/russianm/public_html/reviews/upgrade.php on line 570

Warning: unlink(./login-inc.php): Permission denied in /home/russianm/public_html/reviews/upgrade.php on line 571

Warning: unlink(./email-inc.php): No such file or directory in /home/russianm/public_html/reviews/upgrade.php on line 572

Warning: unlink(./adm-backup.php): Permission denied in /home/russianm/public_html/reviews/upgrade.php on line 573


Finished upgrade! You may now remove this script.

Regarding the permission errors above, I am going to try to change the permissions on the upgrade.php script to 777 and see what that does...

[Khashyar]

I receive the same permission errors....

Do I need to change the permissions in these files as well? (they are currently set to 644 as the install directions recommend) :

showgallery.php

login-inc.php

adm-backup.php


And, do I need to create this file:

email-inc.php ["No such file or directory"]

[Khashyar]

I created and uploaded the email-inc.php file.

I changed the permissions to those 4 files to 777, and I still receive this error during the "2.8 to 3.0" upgrade script:

Warning: unlink(./showgallery.php): Permission denied in /home/russianm/public_html/reviews/upgrade.php on line 570

Warning: unlink(./login-inc.php): Permission denied in /home/russianm/public_html/reviews/upgrade.php on line 571

Warning: unlink(./email-inc.php): Permission denied in /home/russianm/public_html/reviews/upgrade.php on line 572

Warning: unlink(./adm-backup.php): Permission denied in /home/russianm/public_html/reviews/upgrade.php on line 573


Finished upgrade! You may now remove this script.

[Khashyar]

Hi Michael and Chuck,

I deleted the upgrade.php script, and when load my main page, I receive this error:

Warning: main(./forums/2.2.0.php): failed to open stream: No such file or directory in /home/xxxxx/public_html/reviews/pp-inc.php on line 2081

Warning: main(./forums/2.2.0.php): failed to open stream: No such file or directory in /home/xxxxxxxx/public_html/reviews/pp-inc.php on line 2081

Fatal error: main(): Failed opening required './forums/2.2.0.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/xxxxxxx/public_html/reviews/pp-inc.php on line 2081

VB 2.3.4 does not have a file called "2.2.0.php" in its root directory.

Khashyar

[Khashyar]

Somehow, those errors went away without me doing anything, and now I am left with this one error:

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/russianm/public_html/reviews/forums/vb2.php on line 259

Khashyar

[Khashyar]

Also.... although I can now open the categories and reviews, neither the "star" ratings nor the 1 to 5 ratings are showing up....

At the moment, I am still also receiving the vb2.pp error..... And when I log onto the RP with my VB administer login name, it tells me that "You are not a valid administrator! "

Khashyar

[Khashyar]

[I am posting the errors here in this thread and the steps that I am trying so that others who might have the same issue perhaps can learn something if they are experiencing similar errors]



When I try to logout from my screen name, I receive these errors which quickly display themselves on the page, then I am redirected to the index page again without having been logged in.

There seems to be a VB 2.3.4 settings or integration issue:

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/russianm/public_html/reviews/forums/vb2.php on line 259

Warning: Cannot modify header information - headers already sent by (output started at /home/russianm/public_html/reviews/forums/vb2.php:259) in /home/russianm/public_html/reviews/forums/vb2.php on line 179

Warning: Cannot modify header information - headers already sent by (output started at /home/russianm/public_html/reviews/forums/vb2.php:259) in /home/russianm/public_html/reviews/forums/vb2.php on line 180

[Khashyar]

This debug email had been sent to me several times over the past 30 minutes:

An error was encountered during execution of the query:

SELECT cpaccess,modaccess,uploads,reviews,editpho,editposts FROM rp_usergroups WHERE groupid=6 LIMIT 1

The query returned with an errorcode of:

Unknown column 'modaccess' in 'field list'

[Khashyar]

I solved some of the issues altering the MySQL database.

Here were some of the issues:


1) The RP 1.0.2 DB had a table called "usergroups," even though all of the other tables had an rp_ prefix to them. When I upgraded with the upgrade.php file, a dataless table called "rp_usergroups" was created, but none of my "usergroups" info from my 1.0.2 DB was transferred to the newly created 2.9.1 "rp_usergroups" table.

2) I had to rename my "usergroups" table (which was present after the upgrade along with the dataless "rp_usergroups" table) to "rp_usergroups," after deleting the newly created "rp_usergroups".

3) I had to create a "reviews" column because it did not exist in the old "usergroups" column.

4) The upgrade.php file did NOT take me through all the upgrades. It stopped at "upgrading 2.5." I had to restart the update.php file a couple of times to exercise the full upgrade.

5) By the way, there was NO "modaccess" column created in the new "rp_usergroups" table that was created in the 2.9.1 upgrade. This produced an error.

So, I hope that no one else has the same issues as I had with upgrading, but if you do, I hope that some of my experience helps....

Khashyar

[Khashyar]

By the way, the 1 to 10 ratings are not showing up as stars in my category or review pages.....

I wonder why?

And, I wonder how the 2.9.1 software (which issues a 1-10 rating) is going to handle the 1-5 ratings of the older RP 1.0.2 software?

Khashyar

[Khashyar]

I seemed to have fixed all of the issues (with help from the "ratings" bug thread)....

I feel relieved

Khashyar

[Michael P]

I'll go back over the upgrade.php to address these issues, thanks for going through it with us.

The modaccess change to usergroups is on line 152 in upgrade.php; wonder why that didn't take. hmmm

[Chuck S]

Here are the issues

in the upgrade script is this

$query[] = "ALTER TABLE usergroups ADD modaccess smallint(3) NOT NULL default '0'";

it needs to be

$query[] = "ALTER TABLE {$rp_db_prefix}usergroups ADD modaccess smallint(3) NOT NULL default '0'";

then in the 2.5 upgrade we add setting 100 to allow rating and then drop it later in the 2.8 upgrade here

$query[] = "DELETE FROM {$rp_db_prefix}settings WHERE id=100";

we need to remove the above line

[Khashyar]

Thanks for your replies, Michael and Chuck.

There probably will not be that many other users upgrading from 1.0.2 to 2.9.1, but I'm glad that we can resolve the upgrade issues for those who will be going through the same upgrade process.

Regarding the "usergroups" table:

In the 1.0.2 database, all of the other tables have an "rp_" prefix EXCEPT for the "usergroups" table.

So, perhaps that was a bug in the 1.0.2 install script? OR perhaps that happened when I updated my usergroups with my vb 2.3.4 forum in the RP admin panel?

Whichever the case many be, the update.php file did not transfer the 1.0.2 "usergroups" data to the newly created "rp_usergroups" table in RP 2.9.1

I'm glad that we have discovered the issue and know how to resolve it for others.

By the way, I really do like the changes that you made from 1.0.2 to 2.9.1. They are really appealing revisions.

You did a great job upgrading the interface and additional functions of 2.9.1.

Thanks for all of your hard work on the software.

Khashyar