What was the problem before (what did you fix)?
Currently, the form is working when you select either download, but not both. When you select both, it’s returning a 500 Internal Server error. I can’t see what the error is. It will be in your logs somewhere — probably your apache error log. If you’re on shared hosting then it’ll be in cpanel somewhere. We need to see what the error message is to figure out what’s happening.
Aside from that, you could try setting it to ‘inline’ and trying again (selecting both downloads). You could also try setting it to ’email’ and trying again (selecting both downloads). That might narrow down if the problem is related to the email or not (since you currently are on ‘both’). Also, I think you should remove the ‘Before’ and ‘After’ stuff … I assume you did that in the EBD settings for HTML before & after, right? You haven’t modified email-before-download.php or download.php have you? Assuming no, then you should take out any customization template type things you put in the EBD settings (save them off in a text file somewhere so you can put em back later) — try to get those settings back to the default of empty. Also, have you tried both masked url and not masked?
Previous problem was that the form was not submitting at all. A change of footer has solved that issue.
The issue is definitely email as inline works fine (I will switch to this temporarily to get it working). Masked url and not masked has made no difference to email it still hangs.
I will try and access the report log unfortunately i don’t have cpanel access (legacy thing) but do you have any other ideas or am I stumped without that?
I would guess that if you turn off attachments then it would work on email, but that’s just a guess.
There’s really no way to know what the problem could be without seeing the error message (assuming there is one). It might have something to do with the way email gets out of the system that you’re on — maybe it won’t accept multiple attachments or it tries to scan them or who knows, could be anything.
On some hosting providers you can still get to the apache error log via your ftp login. The error log directory would be above your public_html directory (I’m assuming your website files are in there). So, like a directory up from there might have like a logs directory and in that might be an error_log file or something like that. All of this varies by quite a bit, so it’s difficult to say for sure.
You -might- be able to turn on wordpress debugging and make the errors & warning go into a file and it might catch the problem. It will store the errors in a file called error.log or maybe error_log most likely. That file will get dropped in the directory of whatever program is executing when the error happens … that will most likely be down in the plugins/email-before-download directory somewhere, but could be somewhere else. Note that there could be several of those files dropped in various places. EBD sometimes produces messages & warnings that are “normal” and will make the error.log file show up but won’t be related to your 500 internal server error problem. Thus, tracking down the right error.log (if it exists) might take some work… Anyway, if you scroll down this page to the Enable PHP Debugging part it will show you what you need to do to turn on php debugging & (hopefully) get it to drop those messages in a file you can access: http://www.makeuseof.com/tag/the-ultimate-guide-to-solving-500-internal-server-errors-and-blank-white-pages-in-wordpress/
Remember to remove those changes to get the debugging turned off after you’ve turned it on and then run a test to make the problem happen.
