Project

General

Profile

Actions

Bug #27214

closed

Linkvalidator checks wrong links (related to DAM)

Added by Bernhard Eckl almost 13 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Linkvalidator
Target version:
-
Start date:
2011-06-05
Due date:
% Done:

0%

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

Description

I followed the instructions on http://forge.typo3.org/issues/13423 (TSConfig setting and mailtemplate) and executed the linkvalidator from the backend. But then I see there are lots of links checked like this: http://www.domain.tld/index.php?id=DAMID. Of course that link doesn’t exist because there is no page which has the same ID of the DAM ID of the document which is linked in reality. The link should normally link to a DAM file (like http://www.domain.tld/fileadmin/user_uplad/file.pdf).


Files

linkvalidator-dam.gif (91.6 KB) linkvalidator-dam.gif Bernhard Eckl, 2012-05-23 17:13

Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #13423: Add DAM section to the manualClosed2011-02-28

Actions
Actions #1

Updated by Michael Miousse almost 13 years ago

This bug report should go on the dam bug list not on linkvalidator bug list

But what is the dam version you use?
migth be related to that

Actions #2

Updated by Bernhard Eckl almost 13 years ago

DAM version is 1.2.2 (newest in TER)
Should I create a new issue at the DAM project?

Actions #3

Updated by Philipp Gampe over 12 years ago

  • Status changed from New to Needs Feedback
  • TYPO3 Version set to 4.5

Yes please check with DAM project first.

Actions #4

Updated by Philipp Gampe over 12 years ago

Any progress here? Does it work now? Is it a dam bug?

Actions #5

Updated by Bernhard Eckl over 12 years ago

Hm, Sorry I forgot to check the DAM project. But just right now I found this one:
http://bugs.typo3.org/view.php?id=17379

Is this related to that issue?

Actions #6

Updated by Philipp Gampe over 12 years ago

I think, but I disagree with Dan. I think this information should be added to DAM manual, because the Core can not add instructions for every extension with provides linkvalidator tasks.
I know that there will be not many, but it is the wrong approch. The extension should explain in its manual what it does and how you can use it.
That is what an extension manual is for.

Actions #7

Updated by Bernhard Eckl over 12 years ago

I agree. But didn't you want to post this at the other issue?

Actions #8

Updated by Bernhard Eckl almost 12 years ago

It seems that there is still a problem with DAM and Linkvalidator. I inserted mod.linkvalidator.linktypes = db,file,external,dam in Page TSConfig and changed the mailform Template. When I make a check for broken links, I get the following report as in the attached screenshot. The broken links reported are not broken links, it are DAM links (e.g. in RTE). So linkvalidator does not recognize that this is a DAM link to a file, it thinks it is a page link.

Actions #9

Updated by Philipp Gampe almost 12 years ago

Are you using the latest TYPO3 Bugfix Version?

Actions #10

Updated by Michael Stucki over 10 years ago

  • Category set to Linkvalidator
Actions #11

Updated by Michael Stucki over 10 years ago

  • Project changed from 1510 to TYPO3 Core
  • Category changed from Linkvalidator to Linkvalidator
Actions #12

Updated by Alexander Opitz about 10 years ago

  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?

Actions #13

Updated by Bernhard Eckl about 10 years ago

DAM does not work with TYPO3 V6…

Actions #14

Updated by Alexander Opitz about 10 years ago

Ok, as TYPO3 4.5 and 4.7 will only get security updates, this won't be fixed there IMHO, so let me change the question.

Is there an issue with FAL and Linkvalidator or can we close this issue?

Actions #15

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

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