I just upgraded from 4.2 release to 4.3.1. I ran into the table url_alias not being found issue that a few people have mentioned. The workaround is pretty easy:
Environment: i was upgrading from 4.2 to 4.3.1
Symptom: when you run update.php to upgrade it complains about the table url_alias not being found.
Fix:
Open database/database.mysql (in my case, not sure if this error shows up on non-mysql configs) and copy the command for the url_alias section, or just copy this:
CREATE TABLE url_alias (
pid int(10) unsigned NOT NULL auto_increment,
src varchar(128) NOT NULL default '',
dst varchar(128) NOT NULL default '',
PRIMARY KEY (pid),
UNIQUE KEY dst (dst),
UNIQUE KEY src (src)
) TYPE=MyISAM;
open your mysql database with something like:
- mysql -u drupaladminname -p drupaldbname
- paste in the command above
- you should get a successful reply, if not, check your syntax
- \q quits the interactive session
now just run update.php again and it should work. i got a couple small errors in the update log, but nothing looked serious and the portal appears to be running fine.
Now I've got to re-port a custom authentication module that i wrote, but otherwise the upgrade went very well.
Good job, all.