Upgrading from v. 1.0.2 to v. 2.9.1

[Khashyar]

Hello Everyone,

I could not find instructions for upgrading RP from version 1.0.2 to 2.9.1?

Does anyone know what is the best way of doing this?

Thank you,

Khashyar

[Khashyar]

If we are upgrading from RP 1.x to 2.x, do w have to manually configure the "config-int.php" file?

At the moment, I am receiving this error after upgrading:

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

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/xxxxxxxx/public_html/reviews/showcat.php on line 300

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/xxxxxx/public_html/reviews/showcat.php on line 325

And even though I am using a vb 2.3.4 forum as my user DB, my "config-int.php" file states:

// We need to know the server paths to both your vB installation and your ReviewPost installation
$vbpath = "/home/sites/yoursite/web";
$pppath = "/home/sites/yoursite/web/reviewpost";

// We need the URL path to your PhotoPost and vb installation
$url_path = "/reviewpost";
$vb_urlpath = "/forum";

// The URL of your photo dir where your images are stored (with / at end)
$data_dir = "/reviewpost/data/";

// If your reviewpost tables have a prefix, put it here
// Example:
// $rp_db_prefix = "rp_";
$rp_db_prefix = "";

Thanks for your help with this...

Khashyar

[Khashyar]

I just reinstalled by previous RP 1.0.2 files and DB (which integrates without errors with my VB 2.3.4 forum), and I will try to install the RP 2.9.1 upgrade again.

Khashyar

[Khashyar]

Here are some errors that I received during the last phase of the upgrade script:

Performing MySQL command: DROP TABLE rp_stylesheet ... Error: Unknown table 'rp_stylesheet'

and

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

[Khashyar]

I receive the exact same MYSQL errors when going to my newly upgraded RP 2.9.1 site...

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

and

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/xxxxxxx/public_html/reviews/showcat.php on line 300

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/xxxxxxx/public_html/reviews/showcat.php on line 325

I would appreciate any feedback.

Thanks,

Khashyar

[Khashyar]

I reinstalled my old RP 1.0.2 software (which is working fine and integrating well with VB 2.3.4) until we can figure out why the upgrade did not work.

Khashyar

[Khashyar]

I tried a new test fresh install of the full RP 2.9.1 in another directory on my server, and although the install instructions said to change the permissions on the config-inc.php file to 644, the full install could not write to the config-inc.php file until I changed the permissions to 777.

I wonder if my upgrade issue is related to this permissions issue?

During the upgrade process, does the upgrade.php file write to any files?

Khashyar

[Khashyar]

One odd thing is that when I was checking the DB for my RP 1.0.2, it has tables called "rp_usergroups" AND "usergroups".

"rp_usergroups" is empty, and "usergroups" is not. Perhaps "usergroups" is somehow imported into the DB when you choose to use a forum usergroup list.

But, there is not a "rp_stylesheet" table in either my 1.0.2 or newly installed and working 2.9.1 versions. (See the MySQL error involving "rp_stylesheets" in an earlier post).

Khashyar

[Khashyar]

Perhaps someone might be able to help with understanding which variables are not being executed right in the .php code. I would appreciate any help or feedback on this.

The code for this error:

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

refers to this line in the vb2.php file:

// groups less than 1 have no posting privledges..
if ( $usergroup < 1 ) {
$User['nopost'] = 1;
}

$query = "SELECT cpaccess,modaccess,uploads,reviews,editpho,editposts FROM {$Globals['rp_db_prefix']}usergroups WHERE groupid=$usergroup LIMIT 1";

$resulta = ppmysql_query($query,$link);
list( $User['adminedit'],$User['moderator'],$useruploads,$userreview,$ueditpho,$ueditposts ) = mysql_fetch_row($resulta);
ppmysql_free_result($resulta);

$CatPerms = array();
$listofcats = set_group_perms( $usergroup );
$Globals['offset'] = $offset;

$catarray = explode( ",", $listofcats );
foreach ($catarray as $thecat) {
if ($CatPerms['ugview'][$thecat] == 1) {
$exclude_cat .= " AND cat != $thecat";
}
}

if ( $gologin == 1 ) {
$User['username'] = $Globals['pp_lang']['unreg'];
$User['userid'] = 0;
$Globals['offset'] = $Globals['gmtoffset'];
}

And this error:

Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /home/xxxxxxx/public_html/reviews/showcat.php on line 300

refers to this line:

$queryv = ppmysql_query($query,$link);
$rowcnt = mysql_num_rows($queryv);

This last error:

Warning: mysql_fetch_row(): supplied argument is not a valid MySQL result resource in /home/xxxxxxx/public_html/reviews/showcat.php on line 325

refers to this line in the showcat.php script:

