twisted1919
Administrator
Staff memberAs much as i struggle to make MailWizz EMA compatible out-of-the-box with any host, this is just unrealistic since the configuration vary so much between the hosts.
By default, MailWizz EMA runs in production mode, that is, no errors are show to the end user. That also means that if you get a serious error (most of the time a file permission error) the application will stop running and you will get a white screen.
If this happens, most probably you will open a support ticket but in order for me to be able to help you, you will have to enable debugging so that i can see exactly the error.
In order to enable debugging, all you have to do, is to open the 'apps/init.php' file and at line 16, right before the following piece of code:
add the line define('MW_FORCE_DEBUG_MODE', true); so that the code becomes:
After this change, save the file and reload your web page, you should see the reason why the application stop working.
Please don't forget to remove the added line once you are done debugging.
[UPDATE]
Since version 1.3.5.7, in the init.php file, you will find:
In order to force debug you'll have to define the debug mode as in:
By default, MailWizz EMA runs in production mode, that is, no errors are show to the end user. That also means that if you get a serious error (most of the time a file permission error) the application will stop running and you will get a white screen.
If this happens, most probably you will open a support ticket but in order for me to be able to help you, you will have to enable debugging so that i can see exactly the error.
In order to enable debugging, all you have to do, is to open the 'apps/init.php' file and at line 16, right before the following piece of code:
Code:
// if debug mode is forced then go with it
if (defined('MW_FORCE_DEBUG_MODE') && MW_FORCE_DEBUG_MODE) {
[..]add the line define('MW_FORCE_DEBUG_MODE', true); so that the code becomes:
Code:
define('MW_FORCE_DEBUG_MODE', true);
// if debug mode is forced then go with it
if (defined('MW_FORCE_DEBUG_MODE') && MW_FORCE_DEBUG_MODE) {
[..]After this change, save the file and reload your web page, you should see the reason why the application stop working.
Please don't forget to remove the added line once you are done debugging.
[UPDATE]
Since version 1.3.5.7, in the init.php file, you will find:
PHP:
// set the developer ip addresses, separated by a comma
defined('MW_DEVELOPERS_IPS') or define('MW_DEVELOPERS_IPS', '');
// decide if we're in read only mode, note that MW_DEVELOPERS_IPS still have full access
defined('MW_IS_APP_READ_ONLY') or define('MW_IS_APP_READ_ONLY', false);
// whether we should force debug mode
defined('MW_FORCE_DEBUG_MODE') or define('MW_FORCE_DEBUG_MODE', isset($_SERVER['REMOTE_ADDR']) && in_array($_SERVER['REMOTE_ADDR'], array_map('trim', explode(',', MW_DEVELOPERS_IPS))));
// if debug mode is forced then go with it
if (defined('MW_FORCE_DEBUG_MODE') && MW_FORCE_DEBUG_MODE) {
[...]In order to force debug you'll have to define the debug mode as in:
PHP:
// set the developer ip addresses, separated by a comma
defined('MW_DEVELOPERS_IPS') or define('MW_DEVELOPERS_IPS', '');
// decide if we're in read only mode, note that MW_DEVELOPERS_IPS still have full access
defined('MW_IS_APP_READ_ONLY') or define('MW_IS_APP_READ_ONLY', false);
// ADDED THIS before the initial check for debug mode:
define('MW_FORCE_DEBUG_MODE', true);
// whether we should force debug mode
defined('MW_FORCE_DEBUG_MODE') or define('MW_FORCE_DEBUG_MODE', isset($_SERVER['REMOTE_ADDR']) && in_array($_SERVER['REMOTE_ADDR'], array_map('trim', explode(',', MW_DEVELOPERS_IPS))));
// if debug mode is forced then go with it
if (defined('MW_FORCE_DEBUG_MODE') && MW_FORCE_DEBUG_MODE) {
[...]
Last edited:
