rickharris3

I am getting much more SPAM too with this V3 version of Recaptcha and Flamingo isn’t even catching it as SPAM; thus, my inbox is getting inundated with crap. Please reimplement support for V2

Thanks for all your efforts. I just switched to Easy WP SMTP and it gets the job done. I still prefer your Oauth authentication over smtp TLS, so please let me know when you have a new version to try.

It looks to me like you are calling a method “ClassLoader::setClassMapAuthoritative()” that simply does not exist in my version of PHP. What version of PHP are you working with?

Hi, I changed the log_errors_max_len to 0 and it still seems to truncate individual function calls but looks like the entire stack trace is here. I am not aware of any PHP caches; however, I restarted the php-fpm which is supposed to clear the Opcache and it did not help.

[Wed Jan 03 15:33:27.442116 2018] [proxy_fcgi:error] [pid 22902:tid 140454913464064] [client 172.56.6.193:65335] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught Error: Call to undefined method Composer\\Autoload\\ClassLoader::setClassMapAuthoritative() in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/vendor/composer/autoload_real.php:38\nStack trace:\n#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/vendor/autoload.php(7): ComposerAutoloaderInitbd625bfb904527ebcdc364a59295e538::getLoader()\n#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/src/Providers/Gmail/Mailer.php(53): require(‘/opt/bitnami/ap…’)\n#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/src/Providers/Loader.php(170): WPMailSMTP\\Providers\\Gmail\\Mailer->__construct(Object(WPMailSMTP\\MailCatcher))\n#3 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/src/Providers/Loader.php(127): WPMailSMTP\\Providers\\Loader->get_entity(‘gmail’, ‘Mailer’)\n#4 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/src/MailCatcher.php(51): WPMailSMTP\\Providers\\Loader->get_mail…\n’, referer: https://bak.rickharris.com/wp-admin/options-general.php?page=wp-mail-smtp&tab=test

Sorry, I do not have a composer.json or a /vendor directory.

Also, not sure how the error log is still cut? It was the last line in the log file and it looks like a full stack trace to me.

Remember, 1.0.2 still works fine and luckily that is what I am using on my production site.

Google VM, Debian GNU/Linux 8\n\1, Apache 2.4.23, PHP 7.0.12, WP 4.9.1, WP Mail SMTP 1.2.2

[Thu Dec 28 15:32:13.256718 2017] [proxy_fcgi:error] [pid 29162:tid 140562451552000] [client 172.56.7.48:56888] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught Error: Call to undefined method Composer\\Autoload\\ClassLoader::setClassMapAuthoritative() in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/vendor/composer/autoload_real.php:38\nStack trace:\n#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/vendor/autoload.php(7): ComposerAutoloaderInitbd625bfb904527ebcdc364a59295e538::getLoader()\n#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/src/Providers/Gmail/Mailer.php(53): require(‘/opt/bitnami/ap…’)\n#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/src/Providers/Loader.php(170): WPMailSMTP\\Providers\\Gmail\\Mailer->__construct(Object(WPMailSMTP\\MailCatcher))\n#3 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/src/Providers/Loader.php(127): WPMailSMTP\\Providers\\Loader->get_entity(‘gmail’, ‘Mailer’)\n#4 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/wp-mail-smtp/src/MailCatcher.php(51): WPMailSMTP\\Providers\\Loader->get_mail…\n’, referer: https://bak.rickharris.com/wp-admin/options-general.php?page=wp-mail-smtp&tab=test

For what it is worth, I am still getting error 500 with version 1.2.2, hosted on Google servers with the Bitnami WP stack

I am having the same problem after updating from 1.0.2 to 1.2.1. If I downgrade back to 1.0.2 everything works fine. I have also noticed that the “Save Settings” button has disappeared in this 1.2.1 version. Something is awry.

Understood, and thanks for the help. I spent about an hour debugging the CF7 code and it seems more like a server side problem than a client problem, since the data gets sent to the server and an the error I mentioned above gets returned back to the client. Unfortunately, since I could not get CF7 to work with all other plugins deactivated and with the standard Twenty Thirteen them that comes with WP, then I simply had to abandon using it.

Thanks, but I already switched to using the Fast Secure Contact Form, which appears to work just fine.

I tested it with the standard 2013 WordPress theme and the only plugins used were Easy WP SMTP and Really Simple CAPTCHA, which were required for my contact form.