You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The troubles of the hosting provider is without your control. In my case, the database server was out for some time and users saw an English message about a critical error with advice to check the configuration file. But it wasn't true, the configuration file was correct.
Proposed Solution
if there is a live site - no debug, developer mode, not localhost or something like that, display the user some nice message about troubles on site, we are working on it
replace file name e107_config.php similar way as other error strings - your configuration file - a person that is able to fix this knows the file name of the config file
don't display the database name in the error message on the live site
improve message look
translate messages (those from lan_error.php) - site language should be cached in a file (so available without database connection)
add main admin notification if site is down because this issue
Additional Context
It looks like this now:
At least this is helping:
It would be nice to update the legacy code too. My editor is telling me this and I really don't know if they are false errors or how it is possible that it is workin
The text was updated successfully, but these errors were encountered:
…s. (one email per day)
Usage: Add the following to e107_config.php, replacing the email address with your own.
define('e_EMAIL_CRITICAL', 'myemail@somewhere.com');
…error constant as example to e107_config.php during installation.
CaMer0n
changed the title
improving critical error message for users when there are issues on live site
Add option to email any critical error message to an admin
Nov 23, 2023
Motivation
The troubles of the hosting provider is without your control. In my case, the database server was out for some time and users saw an English message about a critical error with advice to check the configuration file. But it wasn't true, the configuration file was correct.
Proposed Solution
Additional Context
It looks like this now:
![image](https://user-images.githubusercontent.com/5429548/222977297-164163ed-1259-46ba-8537-62f09ba7e3f3.png)
At least this is helping:
![image](https://user-images.githubusercontent.com/5429548/222977341-04a5449b-6281-4ad6-8303-c8c8c16d1ff0.png)
It would be nice to update the legacy code too. My editor is telling me this and I really don't know if they are false errors or how it is possible that it is workin
![image](https://user-images.githubusercontent.com/5429548/222977562-79ec0cae-f24f-45d8-9b5b-894ff7ce9e81.png)
The text was updated successfully, but these errors were encountered: