I recently switched over to pathauto for manual creating aliases and am in the process of re-indexing the site. When a Page Not Found error occurs from a page that used to have a different URL.

This error appears when a user uses a GSA or google to search a page and the old URL appears and when they hit the hyperlink this appears:
_______________________________

Page not found

* warning: pg_query() [function.pg-query]: Query failed: ERROR: value too long for type character varying(255) in /home/www/html/includes/database.pgsql.inc on line 139.
* user warning: ERROR: value too long for type character varying(128) query: INSERT INTO accesslog (title, path, url, hostname, uid, sid, timer, timestamp) values('Page not found', 'bodpodfaq', 'http://www.google.com/cse?cx=011858688371602201473%3Ay7urkrhxoqq&cof=FOR...', '129.255.166.186', 1, '1rm3gd3er3tcumbns4n04p9tu5', 340, 1251493102) in /home/www/html/modules/statistics/statistics.module on line 64.
* warning: pg_query() [function.pg-query]: Query failed: ERROR: value too long for type character varying(128) in /home/www/html/includes/database.pgsql.inc on line 139.
* user warning: query: INSERT INTO watchdog (uid, type, message, variables, severity, link, location, referer, hostname, timestamp) VALUES (1, 'page not found', 'bodpodfaq', 'N;', 4, '', 'http://icts.uiowa.edu/bodpodfaq', 'http://www.google.com/cse?cx=011858688371602201473%3Ay7urkrhxoqq&cof=FOR...', '129.255.166.186', 1251493114) in /home/www/html/modules/dblog/dblog.module on line 144.

The requested page could not be found.
___________________________________________

This error is reproducible any time a user attempts to hit a page that had a valid URL path before but has been renamed and not yet re-indexed.

For instance if you search on google, or on my site (www.icts.uiowa.edu) for BodPod FAQ and select (from google) the link that says:
BOD POD® | Institute for Clinical and Translational Science the error will occur.

I would have expect just the usual "Page Not Found" Message with out the long error string. Which is very confusing to users and renders in a large block of text on the page.

If a user attempts to find a page that simply does not exists, this error does not occur.
It always occurs in the situation described above.

I had noticed this error twice prior deploying pathauto but could not reproduce it and trace it to anything, now because of all of the pages Aliases being rewritten I was able to narrow this issue down.

Drupal 6.13
PhP 5.1.4
PostgreSQL 8.1.11
RedHat Apache/2.2.3 (Red Hat)
PhP Memory Limit 128M

Comments

dpearcefl’s picture

Priority: Critical » Normal
Status: Active » Postponed (maintainer needs more info)

is this still occurring with a current version of Drupal v6?

dpearcefl’s picture

Priority: Normal » Major
Status: Postponed (maintainer needs more info) » Active

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.