TYPO3 Core

I just hit into this one.

Tried applying the v2 patch in the core list, but it did not apply on latest 4.4.4. I will try to see what was wrong with the hunk 3 when I have more time and will send an updated patch to the core list including my +1 on testing (if it tests well).

Hey Lars, do you have an updated version of this patch that applies to 4.4.4?

Not right now, but I will try to get one made in the nearest future.

OK, all apologies if what I'm doing is wrong but i need that feature and looking at the proposed patch and 4.4 code, I made a quick revision of the patch which seems to work for me.

bump Just encountered this problem and I think suggest in flexform would be awesome. Btw, this is related to #0012399.

Patch set 1 of change Ia90e0e93b9aaacd42f76e381c0b0923bb0d37356 has been pushed to the review server.
It is available at http://review.typo3.org/4252

this patch doesn't fix everything but the direction is at least correct.

at least the following settings did not work for me.
Example:

<settings.categories>
    <TCEforms>
        <label>LLL:EXT:news/Resources/Private/Language/locallang_be.xml:flexforms_general.categories</label>
        <config>
            <type>select</type>
            <foreign_table>tx_news_domain_model_category</foreign_table>
            <foreign_table_where> AND (tx_news_domain_model_category.sys_language_uid = 0 OR tx_news_domain_model_category.l10n_parent = 0) ORDER BY tx_news_domain_model_category.sorting</foreign_table_where>-->
            <size>10</size>
            <autoSizeMax>20</autoSizeMax>
            <minitems>0</minitems>
            <maxitems>20</maxitems>
            <wizards>
                <suggest>
                    <type>suggest</type>
                </suggest>
            </wizards>
        </config>
    </TCEforms>
</settings.categories>

doesn't work and needs an additional setting

<allowed>tx_news_domain_model_category</allowed>

furthermore the foreign_table_where is not considered!

Patch set 1 of change I8d25594ba0376f7d35aa7f52860cad975014cc0a has been pushed to the review server.
It is available at http://review.typo3.org/5703

Why should we wait for 4.7 to get this fix in? Worked together with Chetan on this one and it works fine in some client projects so far, so I don't see a reason to wait. Pushed it to Gerrit: https://review.typo3.org/5625

Patch set 2 of change I8d25594ba0376f7d35aa7f52860cad975014cc0a has been pushed to the review server.
It is available at http://review.typo3.org/5703

Patch set 2 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/4252

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/5703

Patch set 1 for branch TYPO3_4-6 has been pushed to the review server.
It is available at http://review.typo3.org/7133

Patch set 1 for branch TYPO3_4-5 has been pushed to the review server.
It is available at http://review.typo3.org/7134