Bug #66312
closedphp_tree_stop not working in ExtJs pagetree
100%
Description
In the page properties (tab Behaviour) is the option "Stop Page Tree". According to the CSH information this should stop the pagetree from expanding on this node. Instead there should be a red [+] icon which will load that node as a temporary tree mount.
In the ExtJs pagetree this isn't working. In the link browser the feature still works.
The new (jQuery based) page tree is a good opportunity to bring the feature back.
Updated by Gerrit Code Review over 9 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41496
Updated by Gerrit Code Review over 9 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41496
Updated by Susanne Moog over 9 years ago
- Target version changed from 7.4 (Backend) to 7.5
Updated by Gerrit Code Review about 9 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/41496
Updated by Gerrit Code Review about 9 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/41496
Updated by Gerrit Code Review about 9 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/41496
Updated by Benni Mack about 9 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 53bb61d360d587d31ff38d76bae2cb3459083fbf.
Updated by Gerrit Code Review about 9 years ago
- Status changed from Resolved to Under Review
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/44714
Updated by Mathias Schreiber almost 8 years ago
- Status changed from Under Review to Resolved
This issue popped back up, due to the 6.2 patch that was abandoned later