Bug #77993
closed
Pagetree filter: Duplicate root page displayed at opening a resulting page
0%
Description
Description:¶
If a normal backend user (not admin user), who has DB mounts, enters a searchterm in the pagetree filter and opens a resulting page, the root page will be displayed again under the subpages, which don't have any children. (see attachment)
Files
Updated by Riccardo De Contardi over 6 years ago
- Related to Bug #82041: Page tree gets duplicated after creating a new page in filter mode added
Updated by Riccardo De Contardi about 6 years ago
This issue is still present in version 8.7.10
Steps to reproduce
1) log in as an editor with a db mount point
2) filter the pagetree
3) add a page with drag and drop
RESULT:¶
You will see a tree of pages from the mount point; this tree is "false",as it goes away with refresh
On version 9.2.0-dev (latest master)¶
1) log in as an editor with a db mount point
2) filter the pagetree
3) add a page with drag and drop
RESULT:¶
it is not possible to add a page when the filter is active; this behavior is present even with an admin user (and no db mount points)
Updated by Ruslan Steiger about 6 years ago
When you look at the Network Tab in the Browser you will find that many XHR Request are fired (see attachement).
The First XHR-Request is fine. But all other XHR-Request that arrive after start the duplication of the filtered page tree.
I think it should only fire once. Somehow it keeps going and going.
Updated by Alexander Stehlik almost 6 years ago
- Has duplicate Bug #85028: TYPO3 V 7.6.20PageTree does not show subpages on specific page when in filtered mode added
Updated by Riccardo De Contardi over 5 years ago
Is this one still reproducible on the latest master (9.5.2-dev)?
I tried with (9.5.2-dev) and the behavior now seems correct.
Note:¶
Still reproducible with 8.7.20
Updated by Riccardo De Contardi over 5 years ago
- Status changed from New to Closed
Sorry, but I close this one as it only affects 8.7 and for now it won't be fixed as nobody will work on it.
If you think that this is the wrong decision or experience the issue on a newer TYPO3 version, please reopen it or open a new issue with a reference to this one.