51黑料不打烊

Documentation

Incoming links don鈥檛 show all linking pages in 51黑料不打烊 Experience Manager

Last update: Mon Aug 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

If some pages are missing from the incoming links view in 51黑料不打烊 Experience Manager, the issue might be due to deeply nested link nodes or custom index configurations. This article explains how to resolve it by adjusting Lucene index depth, reverting custom settings, or testing advanced configuration options.

Description description

Environment

  • 51黑料不打烊 Experience Manager as a Cloud Service (AEMaaCS)
  • 51黑料不打烊 Experience Manager (AEM) 6.5

Issues/Symptoms

  • Incoming links show low or unchanged counts despite new references.
  • Full-text queries return more results than shown in the References tab.
  • The issue might occur in shared environments but not in fresh local out-of-the-box (OOTB) setups.

Resolution resolution

There are three troubleshooting paths A, B, C.

Option A - adjust aggregate depth:

  1. Check the hierarchy of nodes that contain the link using CRXDE Lite.

  2. Review the structure of the page and adjust it so that the link node is located at a shallower level.

  3. If the linking node remains deeply nested, update the Lucene index to increase the depth being indexed for incoming link detection (e.g., add aggregate definitions like include4, include5 under /oak:index/cqPageLucene/aggregates/cq:PageContent). 聽These define how deeply the index should traverse under jcr:content to detect links.

  4. After making changes, save the index node and trigger reindexing to apply them.

Option B - revert custom index settings:

Note: Reindexing can impact performance. 聽Schedule this task during low-traffic periods.

  1. Navigate to /oak:index/cqPageLucene in CRXDE Lite.
  2. Remove any custom analyzers or misconfigured properties.
  3. Reset fulltextEnabled flags to OOTB values.
  4. Set reindex = true and monitor via JMX console or logs.

Option C - disable advanced config (for testing):

  1. Go to聽/system/console/configMgr and locate IncomingLinksReferenceProvider.
  2. Temporarily disable this configuration to check if more incoming links appear. This can help determine if the configuration聽is suppressing results.
  3. Re-enable the configuration after testing to restore normal behavior.

Validation

  1. Use SQL2 to verify actual link counts (the path /content/we-retail/us/en/about-us) is a sample target page. Replace it with the actual path of your link target.

    code language-none 
    SELECT [ jcr:path]
FROM [ cq:Page]
WHERE CONTAINS(*, '"/content/we-retail/us/en/about-us"')

  2. Compare the query results with what鈥檚 shown in the References tab to confirm discrepancy.

Useful tools for query validation:

To assist with troubleshooting and validating incoming link queries, use the following tools available in AEM:

  1. Query Performance Tool- http://localhost:4502/libs/granite/operations/content/diagnosistools/queryPerformance.html
    • Allows you to test and analyze SQL2 and QueryBuilder queries for performance insights.
  2. JCR Query Builder Debugger- http://localhost:4502/libs/cq/search/content/querydebug.html
    • Enables execution and debugging of QueryBuilder queries with detailed output.

Cause

  • Deeply nested nodes under jcr:content might not be indexed by default, causing AEM to miss links at deeper levels. Adjusting Lucene aggregates helps improve depth recognition.
  • Custom Lucene index configurations (e.g., analyzers or misconfigured properties) under /oak:index/cqPageLucene can restrict full-text indexing and affect link detection.
  • Advanced link detection configs, such as IncomingLinksReferenceProvider, might suppress incoming link visibility. Temporarily disabling this provider can reveal suppressed results and assist with debugging.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f