Ok. First, are you wanting to do ‘inline’? or ‘both’? or ’email’? Based on what you said, I’m guessing you want to do ‘inline’, but I’m not sure ..? (For now, I would like you to set it to ‘both’ in order to help me debug it.)
So, I tried your form and received an email with no attachments. That email contained a list of the file titles with a vertical bar between each one. That email, as you noted, is sent by CF7. That is what I call the “notification email”. That email should be going to you (the wordpress admin), not to the web surfer who filled out the form (me in this case). So, in your CF7 form you probably put your-email into the To: field, I’m guessing. Don’t do that. Instead you want that to be the wordpress admin email address. That will make him get the notification email each time someone submits the form.
In my tests, I never received the email that goes to the web surfer (the email that would have attachments). In fact, your system never even tried to send it. So, we can work on fixing that, but there’s not much reason to if you intend to go with ‘inline’ … you only need to fix it if you intend to do ‘both’ or ’email’.
Thank you for the response, much appreciated 🙂
I’d changed the CF7 to try and debug by myself and just haven’t switched it back as yet but will do now.
I was wanting to do ‘both’ which is what it is currently set at. I was wondering if the email had sent, I had sent a test through another contact form which was sending but I had wondering if the issue was bigger.
If you have any pointers that would be appreciated!
it -might- have something to do with the file titles or file names having unusual characters in them (foreign characters). I have never proven that’s a problem, but have suspected it in the past a few times. Let me try it again now and see what I see and will update again. Don’t change anything for a bit…
Ok, so it looks like there is an ajax-related problem. When I hit the submit button, it POSTs the form properly, but the result that comes back is the entire page all over again (all the html for the entire page). If you watch closely, you’ll see that the browser clears the entire page and redraws it (and you’ll note the form is empty). It’s not supposed to do that. Instead, it’s supposed to return (via ajax) a couple of lines of json … just a few bytes … and then update the page in-place, which results in the page not reloading & instead just a bit tacked onto the bottom.
As you can see at this CF7 support post – http://contactform7.com/why-isnt-my-ajax-contact-form-working-correctly/ – that ajax problem is usually the results of either your theme not calling wp_footer(), or some sort of conflict with a wordpress plugin that mucks around with ajax or gets involved in the http traffic somehow, or it’s due to an error on the page somewhere.
I noticed that your page is showing 4 errors when it loads. The first is an uncaught referenceerror saying jQuery is not defined. That is coming from line 104 of theme_scripts.js. The next 3 errors are typeerrors and I’m guessing they might be related to the jquery issue. So, I don’t know if these are really a problem or not .. they may not be .. but that’s where I’d look to start with probably. It looks like theme_scripts.js loads and starts executing, errors, and then jquery.js gets loaded after that as far as I can tell. That may not be an issue, but it might be, not sure. You might need to get jquery.js loaded earlier perhaps.
But, again, that may not be the problem. It could be the wp_footer thing. I don’t really know much about that — you might have to look down in the templates of your theme and see if it gets called or whatever. You might have to go to CF7 support for help on that since I don’t really know much about it..
All that said, you might want to make a new test page and just put a CF7 form on it — nothing to do with EBD. You can use that to test with and make things simpler. Until you get it updating via ajax (and not reloading the entire page) then EBD is not going to work…
Thank you! That at least gives me a lot of information to start testing and working out the issue.
I have a feeling that it might be a larger issue as more things are starting to not work.
