Bug #27214
closed
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
DAM version is 1.2.2 (newest in TER)
Should I create a new issue at the DAM project?
- Status changed from New to Needs Feedback
- TYPO3 Version set to 4.5
Yes please check with DAM project first.
Any progress here? Does it work now? Is it a dam bug?
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.
I agree. But didn't you want to post this at the other issue?
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.
Are you using the latest TYPO3 Bugfix Version?
- Category set to Linkvalidator
- Project changed from 1510 to TYPO3 Core
- Category changed from Linkvalidator to Linkvalidator
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.1.7)?
DAM does not work with TYPO3 V6…
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?
- 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.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 