remi123

After some debugging I found this error message inside $options = gmail_smtp_get_option();

[oauth_access_token] => {"error":"invalid_grant","error_description":"Code was already redeemed."}

Do you know how to fix this?

Hi @naa986,

I’ve followed the steps of ‘Fresh Authorization’ (revoked access and deleted access key) and granted access again.
Got the same results;

error.log

[Wed Dec 13 09:41:09.167646 2017] [lsapi:error] [pid 104091:tid 140039989470976] [client 212.45.43.190:62093] [host www.cityspotz.nl] Backend fatal error: PHP Fatal error: Uncaught exception 'InvalidArgumentException' with message 'Invalid token format' in /home/cityspotz/domains/cityspotz.nl/public_html/v2/wp-content/plugins/gmail-smtp/google-api-php-client/src/Google/Client.php:434\nStack trace:\n#0 /home/cityspotz/domains/cityspotz.nl/public_html/v2/wp-content/plugins/gmail-smtp/class.phpmaileroauthgoogle.php(139): Google_Client->setAccessToken('{"error":"inval...')\n#1 /home/cityspotz/domains/cityspotz.nl/public_html/v2/wp-content/plugins/gmail-smtp/PHPMailer/class.smtp.php(475): GmailXOAuth2->getOauth64()\n#2 /home/cityspotz/domains/cityspotz.nl/public_html/v2/wp-content/plugins/gmail-smtp/class.phpmaileroauth.php(153): SMTP->authenticate('', '', 'XOAUTH2', '', '', Object(GmailXOAuth2))\n#3 /home/cityspotz/domains/cityspotz.nl/public_html/v2/wp-content/plugins/gmail-smtp/PHPMailer/class.phpmailer.php(1542): PHPMailerOAuth->smtpConnect(Array)\n#4 /home/cityspotz/domains/cityspotz.nl/public_html/v2/wp-content/plugins/gmail-smtp/PHPMailer/class.phpmailer.php(1337): PHPMailer->smtpS in /home/cityspotz/domains/cityspotz.nl/public_html/v2/wp-content/plugins/gmail-smtp/google-api-php-client/src/Google/Client.php on line 434\n, referer: https://www.cityspotz.nl/v2/wp-admin/options-general.php?page=gmail-smtp-settings&action=test-email

Test Eail result:

2017-12-13 08:41:08 Connection: opening to smtp.gmail.com:587, timeout=300, options=array ()
2017-12-13 08:41:09 Connection: opened
2017-12-13 08:41:09 SMTP -> get_lines(): $data is ""
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "220 smtp.gmail.com ESMTP l50sm824677eda.85 - gsmtp"
2017-12-13 08:41:09 SERVER -> CLIENT: 220 smtp.gmail.com ESMTP l50sm824677eda.85 - gsmtp
2017-12-13 08:41:09 CLIENT -> SERVER: EHLO www.cityspotz.nl
2017-12-13 08:41:09 SMTP -> get_lines(): $data is ""
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-smtp.gmail.com at your service, [185.12.13.17]"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-SIZE 35882577"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-8BITMIME"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-STARTTLS"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-STARTTLS"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-ENHANCEDSTATUSCODES"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-STARTTLS250-ENHANCEDSTATUSCODES"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-PIPELINING"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-STARTTLS250-ENHANCEDSTATUSCODES250-PIPELINING"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-CHUNKING"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-STARTTLS250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250 SMTPUTF8"
2017-12-13 08:41:09 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-STARTTLS250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8
2017-12-13 08:41:09 CLIENT -> SERVER: STARTTLS
2017-12-13 08:41:09 SMTP -> get_lines(): $data is ""
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "220 2.0.0 Ready to start TLS"
2017-12-13 08:41:09 SERVER -> CLIENT: 220 2.0.0 Ready to start TLS
2017-12-13 08:41:09 CLIENT -> SERVER: EHLO www.cityspotz.nl
2017-12-13 08:41:09 SMTP -> get_lines(): $data is ""
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-smtp.gmail.com at your service, [185.12.13.17]"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-SIZE 35882577"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-8BITMIME"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-ENHANCEDSTATUSCODES"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH250-ENHANCEDSTATUSCODES"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-PIPELINING"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH250-ENHANCEDSTATUSCODES250-PIPELINING"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250-CHUNKING"
2017-12-13 08:41:09 SMTP -> get_lines(): $data is "250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING"
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "250 SMTPUTF8"
2017-12-13 08:41:09 SERVER -> CLIENT: 250-smtp.gmail.com at your service, [185.12.13.17]250-SIZE 35882577250-8BITMIME250-AUTH LOGIN PLAIN XOAUTH2 PLAIN-CLIENTTOKEN OAUTHBEARER XOAUTH250-ENHANCEDSTATUSCODES250-PIPELINING250-CHUNKING250 SMTPUTF8
2017-12-13 08:41:09 Auth method requested: XOAUTH2
2017-12-13 08:41:09 Auth methods available on the server: LOGIN,PLAIN,XOAUTH2,PLAIN-CLIENTTOKEN,OAUTHBEARER,XOAUTH
2017-12-13 08:41:09 CLIENT -> SERVER: QUIT
2017-12-13 08:41:09 SMTP -> get_lines(): $data is ""
2017-12-13 08:41:09 SMTP -> get_lines(): $str is "221 2.0.0 closing connection l50sm824677eda.85 - gsmtp"
2017-12-13 08:41:09 SERVER -> CLIENT: 221 2.0.0 closing connection l50sm824677eda.85 - gsmtp
2017-12-13 08:41:09 Connection: closed

