Support

Home Forums Event Espresso Premium Cocoa error 3840

Cocoa error 3840

Posted: February 8, 2014 at 4:51 pm


David Short

February 8, 2014 at 4:51 pm

Error 3840 when trying to login using the ipad app.

I have checked the plugins and all seem fine.

Ideas on next steps?


Tony

  • Support Staff

February 10, 2014 at 1:30 am

Hi David,

Which version of the app are you using currently?

You’ll need the HD version and the latest is v1.6.2


David Short

February 10, 2014 at 8:48 am

Yes, that is the version I am using…..


Josh

  • Support Staff

February 10, 2014 at 8:55 am

Hi David,

Is the endpoint URL that you’re entering when you log into the app the same address where WordPress is installed?


David Short

February 10, 2014 at 9:33 am

Yes, minus the wp content. Same URL.


Josh

  • Support Staff

February 10, 2014 at 9:41 am

There shouldn’t be a wp-content in either case. Can you let us know the URL that you’re entering as the endpoint URL?


David Short

February 10, 2014 at 9:45 am

you bet. http://absecllc.com


Josh

  • Support Staff

February 10, 2014 at 10:22 am

Hi David,

I checked the JSON API event feed, and this is being output into it:

WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory.

This is potentially breaking the JSON feed and causing the error you’re seeing.

You could try fixing the WP super cache installation, -or-

1) Go into the WP super cache settings and set it to disable caching then

2) Deactivate the WP super cache plugin for now.


David Short

February 10, 2014 at 10:28 am

Hmm.. This makes sense. I switched providers to wpengine.com and wpcache is on their list of non approved plugins.
http://wpengine.com/disallowed-plugins/

I recently had some interaction with their support staff, where they blamed EE for performance issues on the backend. They supported their assertions with SQL logs and stated that EE doesn’t play well with caching on the backend. This would explain it.

Now, the question would be this: Am I able to run this without WPCache? it is not installed nor running….

Thanks for the rapid responses, Josh!


Josh

  • Support Staff

February 10, 2014 at 10:41 am

You definitely shouldn’t run wp super cache on wpEngine hosting. WP Engine caches for you. With that, you can ask WPEngine support to disable caching for the main registration and payment pages (the URLs are in Event Espresso>System Status) to avoid other issues.


David Short

February 10, 2014 at 2:36 pm

They have disabled caching for my entire site. Performance has significantly improved on the backend. Unfortunately, still getting the 3840 errors…..
Thoughts?

David


Josh

  • Support Staff

February 10, 2014 at 2:48 pm

Hi David,

Have you set the wp-super-cache plugin to no longer cache and then after that disabled it? (Not WPEngine’s internal caching, the wp super cache plugin that is installed). If you take a look at the event JSON feed and scroll to the bottom, WP super cache is still throwing an error.


David Short

February 10, 2014 at 2:55 pm

Right, so the wp-super-cache plugin doesn’t exist on my WP install. The files are not in the directory, nor is the plugin shown in the dashboard. This may be an artifact of my previous host? I was with GoDaddy until I had some really bad site performance issues that made me go with my current provider……
The plugin isn’t installed and hasn’t been for some time.


Josh

  • Support Staff

February 10, 2014 at 3:42 pm

Hi David,

There could be artifacts from the previous install. Was WP super cache installed there before? If so, WP Super Cache does add files to the wp-content directory, and it also adds rules to the .htaccess file (which I think WPEngine will ignore what’s in the .htacess file).

The author of the WP Super Cache plugin posted some step by step instructions on how to manually remove the files it adds:

https://wordpress.org/plugins/wp-super-cache/other_notes/

I’m thinking it’s likely what’s in wp-content/wp-cache-config.php may be causing the issue that you’re seeing in the JSON event feed.


David Short

February 10, 2014 at 4:24 pm

Great work Josh. The 3840 error is gone now. I’m getting a 404 “not found” error, but that is something that I can work with.

I appreciate the support!!

The support post ‘Cocoa error 3840’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

Event Espresso