Hi-

Our site (chipmagician.com) recently was moved from a Windows server to a Linux server. Since then, forms send just fine, but attachments are no longer working. It shows the file names, but no attachments to the emails. This is a Godaddy reseller type host, so we're using the SMTP relay option, port 25. I've tried without it also, to no avail. I really don't care about the uploading of the files to a folder, but it seems that with the new version of the plugin, I have to choose that option.

I tried using another form plugin, but wasn't even able to get it to send.

When the cforms form sends form sends (http://chipmagician.com/estimates), I get the following file attach error for each individual file:

—

Warning: move_uploaded_file(D:\Hosting\4630070\html/photo-uploads/126-obey-carl.jpg) [function.move-uploaded-file]: failed to open stream: No such file or directory in /home/content/d/e/r/derekprice/html/wp-content/plugins/cforms/lib_aux.php on line 316

Warning: move_uploaded_file() [function.move-uploaded-file]: Unable to move '/tmp/phpMlU0OA' to 'D:\Hosting\4630070\html/photo-uploads/126-obey-carl.jpg' in /home/content/d/e/r/derekprice/html/wp-content/plugins/cforms/lib_aux.php on line 316

—

I know the file folder I created exists. The default cforms folder gives me the same error. Again, we really don't need it to even upload into a folder, but it doesn't seem like the cforms 14.6 even gives us a choice. The files not attaching to the emails are the only real issue.

I'm really at my wit's end here. Anybody?

Michelle said
I'm having a similar issue after upgrading to WordPress 3.5.1 and CForms II 14.6. Uploaded files arrive fine as attachments but aren't saving to the defined directory. Files saved to this designated folder just fine before the upgrades. I wonder if I'm seeing a folder permissions issue.

I have an update. My issues were related to a recent server move. We ended up with two versions of the site, one and the old server and one on the new. File uploads were always working just fine but on a different version of the site than what I was seeing. It's all been fixed now.