Skip to content

500 Error on Review Edit Page in Production

A 500 Internal Server Error occurs when attempting to access the Edit page of a Review node, as reported by @mdelgado624. This issue appears to be limited to the Review content type and is reproducible only on the production environment, not locally.

Steps to Reproduce

  1. Navigate to the Review Edit page.
  2. Observe that a 500 error is returned.

Observations

  • After clearing the cache (via UI or Drush), the page loads correctly once, but subsequent attempts result in a 500 error again.
  • Clearing the cache via the admin UI often results in a 504 Gateway Timeout (maybe not related to the Review nodes but it's something).
  • The issue only affects the Review Edit page. Edit pages for all other content types function as expected.
  • No related errors appear in the Drupal database logs and the OKD logs only show the 500 status response.
  • The issue is not reproducible in a local development environment, which suggests it may be related to infrastructure, environment configuration, or specific production-only data.

Next Steps

  • Rebuild the pods in the production environment to rule out any issues with a misbehaving pod.
  • Look at the codebase to identify any potential optimizations or problematic logic, especially:
    • Review-specific hooks, preprocess functions, or custom logic that may be impacting the Edit form.
  • Compare local and production configuration settings to ensure alignment. This will help replicate the production behavior locally for more accurate testing and debugging.
Edited by Eric Poirier