Skip to main content

Debugging your content

Use the Debugger page in PageBuilder Editor Developer Tools to verify or troubleshoot content sources that define what stories and media show in specific blocks of your site.

Arc XP's Debugger has two main debugging types:

  • Content Debugger - allows you to test and verify specific content sources. It helps troubleshoot issues by letting you examine the responses returned from content sources.

  • Resolver Debugger - allows you to examine how your site's content is rendered.

To access the Debugger tool, you must have Developer Tools access provided through the Permissions application. See Permissions for more information.How To Configure User Permissions for Access to Developer Center

Scenario: Solving a 500 error when accessing a story in the browser

As an administrator of The News, you notice that the updated content in Composer is not reflected on the frontend website.

To investigate, you access the Resolver Debugger in PageBuilder Editor's Developer Tools. You enter the article’s URI and check if the screen displays Resolver, Rendering, and Content sections with an expandable content root.

You expand the Content section and locate the field named revision_id. You don't find Content section, the revision_id is missing, and the revision_id differs. You can copy the information to open a support ticket with the collected information to your development team.

Procedures

Using the Content Debugger

To use the Content Debugger in PageBuilder Editor's Developer Tools, complete the following:

  1. Navigate to PageBuilder Editor > Developer Tools > Debugger. The Debugger page opens.

  2. Click the Select a Site dropdown to pick a site from your organization.

  3. Click the Select a Type > Content Debugger. The Content Debugger page opens, showing two columns:

    • Content sources - shows the endpoints from which PageBuilder Engine retrieves content, for example, author-api.

    • Query parameters - shows a series of query parameters defining what data to retrieve from the content source, such as slug.

  4. Enter the required query parameters.

  5. Select the cache control action you prefer from the following:

    • Fetch - retrieves content from the cache, if available; otherwise, gets it from the source and stores it in cache.

    • Update - forces retrieval of fresh content from the source and updates the existing cache with this new content.

    • Clear- removes the specified content from the cache entirely without fetching new content.

    A confirmation message appears on the page.

Using the Resolver Debugger

To use the Resolver Debugger in PageBuilder Editor's Developer Tools, complete the following:

  1. Navigate to PageBuilder Editor > Developer Tools > Debugger. The Debugger page opens.

  2. Click the Select a Site dropdown to pick a site from your organization.

  3. Click the Select a Type > Resolver Debugger. The Debugger page refreshes, showing a text field and the Debug URI button.

  4. Enter the URI you want to debug.

  5. Click Debug URI. The debugger analyzes the URI and returns the following information:

    • Resolver - maps incoming requests to templates using URL patterns and extraction rules.

    • Rendering - defines the template that formats the response for display.

    • Content - stores the retrieved data along with caching metadata.

    • Request - contains details about the incoming user request.

  6. Click the content root to expand it and view its details.

  7. Click the copy to clipboard icon icon_copy_to_clipboard.png next to the JSON block to copy the content and share it with your development team or Arc XP Customer Service for troubleshooting.

In this section: