Make WordPress Core

Opened 10 years ago

Closed 10 years ago

Last modified 7 years ago

#28336 closed feature request (wontfix)

Custom template for 500 error page

Reported by: lukbarros's profile lukbarros Owned by:
Milestone: Priority: normal
Severity: normal Version: 3.9.1
Component: Themes Keywords: close
Focuses: template Cc:


The hierarchy of wordpress theme allows you to have a 404 page so you can personalize answer to that status of the web server.

Very good long term include a 500.php when the question 'what I want' is taken to decide which theme file run. It would be useful for developers who use hosting providers compartilhadamente and he does not have access to that specific configuration.

Change History (13)

#1 @lukbarros
10 years ago

Last edited 10 years ago by lukbarros (previous) (diff)

#2 @lukbarros
10 years ago

  • Focuses administration performance added
  • Severity changed from normal to minor
Last edited 10 years ago by lukbarros (previous) (diff)

#3 @lukbarros
10 years ago

Last edited 10 years ago by lukbarros (previous) (diff)

#4 @ericlewis
10 years ago

Interesting idea. Apache supports specifying a custom 500 error page in an .htaccess file, so this might be something we could do.

#5 @ocean90
10 years ago

  • Focuses administration performance removed
  • Keywords close added
  • Severity changed from minor to normal

5xx errors are server failures so we can't ensure that PHP and MySQL are still available to let WordPress show a custom error template for this type of errors. I think it's also hard to detect 5xx errors.

#6 @SergeyBiryukov
10 years ago

  • Summary changed from 500 error page to Custom template for 500 error page

#7 @lukbarros
10 years ago

Hi gus... See outher ticket #28343

#8 @lukbarros
10 years ago

Hello guys, the 500 error then somehow could not recall all the wordpress shooting connection issues the bank, can be a 500.php page q receives some specification error (which can be a php against her including her and prepare data before including 500.php

The example above ensures that we can have a callback for 500.x error

I await further consideration.

This ticket was mentioned in IRC in #wordpress-dev by Clorith. View the logs.

10 years ago

#10 @Clorith
10 years ago

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version changed from trunk to 3.9.1

As the errors in the 5xx branch mean WordPress won't ever be reached, I'm afraid this just isn't doable.

#11 @SergeyBiryukov
10 years ago

Even if we could use Apache ErrorDocument directive for this, we still wouldn't want for WordPress to take ownership of server errors, for the same reasons as in comment:8:ticket:19196.

#12 @SergeyBiryukov
10 years ago

  • Milestone Awaiting Review deleted

This ticket was mentioned in Slack in #core by sergey. View the logs.

7 years ago

Note: See TracTickets for help on using tickets.