Project

General

Profile

Actions

Bug #93043

closed

Link browser in the redirect module goes blank when trying to expand a nod in the page tree

Added by Karina Helena Reinhardt over 3 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2020-12-09
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

The issue occurs in 9.5.22 and 9.5.23

Steps to reproduce:
1. Open redirects module and add a new redirect
2. Open the link browser to set the target
3. Try to expand a nod in the page tree

I get the following error message in Firefox Inspector:
"The character encoding of the plain text document was not declared. The document will render with garbled text in some browser configurations if the document contains characters from outside the US-ASCII range. The character encoding of the file needs to be declared in the transfer protocol or file needs to use a byte order mark as an encoding signature."

Chrome reports 404 Page not found.

The URL of the blank page doesn't work when it's url-encoded, but it works when decoded.


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #91409: Using pagebrowser in redirects module results in error 404Needs Feedback2020-05-14

Actions
Actions #1

Updated by Karina Helena Reinhardt over 3 years ago

  • Related to Bug #91409: Using pagebrowser in redirects module results in error 404 added
Actions #2

Updated by Karina Helena Reinhardt over 3 years ago

Our setup is Windows/IIS 8.5 (Windows Server 2012 R2). Occurs in Firefox, Chrome, Edge, Opera.

Actions #3

Updated by Riccardo De Contardi about 3 years ago

  • Category set to Backend User Interface
Actions #4

Updated by Benni Mack over 2 years ago

  • Status changed from New to Needs Feedback

Hey Karina,

thanks for your report and sorry for the late reply!

can you check this with the latest v11 versions? We've overcome a lot of limitations in the link browser in TYPO3 v11, which were bad from an architectural point of view.

Actions #5

Updated by Christian Kuhn about 2 years ago

  • Status changed from Needs Feedback to Closed

Hey, I hope it's ok to close here since we reworked the tree handling in v11 heavily and are pretty certain such scenarios don't pop up anymore.

Please create a fresh issue in case we missed something.

Actions

Also available in: Atom PDF