Skip to main content

Portal Troubleshooting

This page lists common portal problems and practical checks.

User Is Redirected to Login​

Possible causes:

  • no valid session cookie exists
  • session expired
  • OIDC auto-redirect is enabled
  • SSO redirect is configured
  • the target page or object requires login
  • the login page is configured incorrectly

Checks:

  • verify login_page_url and pb_entry_page
  • check whether ?local=1 or ?no_sso=1 should bypass SSO for administration
  • inspect access manager logs
  • verify the session cookie name matches SESSION_COOKIE_NAME

Page Is Empty​

Possible causes:

  • the page object exists but has no boxes
  • the boxes are not published
  • the boxes are assigned to a zone that the template does not render
  • the current user does not match the box ACL
  • required boxes are missing

Checks:

  • verify the page ID
  • check the page-specific box folder
  • check FIELD_BOX_POSITION and pb_zone_mapping
  • check FIELD_BOX_PUBLISH
  • test as portal administrator

Document Is Not Visible​

Possible causes:

  • DMS read permission is missing
  • obj_acl or cq_acl does not match the user's roles
  • the document is not linked to the expected page or folder
  • the template query filters it out
  • the user is still using the anonymous session

Checks:

  • inspect the object permissions
  • compare user roles with ACL values
  • test the DQL query separately
  • verify login state and session info

Template Include Error​

Possible causes:

  • template file missing
  • wrong layout path
  • wrong master template path
  • customer template encoded differently
  • required template context value missing
  • DQL or SQL error inside the template

Checks:

  • verify pb_language_path, pb_layout_path, and template path values
  • check the exact include name in the error
  • test the template with a minimal page
  • inspect the nested exception in the log

Box Is Slow​

Possible causes:

  • unbounded DQL query
  • expensive SQL query
  • many nested includes
  • too many boxes on one page
  • document previews or content lookups inside a list

Checks:

  • look for slow box template log entries
  • add or reduce result limits
  • cache stable query results if appropriate
  • split large portal pages into smaller pages

Search Returns Unexpected Results​

Possible causes:

  • direct search and configured query search are mixed up
  • query parameters are wrong
  • DQL result rows contain multi-value fields
  • permissions filter out expected results
  • publication filters hide portal pages

Checks:

  • inspect the generated search query
  • test with an administrator and a normal user
  • verify query result fields used by the template
  • check page publication values

Admin Cannot Edit Portal Content​

Possible causes:

  • the user lacks role_edit_portal
  • the user is not admin
  • customer-specific administrator role is missing
  • edit mode parameter is not set
  • the target page is protected

Checks:

  • inspect session roles
  • verify role_edit_portal keyword exists
  • check protected page IDs
  • test /portal/admin

Login Works but User Sees Wrong Language​

Possible causes:

  • user language is empty
  • default language is different from expected
  • translation table misses portal labels
  • templates contain hardcoded text

Checks:

  • inspect obj_language on the user
  • verify default_language
  • check translation table entries
  • search templates for hardcoded labels