2.6 to 3.01 Upgrade Problem

DHewes · April 7th, 2008, 08:39 AM

I had 2.61 running, copied over all of the files/folders (I updated the config files first, left out the additional languages and forum files and left out install.php). I then ran the upgrade.php, selected the correct upgrade link and ended up with a screen full of errors. Other then table name and line number, all errors are the same (sample pasted below). I am sure I am missing something here...any thoughts?

Error performing MySQL command: CREATE TABLE ppc_messages ( msgid int( 12 ) NOT NULL AUTO_INCREMENT , userid int( 12 ) NOT NULL default '0', datestamp int( 15 ) NOT NULL default '0', message mediumtext, status smallint( 1 ) NOT NULL default '0', type enum( 'c', 'f', 'i', 'm', 'r' ) default NULL , product int( 12 ) NOT NULL default '0', PRIMARY KEY ( msgid ) ) TYPE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_bin
Error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'DEFAULT CHARSET=utf8 COLLATE=utf8_bin' at line 9

My server info:
Apache version 1.3.37 (Unix)
PHP version 4.4.4
MySQL version 4.0.27-standard
Architecture i686
Operating system Linux

I have confirmed in phpMyAdmin that these new tables do not in fact exist. I have also verified that the name/password in the config file is correct.

Thanks!

Chuck S · April 7th, 2008, 10:30 AM

Weird php4 allows the setting of collation. You can try editing your upgrade.php file and remove this from the queries

Code:

Content visible to verified customers only.

DHewes · April 7th, 2008, 10:48 AM

I removed all entries of that line and re-uploaded upgrade.php. Now I get a screenfull of these errors:

Preparing to update database...
Error performing MySQL command: ALTER TABLE ppc_users ADD realname varchar(80) default NULL, ADD title varchar(30) default NULL, ADD signature varchar(250) default NULL, ADD avatar varchar(120) default NULL, ADD invites int(6) NOT NULL default '0', ADD accepts int(6) NOT NULL default '0', ADD laston int(15) NOT NULL default '0'
Error: Duplicate column name 'realname'

Error performing MySQL command: ALTER TABLE ppc_iponline ADD uid INT(12) NOT NULL default '0', ADD referer VARCHAR(255) default NULL, ADD agent VARCHAR(100) default NULL
Error: Duplicate column name 'uid'

Error performing MySQL command: INSERT INTO ppc_settings VALUES (223,'Use Messaging System for PhotoPost alerts/notices?','usemsg','','yes',38,1)
Error: Duplicate entry '223' for key 1

Error performing MySQL command: INSERT INTO ppc_settings VALUES (224,'Use CAPTCHA images when verifying registration?','usecaptcha','Requires GD2 support!','no',4,8)
Error: Duplicate entry '224' for key 1

etc....then a bunch of these:

Error performing MySQL command: ALTER TABLE ppc_admingroups CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci
Error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci' at line

Error performing MySQL command: ALTER TABLE ppc_admlog CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci
Error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci' at line

Error performing MySQL command: ALTER TABLE ppc_adtypes CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci
Error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci' at line

And then this:

Error performing MySQL command: ALTER TABLE ppc_usergroups ADD free INT(3) NOT NULL DEFAULT '0'
Error: Duplicate column name 'free'

updating product tags...done.

Upgrade complete! To prevent users from modifying your PhotoPost database settings, please be sure to delete the upgrade.php file from your PhotoPost directory before continuing.

Chuck S · April 7th, 2008, 10:50 AM

duplicate errors are not a problem that just means it was ran before and doing what you did took care of the issue with trying to create tables with a collation that your mysql is not supporting although as stated mysql 4 should allow it.

DHewes · April 7th, 2008, 10:55 AM

I believe you responded before I saved my editted post. If the duplicates are not an issue, great. What about these though:

Error performing MySQL command: ALTER TABLE ppc_admingroups CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci
Error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci' at line

Error performing MySQL command: ALTER TABLE ppc_admlog CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci
Error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci' at line

Error performing MySQL command: ALTER TABLE ppc_adtypes CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci
Error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci' at line

Chuck S · April 7th, 2008, 11:01 AM

You dont need to worry about those thats where we try to change collation but again your server does not support it for some odd reason

DHewes · April 7th, 2008, 11:02 AM

Something is clearly not happy...going to the admin page has a whole bunch of these:

Warning: is_dir() [function.is-dir]: Stat failed for /home/{domain}/public_html/ppc/data///5/index.htm (errno=13 - Permission denied) in /home/{doimain}/public_html/ppc/adm-inc.php on line 682

Though his may be just a config issue once everything is working.

The site itself looks OK, no SQL errors -but no skin whatsoever, like forum integration is no longer working...going through the "new install" directions now to confirm everything is set as it should be.

DHewes · April 7th, 2008, 11:07 AM

Interesting...on the above error on the admin page it is adding a couple extra "//"'s to the data location, clearly wrong. I noticed that somehow there were three forward slashes on the configuration line for:

Full path to PhotoPost Classifieds data directory
Full path to the image files directory.

However, when I remove these (so that there are no slashes) and save - it always adds one back. So the error now still exists, only it has a double forward slash instead of a tripple, like this:

Warning: is_dir() [function.is-dir]: Stat failed for /home/{domain}/public_html/ppc/data//5/index.htm (errno=13 - Permission denied) in /home/{domain}/public_html/ppc/adm-inc.php on line 682

Chuck S · April 7th, 2008, 11:20 AM

/home/{domain}/public_html/ppc/data//

remove the extra slash off your data path and that will get rid of your error

You need to post a login and url if we are to assist with a style issue.

DHewes · April 7th, 2008, 11:40 AM

/home/{domain}/public_html/ppc/data//

The trailing slashes were both removed in options. Upon save a single trailing slash is added back, resulting in a double slash when I open the admin page and receive the above errors.

In regards to style, not sure why but it was not reading my integration config file. I re-uploaded and that part is working fine. Still having some rights issues in rebuilding thumbnails, but going through those settings now.

DHewes · April 7th, 2008, 12:22 PM

RE: /home/{domain}/public_html/ppc/data//

Through phpMyAdmin I removed the trailing slash in the global config settings. Not sure why it kept coming back, but no matter how I changed it on the settings page (even deleting the entire entry) it still added a single trailing slash. I do not know php well enough to find it in the code, but hey - hack SQL directly works until I do a save on the settings again.

At this point everything is up and running. One additional odd note...and I have experienced this before...

After the upgrade I went to database maintenance and ran the various checks/repairs (all but watermarks, since I do not use those).

One on of the numbered folders under the /data/ directory it modified the folder in such a way that it shows permissions of 666 and owned by the nobody user (all other numbered folders are 777 and owned by nobody) but I am now completely unable to access or modify this folder. Since this is a shared server I have to contact the host to have them reset permissions. This happens a couple times a year, but is very odd. Anyhow, I know how to fix it.

Otherwise, all is good. Thanks.

Chuck S · April 7th, 2008, 02:33 PM

Well you always need one trailing slash on the data path and there is a check for this.

Now on to folders we set folders to 777 when we make them not 666 and if your server is setting it to nobody then you may need to ask your host as this sounds like a host issue as to my knowledge if your server is setup whatever directories you make should be under your accounts name. we use a simple php command like so to create and change permissions on a directory

Code:

Content visible to verified customers only.