Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By andrewtf on
I'm troubleshooting an issue where saving a node in a specific content content type results in the dreaded White Screen of Death™. In this case the new node (or updates to an existing one) isn't saved.
No errors in Drupal's reports, and a check of Apache's httpd logs doesn't reveal anything either. Chrome returns a message suggesting a server error.
I'm not sure what led to this happening. It was working fine one moment and then wasn't. I've tried disabling a few suspect modules, but no luck there, either.
Any suggestions as to where to go from here would be really helpful. In the worst case scenario I just make a new content type to replace the FUBARed one and get back to work, but I'd really like to know why we're having this issue and to fix it if possible.
