Skip to main content
skadobe9
Aug 3, 2021 6:25 PM UTC
Solved

disabling "disable checking" in Day CQ Link Checker Transformer

We disabled the "disable checking" checkbox to login publisher servers in 6.5.9, is it a good practice?

added /libs/granite/core/content in blacklist paths.

 

Please let us know your thoughts

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Shubham_borole
Shubham_boroleAccepted solution
Community Advisor
Aug 4, 2021 3:36 AM UTC

Hi @skadobe9 ,

 

In my understanding it is better to have the checking (and rewriting just to be safe) disabled in publishers since this can cause performance concerns.
For author instances, this can be kept on if there is some value to the authors in terms of catching incorrect urls. One of the challenges I faced for author instance and getting accurate broken links was discussed here - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/find-and-fix-broken-links-in-aem/qaq-p/390654.   We ended up disabling it in author as well (time being).

 

Please also refer https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/external-link-checker.html?lang=en for steps to disable link checker. There is no obvious indication of a best practice but based on project situation the Link Checker can be utilized. Plus suggestions from community members..

 

Thanks

View in thread

4 replies

Ravi_Pampana
Community Advisor
Ravi_PampanaCommunity Advisor
Community Advisor
Aug 3, 2021 7:23 PM UTC

Hi,

 

Disabling link checker is fine in case you are referring to external links and don't want them to display as broken in live pages.

 

The feature will be useful if all the links will point to internal urls.

 

Refer: https://experienceleague.adobe.com/docs/experience-manager-64/administering/operations/external-link-checker.html?lang=en for more details

Translate
Ravi Pampana
    arunpatidar
    Community Advisor
    arunpatidarCommunity Advisor
    Community Advisor
    Aug 3, 2021 7:26 PM UTC

    Hi,

    It is always recommned to disable link checker in publish instances, otherwise it cause performance issues.

    On Author, if you think it is good to have , keep it enable otherwise disable it in Author too. There is no harm in disabling.

    Translate
    Arun Patidar
      Shubham_borole
      Community Advisor
      Shubham_boroleCommunity AdvisorAccepted solution
      Community Advisor
      Aug 4, 2021 3:36 AM UTC

      Hi @skadobe9 ,

       

      In my understanding it is better to have the checking (and rewriting just to be safe) disabled in publishers since this can cause performance concerns.
      For author instances, this can be kept on if there is some value to the authors in terms of catching incorrect urls. One of the challenges I faced for author instance and getting accurate broken links was discussed here - https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/find-and-fix-broken-links-in-aem/qaq-p/390654.   We ended up disabling it in author as well (time being).

       

      Please also refer https://experienceleague.adobe.com/docs/experience-manager-65/administering/operations/external-link-checker.html?lang=en for steps to disable link checker. There is no obvious indication of a best practice but based on project situation the Link Checker can be utilized. Plus suggestions from community members..

       

      Thanks

      Translate
        Dipti_Chauhan
        Community Advisor
        Dipti_ChauhanCommunity Advisor
        Community Advisor
        Aug 4, 2021 6:11 AM UTC

        Hi @skadobe9 

          This is anyways good practice to disable it on Publish as it can impact site performance. You can still keep it for authors just to see all broken links.

         

        Thanks

        Dipti

        Translate
          Terms & ConditionsAccessibility statement

          Loading footer...