Bug #16190
closed
requestUpdate does not work on selectboxes (group-fields)
Added by Stephan Petzl over 17 years ago.
Updated almost 11 years ago.
Category:
Backend User Interface
Description
when i try to set requestUpdate on group-fields in TCA, i get no page-reload after modifying the field.
i tried to debug through class.t3lib_tceforms.php and it seams that the parameter "$PA['fieldChangeFunc']['alert']" which is set in line 870, is not passed through to the method "dbFileIcons()" which renders the selectbox and icons.
(issue imported from #M6046)
Files
my Typo3 version is 4.1.0. i have checked the current version of typo3 (4.1.2)
> the bug has not been fixed so far
> seams like a bugfix would not conflict with the version 4.1.2
its quite a mess now because i forgot a edit in the first version of the edited file (class.browse_links_edit.php). so i uploaded another version with diffs. the first version could be deleted (looks like i have no rights to do so)
the uploaded bugfix supplys you with a ext_localconf.php, a XCLASS and a hook-file which have to be integrated into an extension before they take affect on your typo3.
OK, I've deleted all old/unused files attached to this bug.
From the core list:
what's the status on this?
The status is that we have found that the issue is a general problem and
therefore deserves a general solution as well. The problem is that in
general onChange functions are not executed when the TCEForms values are changed by a popup wizard like the element browser.
The patch that we have available so far only solves one part of the
problem in a kind of hardcoded fashion, so it's not a feasible solution yet.
So this RFC is dropped until someone comes up with a proper solution.
cheers
Ingmar
- Status changed from New to Needs Feedback
- Target version deleted (
0)
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by