TYPO3 Core

Hello Peter,
###PAGE_TSCONFIG_IDLIST### is replaced with the page tsconfig content for the right hand part of the select field. The select field's right input that shows all the records correctly and finds all the records because it can replace the markers in the foreign_table_where part of my FlexForm DS.

If I select any of the records they get saved in the db when I save the form, but upon reloading the left hand input that makes up the select element doesn't display the selected records that have PIDs = to those that I set in tsconfig with PAGE_TSCONFIG_IDLIST. The hard coded items in the items array and those records in the storage folder show up ok.

After debugging parts of TYPO3 when TYPO3 creates the form field I discovered that when creating the left input for the select field, the $field argument passed to selectAddForeign() is empty, and without $field being set to pi_flexform the str_replace call in exec_foreign_table_where_query() fails:

$fTWHERE = str_replace('###PAGE_TSCONFIG_IDLIST###', 
$GLOBALS['TYPO3_DB']->cleanIntList($TSconfig[$field]['PAGE_TSCONFIG_IDLIST']), 
$fTWHERE);

"(mind that IMO you are in danger to end up with invalid SQL if one of them is not filled)?"

No, no, it is ok. Storgae PID is always set and even if PAGE_TSCONFIG_IDLIST is not set in the tsconfig it becomes 0 in the sql clause.

I don't have any special function creating the label.

the thing with sys_language.uid doesn't effect this.

if I make the foreign_table_where clause this:

<foreign_table_where> AND (tx_sbportfolio_categories.sys_language_uid=0 || (tx_sbportfolio_categories.sys_language_uid>0 AND tx_sbportfolio_categories.l10n_parent=0)) ORDER BY tx_sbportfolio_categories.title ASC</foreign_table_where>

Then they selected records show up ok, even if they are not in the storage folder, but stored in the PIDs set in tsconfig.

THis is really just a problem with the left input field in the select field, because $field is empty, it can't convert the markers in exec_foreign_table_where_query().

Having looked a bitmore at this, I see in the function renderRecord_SW() in class.t3lib_transferdata.php that in the functions help declaration it mentions that $field is empty for flex forms.

    /**
     * Function with the switch() construct which triggers functions for processing of the data value depending on the TCA-config field type.
     *
     * @param    string        Value to process
     * @param    array        TCA/columns array for field    (independant of TCA for flexforms - coming from XML then)
     * @param    array        TSconfig    (blank for flexforms for now)
     * @param    string        Table name
     * @param    array        The row array, always of the real record (also for flexforms)
     * @param    string        The field (empty for flexforms!)
     * @return    string        Modified $value
     */
    function renderRecord_SW($data, $fieldConfig, $TSconfig, $table, $row, $field) {

I think this is the cause of the problem.

I believe this is a bug because the right hand part of the select field can convert these markers and any records that I select are saved ok in the flexform DS. It is just when the form reloads, or the record is first opened that the problem occurs.

It doesn't say why $field is empty for FF, why is this so? It's need to be set for any of the markers in exec_foreign_table_where_query() to be converted.

Same Problem, but simpler Example:

<address>
<TCEforms>
<label>LLL:EXT:test/pi1/locallang.xml:tt_content.flexform.address</label>
<config>
<type>select</type>
<foreign_table>tt_address</foreign_table>
<foreign_table_where>AND tt_address.pid=###PAGE_TSCONFIG_ID### ORDER BY tt_address.name</foreign_table_where>
<size>4</size>
<minitems>1</minitems>
<maxitems>10</maxitems>
</config>
</TCEforms>
</address>


A simple Selectbox with maxitems=1 works fine, this problem only occurs on Multi-Select-Fields.

I can confirm that this bug is still present in 4.7.5.

Lars Houmark wrote:

I can confirm that this bug is still present in 4.7.5.

I can confirm that this bug is still present in 6.1

May this bug/feature request may have to do with my issue #50785 regarding using "REC_FIELD_"-Markers for accessing FlexForm-Values within foreign_table_where?

I think so... I fixed the problem by using, itemsProcFunc. Maybe you can use it and modify it to your needs.

I can confirm this behaviour is still the same in TYPO3 6.1.3. Saving the form leads to lost record relations.
In my case it's exactly the same thing Stephen Bungert described. I also consider it as a bug.

I confirm this behaviour happens in 6.2.1 too.

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/30781