Installed new path_redirect-6.x-1.0-beta6 version and got this error when I tried edit a node:

"user warning: Unknown column 'path' in 'where clause' query: SELECT rid FROM path_redirect WHERE path = 'titanovye-dokazatelstva-vnezemnoi-krasoty-medison' LIMIT 0, 1 in /home2/madfanbo/public_html/site/modules/pathauto/pathauto.inc on line 74."

Any fix?

Comments

dave reid’s picture

Status: Active » Closed (duplicate)

See #647812: Update to code required for Path_Redirect compatability. Latest betas are undergoing major changes. Stick with beta5 until our official 1.0.

drahman’s picture

Dave, excuse me if this is not the right place to post this request. I am not a developer and I am relatively new to Drupal.org.

Is it possible to have a warning (like on the module's main page http://drupal.org/project/modules?text=path%20redirect) on the release notes page (http://drupal.org/node/648776)? The reason being that in the Available Updates section of the Admin there are two links when a node has an update available: Download and Release notes. The Release notes linked page does not have the warning. Had I seen that warning, I would not have installed the update.

okokokok’s picture

I'm getting them same error on an openatrium site.

Is it possible to downgrade at all, without other issues appearing?

Drush will update to beta6 automatically on most sites, so it would be best to rerelease beta5 as beta7 and leave beta6 for dev.

hefox’s picture

I agree with guaka that it'd be best to keep the two modules in synch for compatibility for stable releases; path auto and path redirect are so often used togeather it's going to be troubleing a lot of users (and it seems it is, based on the other issue),

Most people are going to be see an non-dev update and update like update status suggests they do, both newer and older users (I'm a big user of 'drush update', though I usually read the release notes first).

maddentim’s picture

Ditto with hefox and guaka on this issue. My general process is when something shows up on the available updates page I usually check the release notes and the readme.txt/install.txt file in the actual package, but not the project page. I don't recall seeing this warning and have now upgraded my sites with this new beta version . I am not sure what the best thing to do is now... I don't know how to downgrade. I suppose I should disable the modules, then uninstall, then install beta5 again. bummer. i hate to waste time...

dave reid’s picture

I'll put the same warning on the release notes from the project page.

@maddentim: Upgrade to pathauto 6.x-1.x-dev. That should fix it.

esbon’s picture

Hi, any word on how to downgrade. The table was changed on module upate and I did not backup the table.
Thanks

betancourt’s picture

I got the same problem here. Any help|?

Would it work if I disable and uninstall the latest version and then install again the beta 5? So I get again the old table format?

sir-arturio’s picture

@betancourt: Yes, if you don't have anything valuable stored to the path_redirect table, you can just revert back to beta 5 (uninstall beta6 & install beta 5) but it WILL destroy the stored data.

@esbon and others willing to downgrade
*Please backup your database before doing anything and test the modification in a non-production environment.* :)

The difference between beta5's and beta6's table structure is minimal: just one renamed field (and an unique key bound to it). I reversed the steps of the new update_hook and ran the following SQL clauses (PLEASE REPLACE THE [charset], [collation] and [database name] WITH YOUR OWN VALUES):
----------------------------------------------------------------------------------------
ALTER TABLE `path_redirect` DROP INDEX `source_language`
ALTER TABLE `path_redirect` CHANGE `source` `path` VARCHAR( 255 ) CHARACTER SET [charset] COLLATE [collation] NOT NULL
ALTER TABLE `[database name]`.`path_redirect` ADD UNIQUE `path_language` ( `path` , `language` )
----------------------------------------------------------------------------------------

This should change the table's structure from beta6 to beta5 without losing any data.

Hans Lodder’s picture

Dave,

I get this error with OpenCalais.

Could the solution possibly be "Pathauto 6.x-2.x-dev (2009-Dec-06)", leaving "Path redirect 6.x-1.0-beta6" unlatered? Any consequences?

Regards, hans

Josie_h’s picture

Hi,

I'm a non-techy user, so I don't honestly understand some of what has been said. However, I have just run the updates that Drupal recommended and I have this same error in my logs.

Could someone please tell me (in easy terms) how to recover from it.

Many thanks.

[e]I thought I should add, I don't really understand the 'duplicate thread' and I can't add to it because it is closed. Appreciate any help.[/]

Josie_h’s picture

Status: Closed (duplicate) » Active
Josie_h’s picture

Not to worry, I fixed it myself.

hefox’s picture

Status: Active » Closed (duplicate)

Duplicate means there's already a thread addressing this and should post in that thread instead

houstonaplus’s picture

your script does not work. I get a new error after applying it.

elijah lynn’s picture

I am using Path Redirect with the latest PathAuto Dev and I am getting this error. I had originally installed Beta 6 but then read the page and it said to use Dev. I never tested it with Beta6 and went straight to Dev so I cannot say if this error was there with beta6.

Update: Luckily I just installed path_redirect so I uninstalled it for now, I haven't seen anymore errors since.

petrelharp’s picture

Upgrading to Pathauto 6.x-2.x-dev (2009-Dec-06) and leaving path redirect untouched fixed this problem for me.

rossmerriam’s picture

This also worked for me, Thanks!

cookiesunshinex’s picture

Upgrading to Pathauto 6.x-1.x-dev (2009-Dec-04) and leaving path redirect untouched fixed this problem for me.

Note, I used Pathauto 6.x.-1.x-dev (2009-Dec-04), not the 6.x.-2.x-dev (2009-Dec-06) as the previous user in #17 used.
Pathauto 6.x.-1.x-dev (2009-Dec-04) is linked to on the main Pathauto projects page, but you can also find a link to a page where 6.x.-2.x-dev exists.

bartezz’s picture

Upgrading to Pathauto 6.x-1.x-dev (2009-Dec-04) and leaving path redirect untouched fixed this problem for me.

Seems to fix the problem for me as well...
Cheers

libeco’s picture

I can also confirm that updating to Pathauto 6.x-1.x-dev (2009-Dec-04) removed the error.

elijah lynn’s picture

In response to #16 - I had Pathauto and Path Redirect mixed up. Previously, I had read the project page and installed the DEV of Path Redirect and not Pathauto like it said and that is why I was getting the error still.

I now have pathauto-6.x-1.x-dev installed with path_redirect-6.x-1.0-beta6 and everything works great!

I just wanted to clarify that.

djmy’s picture

i as well had the unknown path clause issues but i did what #17 petrelharp mentioned and upgraded just Pathauto 6.x-2.x-dev (2009-Dec-06) and my redirect works! Thanks petrelharp!

greggles’s picture

Hi folks.

It may be true that upgrading to Pathauto 6.x-2.x-dev fixes this problem, but:

  1. The best branch to stick with is 6.x-1.x, so please use 6.x-1.x-dev instead
  2. Beyond that, we should have a new release of Pathauto shortly as 6.x-1.3 stable so once that is released it is the one to stick with.

6.x-2.x-dev isn't bad, but it isn't as stable as the 6.x-1.x-dev branch.

I'm locking comments here because I want people to see this message and this message alone. If someone needs to add more, contact me and I can open it back up.