Also, error_log
[02-Mar-2016 13:01:13 UTC] WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 1 for query SELECT * FROM wp_mcebd_item WHERE id = ;
This looks like it’s not being passed any ID’s for the document.
So the problem seemed to lie in the Contact Form somewhere.
I’m using Contact Form 7.
I created a new form from scratch and that worked so I slowly started adding my custom form settings into the new form and waiting for something to go wrong. Nothing did.
I’m not 100% sure why that fixed it but for anyone else having trouble, try using a brand new contact form then slowly customising it and checking.
Good luck peeps.
Great, glad you figured it out and got it working. Couple of comments:
A few people have reported problems where the most recent WordPress upgrade broke their existing Email Before Download setup. Those people were all using something other than “your-email” as the field name in the CF7 form for the email that the web surfer would type in to the form. Changing their forms to put your-email in there fixed it for those folks. Some of those people were set for ‘inline’ (not ‘both’ or ’email’) so it’s not exactly clear why they would need to have your-email in there (since nothing is emailed), nor is it clear why putting it in there fixed it. My best guess is that the “your-email” thing didn’t actually do anything, but they somehow got a new CF7 form ID or something like that and that’s what actually fixed it, though I can’t prove that.
It’s difficult to explain, but EBD may end up pulling “old” data out of the database because it pulls based on IDs. Thus, it might miss some changes you did or keep pulling old bad data out of the database. That is why it is often helpful to start completely over — get a new CF7 form (so you get a new ID), reupload your files so they get new IDs (I usually tell people to give them different filenames too), etc. Essentially, make everything brand new, which is similar to what you did to fix things for yourself.
Anyway, glad you got it working…
Interesting because I was just using [email] rather than [your-email] when it stopped working.
Thanks for the info.
I referenced this thread in the one I created earlier this morning for the exact same issue. This helped me tremendously, so I wanted to link them in case it helps someone else. Here’s the link. It is indeed the name of the email field that causes the issue (if it’s set to anything other than ‘your email’). I initially wanted to blame my new hosting at Rackspace…my bad, Rackspace.
