Bug #78460: requestUpdate property for form input fields - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Actions

Copy link

Bug #78460

open

requestUpdate property for form input fields

Added by Sergio Catalá over 7 years ago. Updated about 2 years ago.

Status:

New

Priority:

Could have

Assignee:

Category:

FormEngine aka TCEforms

Target version:

Start date:

2016-10-27

Due date:

% Done:

Estimated time:

TYPO3 Version:

PHP Version:

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

For opened form input fields in the backend, the TCA property requestUpdate (https://docs.typo3.org/typo3cms/TCAReference/Reference/Ctrl/Index.html#requestupdate) is not working.

Is this a bug or a feature request?
If this is not allowed, is there a special reason for that?

Related issues 1 (0 open — 1 closed)

Related to TYPO3 Core - Story #69712: Further FormEngine development

Closed

2011-12-01

Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Anja Leichsenring over 7 years ago

could you please provide steps to reproduce? I can't get your problem from your description. RequestUpdate works for me, for example the CType of tt_content implements that behaviour.

Actions

Copy link

Updated by Sergio Catalá over 7 years ago

I am using the next code through flux extension:

        <flux:form options="{group:'Custom elements'}" 
                   id="headerstage" 
                   description="Teaser element">
            <flux:form.sheet name="content">
                <flux:field.input name="linkpage" requestUpdate="1">
                    <flux:wizard.link />
                </flux:field.input>
                <flux:field.input name="linktext" maxCharacters="50" displayCond="FIELD:linkpage:>:0"/>
            </flux:form.sheet>
        </flux:form>

When the linkpage field looses the focus, the backend should be reloaded, to allow the evaluation of the displayCond in the other field.

Actions

Copy link

Updated by Anja Leichsenring over 7 years ago

Status changed from New to Needs Feedback

no idea about flux, sorry. RequestUpdate is not available for flexforms, too.

Have a look at https://wiki.typo3.org/Extension_Development,_using_Flexforms#Display_conditions_and_dynamic_reloading_of_form, maybe that helps.

Actions

Copy link

Updated by Nicole Cordes over 7 years ago

Status changed from Needs Feedback to Closed

Hi Sergio,

requestUpdate is an option within your tables CTRL section. By reading the provided flux code, this means, flux has to change the TCA on the fly which doesn't work because TCA is cached. IMHO this is a problem of flux not using the TYPO3 TCA api correctly. Please contact the support of EXT:flux.

Closing this issue for now. If you have another way how to reproduce your problem, please report to another ticket. Thank you.

Actions

Copy link

Updated by Christian Kuhn over 7 years ago

Status changed from Closed to New

Actually, requestUpdate is available as "onChange=reload" within flex form fields. And yes, InputTextElements do not handle requestUpdate / onChange at all, I stumbled upon that during my current FormEngine patch.

My patch resolves this "requestUpdate does not exist in flex forms" issue by removing it from 'ctrl' section and allowing "onChange=reload" on all fields, also outside of flex forms.

So, the issue with the input fields is confirmed, and this area needs some JS side works anyway and the issue could be solved along the way.

I'll set a "Related" flag in my patch to point to this issue.

Actions

Copy link