Link-在锚标签中插入图像组件时,CQ 中的检查程序会出现损坏的 URL 问题
Link-checker issue in CQ for broken URLs when images components are inserted in anchor tags
我在锚标签内使用图像组件,发现如果锚标签的 URL 被破坏,那么 link-checker 功能就会启动并用图像标记它,一个开口大括号图像和右大括号图像。但是如果放置在锚标记内的组件是图像组件,则右大括号图像会丢失。
下面是组件的代码。
<div class="" style="background-color:#79a0c1">
<a href="http://http://www .goo gle. Com">
<cq:include path="image" resourceType="/libs/foundation/components/image"/>
</a>
</div>
下面是错误的屏幕截图
This issue was due to improper configuration setting for the entire application.
This is the configuration having incorrect settings.
Config.auth—>
com.day.cq.rewriter.linkchecker.impl.LinkCheckerTransformerFactory with following properties
linkcheckertransformer.disableChecking—> false
linkcheckertransformer.disableRewriting—> false
linkcheckertransformer.mapCacheSize—> 5000
linkcheckertransformer.rewriteElements—> a:href,,area:href,form:action,img:src
linkcheckertransformer.strictExtensionCheck—> false
linkcheckertransformer.stripHtmlExtension—> false
We have the same configuration even for Config.publish
Removed the above configuration from both author and publish, then the issue got resolved
我在锚标签内使用图像组件,发现如果锚标签的 URL 被破坏,那么 link-checker 功能就会启动并用图像标记它,一个开口大括号图像和右大括号图像。但是如果放置在锚标记内的组件是图像组件,则右大括号图像会丢失。 下面是组件的代码。
<div class="" style="background-color:#79a0c1">
<a href="http://http://www .goo gle. Com">
<cq:include path="image" resourceType="/libs/foundation/components/image"/>
</a>
</div>
下面是错误的屏幕截图
This issue was due to improper configuration setting for the entire application.
This is the configuration having incorrect settings.
Config.auth—>
com.day.cq.rewriter.linkchecker.impl.LinkCheckerTransformerFactory with following properties
linkcheckertransformer.disableChecking—> false
linkcheckertransformer.disableRewriting—> false
linkcheckertransformer.mapCacheSize—> 5000
linkcheckertransformer.rewriteElements—> a:href,,area:href,form:action,img:src
linkcheckertransformer.strictExtensionCheck—> false
linkcheckertransformer.stripHtmlExtension—> false
We have the same configuration even for Config.publish
Removed the above configuration from both author and publish, then the issue got resolved