If i call:
http://www.test.dev/de/node/22135
in the Browser it works fine!

But if i call the same node with the wrong language in the URL:
http://www.test.dev/en/node/22135

there is an PDOException:
"PDOException: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')) AND (ml.hidden = '0') ORDER BY ml.weight ASC' at line 2: SELECT ml.*, m.*, ml.weight AS link_weight FROM {menu_links} ml LEFT OUTER JOIN {menu_router} m ON m.path = ml.router_path WHERE (ml.link_path IN ()) AND (ml.hidden = :db_condition_placeholder_0) ORDER BY ml.weight ASC; Array ( [:db_condition_placeholder_0] => 0 ) in _taxonomy_menu_trails_process() (line 171 of /www/sites/www.test.dev/sites/all/modules/contrib/taxonomy_menu_trails/taxonomy_men...). The website encountered an unexpected error. Please try again later."

Might not be an Taxonomy Menu Trails Bug, but on a D6 Site calling a Node with the wrong language worked for me - thats why i put it here.

Any idea? Thanks in advance!

CommentFileSizeAuthor
#1 taxonomy_menu_trails-1794430-1.patch625 bytesDmitriy.trt
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Bernhard Uhl’s picture

Issue summary: View changes

PDOException: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')) AND (ml.hidden = '0') ORDER BY ml.weight ASC' at line 2: SELECT ml.*, m.*, ml.weight AS link_weight FROM {menu_links} ml LEFT OUTER JOIN {menu_router} m ON m.path = ml.router_path WHERE (ml.link_path IN ()) AND (ml.hidden = :db_condition_placeholder_0) ORDER BY ml.weight ASC; Array ( [:db_condition_placeholder_0] => 0 ) in _taxonomy_menu_trails_process() (line 171 of /www/sites/www.test.dev/sites/all/modules/contrib/taxonomy_menu_trails/taxonomy_men...).
The website encountered an unexpected error. Please try again later.

Dmitriy.trt’s picture

Version: 7.x-2.3 » 7.x-2.x-dev
Status: Active » Fixed
FileSize
625 bytes

Yes, I'm able to reproduce the problem with enabled option "Allow only terms with the current language". Fix committed and will be released in 7.x-2.4. Please, wait for the next 7.x-2.x-dev (released today or later) or apply attached patch to the stable version.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

changed