Custom Error messages are not translatable. The same message is used for all languages on a multilingual site. It should be possible, on a multilingual site, to provide translations of the custom error message.
The message are stored as configuration variables. The i18n module provides a mean to translate configuration variables. To support variable translations in Drupal 7, the i18n module uses the Variable module and require translatable variables to be defined using implementation of its hooks.
hook_variable_info() and hook_variable_group_info() in a new customerror.variable.inc file in order to declare the configuration variables used to store custom error messages.None.
None.
Needs work
1.0
Code
After being applied to the 7.x branch, it should be considered for backport to the 6.x branch. Note: This tag should generally remain even after the backport has been written, approved, and committed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Does it make sense to provide changes for a version compatible with Drupal 7 if it has an end life in November 2023?
While the announced EOL of Drupal 7 is November 2013, it may be extended further. A lot of the current owners of websites built with Drupal is not capable of upgrading to Symfony-based Drupal. I doubt the DA wants to alienate such a huge user base.
So a good patch or MR for this will be committed.