I’ve updated quantity-input.php to the latest version (v3.2.0), you can find the source code at https://pastebin.com/GK5d5KQe

You can overwrite /wp-content/themes/shopper/woocommerce/global/quantity-input.php with the code from above or, the best solution, is to put it into a new file in your child theme.
E.g. /wp-content/themes/childthemefolder/woocommerce/global/quantity-input.php

@shopperwp please include the updated quantity-input.php, fix the bugs from https://www.ads-software.com/support/topic/please-fix-these-bugs-css-and-translation-bug/ and release an update for Shopper theme. Thanks!

We are running Linux (CentOS).

Screenshot at https://imgur.com/a/QSfMk (same screenshot as my first post in this topic)

I found a (temporary) workaround until this problem is addressed.

1. Deactivate and uninstall the Yoast SEO plugin from your WordPress site.
2. Download wordpress-seo.3.5.zip (which can be found under the ‘Developers‘ tab @ Yoast SEO plugin page)
3. Upload wordpress-seo.3.5.zip to your WordPress site and install & activate the plugin.
4. After activation, configure Yoast SEO as you like and save all Yoast SEO settings.
5. Then update the Yoast SEO plugin to it’s latest version by using WordPress’ built-in updater.
6. After updating the plugin, check all your Yoast SEO settings since there are some additions and/or changes made in the last few versions.

• This reply was modified 8 years, 1 month ago by remi123.
• This reply was modified 8 years, 1 month ago by remi123.

I got the same problem, Yoast setup wizard won’t continue to step 2 and throws an 404 error.
Screenshot at https://imgur.com/a/QSfMk

I’ve enabled ‘No conflict mode’ and added the CSS rules to the child themes’ stylesheet, it’s working now!

Thanks!

So if I understand correctly, there is no way of achieving any limitation/pagination anymore (at Picasa/Google albums) since version 1.55?

I fixed it by adding some code.

Text Domain: nx-admin

needs to be set in the plugin header.

This together with;

add_action( 'plugins_loaded', 'tx_toolkit_load_textdomain' );
function tx_toolkit_load_textdomain() {
  load_plugin_textdomain( 'nx-admin', false, dirname( plugin_basename(__FILE__ ) ) . '/languages' );
}

in e.g. tx-functions.php

Could you update the TemplatesNext Toolkit plugin with the modifications from above?

Thanks for the answer!

I also needed to create an account @ Transifex before I could access the languages’ .pot files.

Ticket to watch: https://core.trac.www.ads-software.com/ticket/31378

Ticket to watch: https://core.trac.www.ads-software.com/ticket/31378

Temporary workaround if you really need to update to 4.1.1: https://www.ads-software.com/support/topic/cant-upgrade-vom-41-to-411?replies=10#post-6589194

Ticket to watch: https://core.trac.www.ads-software.com/ticket/31378

Temporary workaround if you really need to update to 4.1.1: https://www.ads-software.com/support/topic/cant-upgrade-vom-41-to-411?replies=10#post-6589194

For those who are interested; you can watch this ticket regarding this problem:
https://core.trac.www.ads-software.com/ticket/31378

@karlfazzy & Audiofanzine; You’ve got the same problem as I have (and probably many others).

I Guess we’ll have to wait until this problem is fixed;
https://core.trac.www.ads-software.com/ticket/31378