codesmithsf

Here it is for the autosave call that works. General:

Request URL: https://mydomain.com/wp-json/wp/v2/pages/440/autosaves?_locale=user
Request Method: POST
Status Code: 200 
Remote Address: my.ip.addr:443
Referrer Policy: strict-origin-when-cross-origin

Response Headers:

access-control-allow-credentials: true
access-control-allow-headers: Authorization, Content-Type
access-control-allow-methods: OPTIONS, GET, POST, PUT, PATCH, DELETE
access-control-allow-origin: https://mydomain.com
access-control-expose-headers: X-WP-Total, X-WP-TotalPages
age: 2
allow: GET, POST
cache-control: no-cache, must-revalidate, max-age=0
content-security-policy: upgrade-insecure-requests;
content-type: application/json; charset=UTF-8
date: Tue, 18 Dec 2018 22:17:37 GMT
expires: Wed, 11 Jan 1984 05:00:00 GMT
link: <https://mydomain.com/wp-json/>; rel="https://api.w.org/"
server: nginx
status: 200
strict-transport-security: max-age=300
vary: Origin
via: http/1.1 obfustacated.secureserver.net (ApacheTrafficServer/7.1.2 [uSc sSf pSeN:tOc  i p sS])
x-content-type-options: nosniff
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-port: port_10645
x-robots-tag: noindex
x-sucuri-id: 11018
x-wp-nonce: 20464aac7b
x-xss-protection: 1; mode=block

Ok – I clicked on the Troubleshooting tab and clicked the “Enable Troubleshooting Mode” button. I then went to Pages – Add New. In the Gutenberg editor I entered a Title and then text in the “body” area below. Clicked “Save Draft” and get a red bar with “Updating failed” text.

BUT when I went back to the list of Pages and I see the post listed there. I edited the new page again, made some changes, and then waited. The page “auto-saved” and I see a greyed out “Saved” in the upper right. Went back to all pages and see the changes I made. So saving does seem like it worked despite the error messages.

I went back to Health check and disabled Troubleshooting mode. Went through the same process – got error messages when trying to manually “Save Draft” yet when I got back to the list of pages I see my changes.

I tried to Publish the page. Get a red bar and “Publishing failed” message. I went back to the list of all pages. The page is still in draft mode.

Hope this helps!

Moving to PHP 7.2 made no difference. Still had the same errors when saving content in Gutenberg.

Another issue was that while testing we were never getting the ability to prove that the tester *wasn’t* a spammer. We’d just get a generic error message and “please try again later” and no way to submit the form.

Thanks for the reply. I tried Sockets but not working – see below. Not sure why curl can login using pop just fine but sockets returns an error. Hosting platform is WP Engine if that helps.

getemails: Connecting to pop.gmail.com:995 (pop3-ssl)
getemails: procol: pop3-ssl
pConnection: mailbox: INBOX
Connecting via Socket
Socket: tls://pop.gmail.com:995
Socket error: 0 - 
Socket: POP3
socket read (0) :
Socket: attempting a secure connection
socket write: STLS
socket read (0) :
socket write: USER [email protected]
socket read (0) :
getemails: The username and password provided were not accepted for the POP3 server pop.gmail.com on port 995

• This reply was modified 7 years, 10 months ago by codesmithsf.

Hi – let me know if I can provide more information about the Verification email not being sent. Not sure if this is an issue with the plugin or with the hosting server. It’s curious that according to the email log (great plugin btw) that the To: email is being scrubbed.

Thanks.

Ok thanks for idea to install the “email log” plugin. I did that. I see the successful submission when logged in. I see the reason it’s not working for non-logged in users is because we have “Require Email Verification for Guests” turned on. In the email log, the To: is empty. View screenshot.

Thanks!