Getting Fatal Error on selecting delivery method

  • Resolved firstroundtech

    (@firstroundtech)


    6 years, 1 month ago

    Hi,

    I am hoping you can help. I keep getting a fatal error when switching to the Amazon SES delivery method using this plugin.

    Error Details
    =============
    An error of type E_ERROR was caused in line 212 of the file /var/www/wptbox/wp-content/plugins/mailster-amazonses/classes/amazonses.class.php. Error message: Uncaught Error: Call to undefined method WP_Error::get() in /var/www/wptbox/wp-content/plugins/mailster-amazonses/classes/amazonses.class.php:212
    Stack trace:
    #0 /var/www/wptbox/wp-content/plugins/mailster-amazonses/classes/amazonses.class.php(305): MailsterAmazonSES->getquota(false)
    #1 /var/www/wptbox/wp-includes/class-wp-hook.php(288): MailsterAmazonSES->verify_options(Array)
    #2 /var/www/wptbox/wp-includes/plugin.php(206): WP_Hook->apply_filters(Array, Array)
    #3 /var/www/wptbox/wp-content/plugins/mailster/classes/settings.class.php(1250): apply_filters(‘mailster_verify…’, Array)
    #4 /var/www/wptbox/wp-includes/class-wp-hook.php(290): MailsterSettings->verify(Array)
    #5 /var/www/wptbox/wp-includes/plugin.php(206): WP_Hook->apply_filters(Array, Array)
    #6 /var/www/wptbox/wp-includes/formatting.php(4823): apply_filters(‘sanitize_option…’, Array, ‘mailster_option…’, Array)
    #7 /var/www/wptbox/wp-includes/option.php(319): sanitize_option(‘mailster_option…’, Array)
    #8 /var/www/wptbox/wp-admin/options.php(285)

    I’m using WordPress 5.4 with Mailster and Mailster SES plugins being the only plugins that are activated. I am using the Divi theme but have also tried it on 2019 theme and I still get the error when I try to save my credentials. it also happens on a local install.

    Do you have any idea what the problem could be?

    Thanks in advance

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author EverPress

    (@everpress)

    6 years, 1 month ago

    Hi there!

    Thanks for the feedback!

    We’ve just pushed an update which should fix this so please check again!

    Thanks!

    Thread Starter firstroundtech

    (@firstroundtech)

    6 years, 1 month ago

    Hey,

    Well, that’s the fastest support response I have ever had 🙂

    Thank you very much for your help.

    shekharsmn

    (@shekharsmn)

    6 years, 1 month ago

    I am getting a different error. Tried re-installing but still has the same problem:

    [Fri Apr 17 09:16:14.831154 2020] [proxy_fcgi:error] [pid 6419:tid 140455756818176] [client 183.82.183.82:7745] AH01071: Got error ‘PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘ASC’ at line 1 for query SELECT meta_key FROM wp_usermeta WHERE meta_value NOT LIKE ‘%:{%’ GROUP BY meta_key ASC made by require_once(‘wp-admin/admin.php’), do_action(‘newsletter_page_mailster_settings’), WP_Hook->do_action, WP_Hook->apply_filters, MailsterSettings->newsletter_settings, include(‘/plugins/mailster/views/settings.php’), include(‘/plugins/mailster/views/settings/wordpress-users.php’), MailsterHelper->get_wpuser_meta_fields’, referer: https://www.qalfit.com/wp-admin/edit.php?post_type=newsletter&page=mailster_settings

    [Fri Apr 17 09:17:37.056084 2020] [proxy_fcgi:error] [pid 6419:tid 140455891101440] [client 183.82.183.82:7884] AH01071: Got error ‘PHP message: PHP Fatal error: Uncaught Error: Call to undefined function GuzzleHttp\\_idn_uri_convert() in /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/mailster-amazonses/vendor/guzzlehttp/guzzle/src/Client.php:220\nStack trace:\n#0 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/mailster-amazonses/vendor/guzzlehttp/guzzle/src/Client.php(113): GuzzleHttp\\Client->buildUri(Object(GuzzleHttp\\Psr7\\Uri), Array)\n#1 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/mailster-amazonses/vendor/aws/aws-sdk-php/src/Handler/GuzzleV6/GuzzleHandler.php(43): GuzzleHttp\\Client->sendAsync(Object(GuzzleHttp\\Psr7\\Request), Array)\n#2 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/mailster-amazonses/vendor/aws/aws-sdk-php/src/WrappedHttpHandler.php(87): Aws\\Handler\\GuzzleV6\\GuzzleHandler->__invoke(Object(GuzzleHttp\\Psr7\\Request), Array)\n#3 /opt/bitnami/apps/wordpress/htdocs/wp-content/plugins/mailster-amazonses/vendor/aws/aws-sdk-php/src/ClientSideMonitoring/AbstractMonitoringMiddleware.php(126): Aws\\Wr…’, referer: https://www.qalfit.com/wp-admin/edit.php?post_type=newsletter&page=mailster_settings

    [Fri Apr 17 09:17:42.516001 2020] [proxy_fcgi:error] [pid 6267:tid 140455572178688] [client 183.82.183.82:7898] AH01071: Got error ‘PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘ASC’ at line 1 for query SELECT meta_key FROM wp_usermeta WHERE meta_value NOT LIKE ‘%:{%’ GROUP BY meta_key ASC made by require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), do_action(‘template_redirect’), WP_Hook->do_action, WP_Hook->apply_filters, MailsterCron->template_redirect, MailsterCron->cron_page, include(‘/plugins/mailster/cron.php’), do_action(‘mailster_cron_worker’), WP_Hook->do_action, WP_Hook->apply_filters, MailsterQueue->update, MailsterCampaigns->get_unsent_subscribers, MailsterCampaigns->get_subscribers, MailsterSubscribers->query, MailsterSubscriberQuery->run, MailsterSubscriberQuery->__get, MailsterSubscriberQuery->get_wp_user_meta, MailsterHelper->get_wpuser_meta_fields’, referer: https://www.qalfit.com/mailster/af9bc704461675836bdbc584738b5b50

    Plugin Author EverPress

    (@everpress)

    6 years, 1 month ago

    Hey There,

    Thank you for writing in! We provide all of our official support via the member area on our website. If you have not done so yet, please use the link below to register for access so that you can post your question there: https://mailster.co/go/register/

    We are looking forward helping you out.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Getting Fatal Error on selecting delivery method’ is closed to new replies.