Written.com

Hi Michelle –

Can you send me a quick email with your blog domain? My contact is [email protected].

I can make sure you get taken care of.

Thanks,
Connor

Hey Steve –

Can you make sure that you have the latest version of our plugin installed? Just to be sure, it doesn’t hurt to delete the plugin completely, and reinstall it by searching for it in the WordPress plugin repository in your wp-admin Plugins section.

If that does not resolve the issue, it sounds like there may be a server configuration error on your site. Can you contact your web host and see:

• Do they allow remote requests over HTPS using cURL?
• Ask them if there are any firewalls in place that would prevent an API request to https://written.com
• Also, If you are using any firewall plugins (such as Better WP Security), you should disable them, or adjust the configuration to see if that helps resolve the issue.

Hey Kevin –

Can you check now to see if you are still having this issue? Of course make sure you are running the latest version of the plugin (3.0.2) – it may be worthwhile to delete our plugin and reinstall it from the WordPress repository to make sure you have the latest version.

The SSL certificate on our end is configured correctly, so there might be a slight misconfiguration on the server where your blog is hosted. If you are still seeing this issue the best bet would be to reach out to your web host to ask the following questions:

• Does your web host allow remote requests over HTTPS using cURL?
• Is there any firewall in place that would prevent API requests to https://written.com?
• Does the server that your site is on currently have the most up to date curl libraries installed including the latest CA root certificate to validate SSL?

You can also send your web host this article: https://snippets.webaware.com.au/howto/stop-turning-off-curlopt_ssl_verifypeer-and-fix-your-php-config/ which will better outline the issue from a technical standpoint.

Please let me know if you have any questions, and if any of these resolves the issue.

Thanks,
Connor

Good to hear! Let us know if you have any other questions/issues.

I think I found your blog. It seems yours is connected just fine.

Are you still receiving the error message when you click “Sync”?

What is your blog domain?

Hello,

Can you make sure that you have the latest version of our plugin installed? Just to be sure, it doesn’t hurt to delete the plugin completely, and reinstall it by searching for it in the WordPress plugin repository in your wp-admin Plugins section.

If that does not resolve the issue, it sounds like there may be a server configuration error on your site. Can you contact your web host and see:

• Do they allow remote requests over HTPS using cURL?
• Ask them if there are any firewalls in place that would prevent an API request to https://written.com

Also, If you are using any firewall plugins (such as Better WP Security), you should disable them, or adjust the configuration to see if that helps resolve the issue.

Hi all –

I apologize for a delay in reply here.

This issue has been resolved in 3.0.2.

Please feel to reach out to us directly at [email protected] if you run into any other issues with the plugin.

I noticed this as well.

You can also notice the slow down in new relic:

https://chood.co/fYnF/1G6wj27d

Blue is “time in redis” (although it lists it as memcache, this is because new relic lists redis as memcache for some reason)

As you can see, enabling redis object cache caused significant slow down.

It seems the winner for my setup is switching to APC caching.

Hello!

Connor here from Written. I am one of the co-founders of Written, and I also manage all of our technology including our plugin.

I wanted to address your concern regarding the user our plugin creates in your WordPress account. The user we create does not give us access to your site, it allows us to interact with your site via the XML-RPC interface in WordPress so that we can properly manage content licenses on your behalf (and with your permission, always).

If and when you deactivate the plugin, our deactivation script runs which deletes this user from your WordPress install. If you force delete the plugin via FTP, this deactivation script may not run which means the user is not properly deleted as you observed.

As far as why you did not receive any correspondence from us after you signed up, please accept my sincerest apologies! I am forwarding this thread along to Drew who manages our blogger outreach process, and we will make sure you we get back in touch with you today.

Please email me with any questions ([email protected]) and I am very sorry your first experience with us wasn’t so great. Hopefully you can give us another try.