esarbege

I, too, am having this problem, exactly as @grimecho, down to the warning and error message even though the API appears in the Gmail Search Console as having been verified 4 times.

I have reloaded the page in the admin area as @slaffik suggested several times. I have also deleted the plug-in and reinstalled it.

Once I did all that, there is a change in the error message. Now it isn’t recognizing the Auth Code or Access Token and still, when hitting the confirm, I get the warning and have to go through the “unsafe” allow on Google. Then, it redirects back to the plugin which indicates all is well until I try to send a test email.

Current error:
Versions:
WordPress: 4.9.1
WordPress MS: No
PHP: 5.6.32
WP Mail SMTP: 1.2.2

Params:
Mailer: gmail
Constants: No
Client ID/Secret: Yes
Auth Code: No
Access Token: No

Server:
OpenSSL: Yes
PHP.allow_url_fopen: Yes
PHP.stream_socket_client(): Yes
PHP.fsockopen(): Yes
PHP.curl_version(): Yes

Debug:
Error while sending via Gmail mailer: {
“error”: {
“errors”: [
{
“domain”: “global”,
“reason”: “required”,
“message”: “Login Required”,
“locationType”: “header”,
“location”: “Authorization”
}
],
“code”: 401,
“message”: “Login Required”
}
}

Any other ideas?

• This reply was modified 8 years, 4 months ago by esarbege. Reason: Additional info

OOhhh, great question, @jgj252! I am also giving the 7-day trial a try and I’d love an answer to this one, too.

@josteinf: I’m having a similar problem.

I am using SiteOrigin’s Live Editor which makes use of the tinymce editor as a widget within layout rows. As long as you enter the [restrict] shortcode above all of the text with closing tag at the end…while in the Editor text mode…(this is important), everything works.

However, if, at any point you switch to the Live View mode to edit the page, the [restrict] shortcode gets removed from its original location into its own tinymce editor widget in a row that gets added to the bottom of the page. That breaks the restricted access. So, be aware that this may happen when you switch back and forth as well.

The only way around this that I have found so far is to hide the page while I am working on it in the Live Editor. When done, copy the restricted code from the errant location, then delete that row, switch back to text mode and paste the restrict code into the correct locations (beginning and end of all text code). Then unhide the page.

Because I want my users to be able to access both the public and private areas, I wanted 2 restricted access pages (2 different member sets) to be listed in my submenu under the login menu item. @etoilewebdesign, is there a way to do this without the above mentioned pain?

• This reply was modified 8 years, 9 months ago by esarbege.