Bug #81102

BackendUtility::setUpdateSignal not always triggered instantly

Added by Kay Strobach about 2 years ago. Updated 12 months ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
-
Start date:
2017-05-02
Due date:
% Done:

0%

TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
Sprint Focus:

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

History

#1 Updated by Frank Naegler over 1 year 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.

#2 Updated by Frank Naegler over 1 year ago

Any news? If not I will close this issue.

#3 Updated by Kay Strobach over 1 year 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.

#4 Updated by Frank Naegler over 1 year ago

Benni told me, that it is fixed in master, but I have no commit, sry.

#5 Updated by Frank Naegler over 1 year ago

@Kay: Can you confirm, that is is fixed in master and/or v8 ?

#6 Updated by Kay Strobach over 1 year ago

@frank still a problem in v8, need to check it in master though ... will do in the next days

#7 Updated by Alexander Opitz about 1 year ago

  • Status changed from Needs Feedback to New

#8 Updated by Frank Naegler 12 months 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.

Also available in: Atom PDF