Ability to Customize Core Error Message

Created on 24 January 2020, about 5 years ago
Updated 9 October 2023, over 1 year ago

----------------- Proposed Solution ------------------------

Problem/Motivation

In /core/includes/errors.inc the error message for recoverable fatal error is hard coded. A slight change will allow users to customise this in their settings.php file, if they wish.

Steps to reproduce

Proposed resolution

Add provision in settings.php to override the default error message with proper error handling to make it fail safe where this setting is called to override the respective default message, better by enclosing the code in try-catch block.

Example setting: $settings['custom_error_message'] = "some error message!";

Remaining tasks

Implement the solution.

Feature request
Status

Needs work

Version

11.0 🔥

Component
Base 

Last updated about 3 hours ago

Created by

🇺🇸United States jnicola

Live updates comments and jobs are added and updated live.
  • developer

    Used for Documentation issues that pertain to developer docs.

  • Needs usability review

    Used to alert the usability topic maintainer(s) that an issue significantly affects (or has the potential to affect) the usability of Drupal, and their signoff is needed. When adding this tag, make it easy to review the issue. Make sure the issue summary describes the problem and the proposed solution. Screenshots usually help a lot! To get sign-off on issues with the "Needs usability review" tag, post about them in the #ux channel on Drupal Slack, and/or attend a UX meeting to demo the patch and get direct feedback from designers/UX folks/product management on next steps. If an issue represents a significant new feature, UI change, or change to the general "user experience" of Drupal, use Needs product manager review instead. See the scope of responsibilities for product managers.

  • Needs framework manager review

    It is used to alert the framework manager core committer(s) that an issue significantly impacts (or has the potential to impact) multiple subsystems or represents a significant change or addition in architecture or public APIs, and their signoff is needed (see the governance policy draft for more information). If an issue significantly impacts only one subsystem, use Needs subsystem maintainer review instead, and make sure the issue component is set to the correct subsystem.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024