Closed (fixed)
Project:
Pathauto
Version:
7.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 May 2013 at 15:57 UTC
Updated:
7 Feb 2026 at 18:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave reidI'm not sure what you mean. That issue was fixed *by adding* the try/catch. The real issue that needs to be solved is #1003788: PostgreSQL: PDOException:Invalid text representation when attempting to load an entity with a string or non-scalar ID which is still pending for core.
Comment #2
dave reidI see now the actual link in the @todo was confusing. It should have linked to #1003788: PostgreSQL: PDOException:Invalid text representation when attempting to load an entity with a string or non-scalar ID, not the internal issue in Pathauto.
http://drupalcode.org/project/pathauto.git/commit/655e451
Comment #3
pancho[edit:]
Oops, I'm sorry - didn't reload the page.
I also should have read that issue.
Please ignore this patch.
Comment #5
panchoSo leaving the try... catch in.
But in case an exception has been caught, we don't want to return FALSE but at least continue checking the filesystem. Fixed that.
I also did some more rewording in the doc, because it didn't reflect the fact that we're checking both the menu system and the filesystem.
Also, the wording "Verify if the given path is a valid menu callback" is misleading. It's not like we want to make sure that it already exists, rather we want to make sure it doesn't.
IMHO, the function should also be renamed to something like _pathauto_path_exists() or _pathauto_check_path(), but I did not yet roll that in.
Hopefully, the testbot is able to apply this one correctly - don't know what happened to the other patch.
Comment #7
panchoAh okay, now it should be fine. For explanation, see #5.
Escaping the filesystem check makes this a bug.
Comment #10
mably commentedComment #12
mably commented