Issue Bug New Orphaned

#81102BackendUtility::setUpdateSignal not always triggered instantly

Kay Strobach 05/02/17, 10:08 updated 06/26/18, 22:45

Description

  1. Problem

Triggering setUpdateSignal from a DataHandlerCmdHook does not always execute the triggered Signals in the Frontend of the Backend.

  1. Steps to reproduce:
  • Register a DataHandler Hook
  • Create a page via D&D
  • Change Title of page in pagetree (by double clicking)
  1. what i expected
  • execution of update signals directly after ajax operation
  1. what happened
  • execution of signal was triggered with next loaded module

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] BackendUtility::setUpdateSignal not always triggered instantly Resolves: #81102 Releases: main