LouieGeetoo

Just noticed you prefer to use GitHub issues for this plugin. Made an issue for this here: https://github.com/bradt/wp-tantan-s3/issues/7

I’m guessing this has to do with the version of PHPMailer being used by WordPress being updated with 3.4. It’s causing problems with other plugins, too: https://www.ads-software.com/support/topic/plugin-contact-form-7-not-working-with-wordpress-34

From that thread, a workaround is to change the lines in WordPress’s code as seen here (to remove the fifth parameter mentioned in the error message): https://core.trac.www.ads-software.com/attachment/ticket/20970/20970.patch

I’m going to try it out and will report back with results.

See these non-php.ini options presented in esmi’s link. Since 33554432 bytes is 32MB, you’ll want to try something higher:

2. If you don’t have access to PHP.ini try adding this to an .htaccess file:
php_value memory_limit 64M

3. Try adding this line to your wp-config.php file:
// Increasing memory allocated to PHP
define(‘WP_MEMORY_LIMIT’, ‘64M’);

You’re quite welcome! ??

Try opening it in Chrome Incognito mode or on another computer. If it works there, then you probably just need to clear your Chrome’s cache and site data (wrench > Tools > Clear browsing data…).

Turns out this problem was due to something wrong with SSL/HTTPS. Once I turned off ‘FORCE_SSL_ADMIN’ on our WP installations and tried loading the dashboards via just HTTP, they loaded up just fine. So the problem is not with WordPress but with our SSL configuration.

This makes perfect sense in hindsight: the reason only the dashboards were seeing the problem is because they were the only pages using SSL.