Project

General

Profile

Actions

Bug #54703

closed

Linkvalidator doesn`t handle RTE-inline Image correct

Added by Henrik Ziegenhain about 10 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Linkvalidator
Target version:
-
Start date:
2014-01-02
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
5.3
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

Description

The Linkvalidator is not able to handle Images inside the RTE-field correct.

The Report says, that there are several pages not found:

http://www.example.com/index.php?id=678    - Page (678) does not exist.

The "Page" 678 is the uid of the inline image:

<img src="http://www.example.com/fileadmin/user_upload/path/file.jpg" data-htmlarea-file-uid="678" data-htmlarea-file-table="sys_file" ... />

This behavior is also reproducable on clean installations of 6.1.7.

Steps to reproduce:
1. Insert an image inside the htmlareaRTE.
2. Switch to html-view and check, if the data-htrmlarea-file-uid attribute is there with an ID
3. Save
4. Run Linkvalidator on this site
5. Get an error like the one above, saying the page (1234) doesn`t exit.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #49286: Skip validation of RTE filelinkClosed2013-06-20

Actions
Actions #1

Updated by Philipp Gampe about 10 years ago

  • Target version deleted (next-patchlevel)
  • Complexity set to medium

There are more problems with linkvalidator and FAL. I suggest to use the linkvalidator mainly to check for external links in 6.x.

Actions #2

Updated by Henrik Ziegenhain about 10 years ago

Sorry, but I can’t fix this. If someone could provide a patch, I will test it on our installations.

Actions #3

Updated by Riccardo De Contardi almost 9 years ago

  • Status changed from New to Closed

I close this, as I've done the test reported in the ticket description and the bug is not present on TYPO3 6.2.12 (also, IMHO this is a duplicate of #49286, marked as resolved)

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF