Project

General

Profile

Actions

Bug #80243

closed

TYPO3/CMS/Backend/ContextMenuActions only respects PageTree

Added by Commerce Team over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2017-03-12
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Currently TYPO3/CMS/Backend/ContextMenuActions uses methods of the PageTree directly like for example.

ContextMenuActions.disableRecord = function (table, uid) {
top.TYPO3.Backend.ContentContainer.setUrl(
top.TYPO3.settings.RecordCommit.moduleUrl + '&data[' + table + '][' + uid + '][hidden]=1&prErr=1&redirect=' + ContextMenuActions.getReturnUrl()
);
top.TYPO3.Backend.NavigationContainer.PageTree.refreshTree.defer(500);
};

This prevents custom trees from being refreshed after an element was disabled.

There needs to be a solution on how to refresh custom trees.

Actions #1

Updated by Tymoteusz Motylewski over 7 years ago

  • Status changed from New to Needs Feedback

Hi
I'm pretty certain I've used the same code as it was before.
Did it work in v7? Can you send me some steps to reproduce the issue in v7 (working) and v8 (not working)?
I don't have any example of the custom tree right at hand, so without an example I will not be able to fix it.

Actions #2

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Needs Feedback to Closed

This issue seems no more reproducible on latest master (tested with styleguide > TCA demo/elements select/ renderType=selectTree - if you disable a page in the pagetree, the custom tree is also updated).

Moreover, more than 90 days passed without feedback, so I think it is safe to close it for now.

If you think that this is the wrong decision or experience the issue again, please reopen it or open a new issue with a reference to this one. Thank you.

Actions

Also available in: Atom PDF