Bug #81102
open
BackendUtility::setUpdateSignal not always triggered instantly
0%
Description
- Problem
Triggering setUpdateSignal from a DataHandlerCmdHook does not always execute the triggered Signals in the Frontend of the Backend.
- Steps to reproduce:
- Register a DataHandler Hook
- Create a page via D&D
- Change Title of page in pagetree (by double clicking)
- what i expected
- execution of update signals directly after ajax operation
- what happened
- execution of signal was triggered with next loaded module
Updated by Frank Nägler almost 7 years ago
- Status changed from New to Needs Feedback
I think this should finally be solved with master / v9, but please check again if this solves your issue.
Updated by Frank Nägler almost 7 years ago
Any news? If not I will close this issue.
Updated by Kay Strobach almost 7 years ago
Frank Naegler wrote:
Any news? If not I will close this issue.
So you consider this a missing feature no worth a bugfix? If so ok, will check with master, if the problem still exists there.
Any idea, which commit fixed it in master?
Thx.
Updated by Frank Nägler almost 7 years ago
Benni told me, that it is fixed in master, but I have no commit, sry.
Updated by Frank Nägler over 6 years ago
@Kay Wienöbst: Can you confirm, that is is fixed in master and/or v8 ?
Updated by Kay Strobach over 6 years ago
@frank still a problem in v8, need to check it in master though ... will do in the next days
Updated by Alexander Opitz over 6 years ago
- Status changed from Needs Feedback to New
Updated by Frank Nägler over 6 years ago
- Category changed from Backend JavaScript to DataHandler aka TCEmain
After checking this issue again, I guess I now understand your issue, but I am not sure if we can fix this behavior.
I will move the issue to the DataHandler category.