TYPO3 Core

I have a similar problem.

If i use "sys_language_uid = ###REC_FIELD_sys_language_uid###" to get only the records in the correct language there are no records found by the suggest wizard anymore.

<type>select</type>
                  <foreign_table>my_extension</foreign_table>
                  <foreign_table_where>
                     AND my_extension.pid = 403 AND my_extension.sys_language_uid = ###REC_FIELD_sys_language_uid###
                  </foreign_table_where>

<wizards>
                        <suggest>
                            <type>suggest</type>
                        </suggest>
                    </wizards>

unfortunately there's only replacement of two markers in the foreign_table_where clause:

see t3lib/tceforms/class.t3lib_tceforms_suggest.php:

214                 //process addWhere
215             if (!isset($config['addWhere']) && $foreign_table_where) {
216                 $config['addWhere'] = $foreign_table_where;
217             }
218             if (isset($config['addWhere'])) {
219                 $config['addWhere'] = strtr(' ' . $config['addWhere'], array(
220                                                                             '###THIS_UID###' => intval($uid),
221                                                                             '###CURRENT_PID###' => intval($pageId),
222                                                                        ));
223             }

Is this issue resolved in TYPO3 6.2? Has anyone checked the behaviour in 6.2?

Nope, it's not. :(

When I use

foreign_table_where' => 'AND my_ext.sys_language_uid=0'

the wizard works fine. In my case i can deal with the hard coded 0.

Could you hand in that patch as described here: https://wiki.typo3.org/Contribution_Walkthrough_Tutorials