It seems that the latest version of Path Redirect has made some changes that affect the schema and API. These changes lead to errors like this from Pathauto:

user warning: Unknown column 'path' in 'where clause' query: SELECT rid FROM path_redirect WHERE path = 'content/dummy-page' LIMIT 0, 1 in /sites/all/modules/pathauto/pathauto.inc on line 74.

I've attached a patch that I think will fix the problem. Needs testing.

CommentFileSizeAuthor
pathauto-path-redirect-update.patch1.08 KBjtsnow

Comments

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented
Status: Needs review » Closed (duplicate)

This has already been fixed in 6.x-1.x-dev.
#647812: Update to code required for Path_Redirect compatability

alexgreyhead’s picture

alexgreyhead commented

jtsnow, thank you very much for that - you rescued me from a bit of a hole there!

@Dave Reid, I'm guessing the schema change was sprung on the pathauto folks (is that you, or you plus a team, or someone entirely different...?); as this has no doubt surprised a few people who weren't expecting to see error messages like this, is there anything you or the community can do to try to avoid this happening in future? I'd be happy to (try to) help test any code you'd like checked out...

dave reid’s picture

dave reid
he/him
Primary language English
Location Nebraska USA
commented

@alexharries: I didn't spring this on them (I think I warned greggles) but there's not much they can do. We had it fixed within a day I think in the 6.x-1.x dev release of pathauto. Its just that I like to release quicker than pathauto does instead of waiting a while for a new release. The other problem is that pathauto was accessing the data in path_redirect directly from the database instead of using any kind of APIs, which is going to cause problems like this down the road. Now that its using the API functions, its much easier for me to work in backwards-compatibility from within path_redirect.

And of course, I'll remind people that path_redirect is still in 'beta' so always take caution when upgrading and follow backup procedures.