while ( $row = mysql_fetch_row($queryv) ) {
if ( $cat == "fav" )
list( $favid, $id, $tuser, $tuserid, $pcat, $date, $title, $desc, $keywords, $bigimage, $views, $approved, $imgrating, $manuf, $comcount ) = $row;
else
list( $id, $tuser, $tuserid, $pcat, $date, $title, $desc, $keywords, $bigimage, $views, $approved, $imgrating, $manuf, $comcount ) = $row;

Thanks again for any thoughts...

Khashyar

[Michael P]

Not sure where to start since it seems you've done several things since your first post.

First thing is you can ignore the DROP warnings, since they are just telling you that it cant DROP something that isn't already there.

$query = "SELECT cpaccess,modaccess,uploads,reviews,editpho,editposts FROM {$Globals['rp_db_prefix']}usergroups WHERE groupid=$usergroup LIMIT 1";

Appears this query is failing - can you check your RP usergroups table and see that all those fields are in that table?

Are you working form the upgrade or a new install at this point? I'm a little confused as to where you are in the process right now.

[Khashyar]

Thanks for the reply, Michael.

What I've done at this point is to reinstall the old RP 1.0.2 software and DB (which is working fine), but....

I would like to install the upgrade again.

So, it seems like the upgrade process is not creating all of the necessary new fields in the table when it is upgrading the table from 1.0.2 to 2.9.1...

Could you please post the Mysql query that I could need to run to create new fields in phpmyadmin if they are missing?

If you don't want, I would like to temporarily create a second fresh nonpublic install of RP 2.9.1 along with upgrading the 1.0.2 version so that I can compare the DBs and see which fields might be missing.

Also, does the upgrade process write to any .php or other files? If so, then I need to change those files to chmod 777, since that is the only setting that will allow me to write to them.

I and going to begin working on the upgrade again later this afternoon, but I appreciate any thoughts or ideas that I can apply then.

Thanks,

Khashyar

[Chuck S]

Usually upgrading is like this you upload all the files except do not overwrite config-inc.php and then run upgrade.php in your browser and run all applicable upgrades

[Michael P]

I haven't run an upgrade from the 1.0 series in a long time; follow what Chuck says and if you have any troubles, PM me your server info and I'd be glad to take a look (phpmyadmin, ftp, a login).

Grab a current 2.91 from the members area and be sure to start with that.

[Khashyar]

Thank you for your help and feedback, Michael and Omega...

I actually DID overwrite my config-inc.php file, but only after changing the settings on the new file.

However, the config-inc.php file for v 2.9.1 has a few more settings than the config-inc.php file for 1.0.2

Doesn't RP 2.9.1 need those other settings?

I will try an upgrade again in a few minutes....

(And thanks, Michael, for taking a look at the upgrade if things don't upgrade properly this time).

Khashyar

[Chuck S]

If using the new config just make sure all the info is correct and you should be fine. The key is as I noted to make sure to run all the proper upgrades so all the new fields and changes to the database are made

[Khashyar]

Yes, Omega...

I did go through all of the steps of the upgrade.php file.

I have installed several .php MySQL-based programs on servers, so I followed the directions carefully

It seemed that the update.php file (or the .sql file) did not properly upgrade all of the database from 1.0.2 all the way to version 2.9.1.

When I did a test fresh install of RP 2.9.1 (without upgrading), it worked fine.

But there is a problem in the upgrade process.

Khashyar

[Chuck S]

Well I have done a few upgrades from that version without issue as I do the upgrades for the company.

Lets take one error you have the showcat one

Most likely it is failing on the numreviews field that was added to the products table however if you ran the 2.8 upgrade it is added

$query[] = "ALTER TABLE {$rp_db_prefix}products ADD numreviews INT(12) DEFAULT '0' NOT NULL AFTER lastpost";

try turning on debugging to display errors so you can see the full nature of the error

offer still stands Michael or I would have no problem assisting you find out the nature of the issue but you would need to send access info

[Khashyar]

Thank you, Chuck.

Yes, I am sure that you have done many upgrades and know the software well.

I will do an upgrade again now, and then will send you the information in a few minutes.

Just to double check on something:

Should the config-inc.php file have file permissions of 644, or 777? (The instructions say all .php files should be set to 644, but the instructions for photopost say 777).

Thanks,

Khashyar

[Khashyar]

Also, do you think that I should leave the original config file during the upgrade?

Will the upgrade.php file update it and add any necessary fields?

Or is it best to use the new config file? (When I did a fresh install of RP 2.9.1, everything worked fine, so I assume that I had the correct config settings.)

Thanks,

Khashyar

[Khashyar]

Hi Michael and Chuck....

The last upgrade step is titled:

"Preparing to update 2.5 database..."

and at the end of this upgrade, it says:

"Done! You can now remove this file and check out your new Admin Options layout!"

Shouldn't there be some additional upgrade steps here? (like from 2.8 to 2.9, etc??)

Khashyar