WYGWAM image upload not working on the "send it to server button" in 1.3.1

Edit Subject

Brandon, here is the exact problem I am still having (complete with screenshots). I thought that other thread was about the same issue and it had a lot of attention so I was posting there. Thanks for your help. Right now the version that I have installed is the one from your github profile.

Hey Brandon,

I'm still having this issue and haven't gotten it sorted out. Not sure where to look at this point.

Thanks!

I'm running Wygwam 2.1.4 on ExpressionEngine 2.1.0 build 20100810, and I'm getting this exact problem.

The upload/Send to Server upload simply gives me an "invalid file" error, but if I go in to browse images I can upload them through the CKFinder.

I've checked that my Upload directory is set to 777 and Wygwam set to 755. The upload directory allows both images and other files, and the files I'm trying to upload are way below the upload limit.

In addition, I just switched this site from my development server to the client's GoDaddy Linux Hosting account. I had other GoDaddy problems before so that may be where the issue lies, but any insight would be appreciated.

Thanks!

Can you check your Javascript console and see if you're getting any JS errors on the page?

Hi Brandon,

Looks like I'm getting a total of three errors:

1. Failed to load resource: Operation could not be completed. (NSURLErrorDomain error -999) - associated with connector.php
2. [The HTML that caused this error was generated by a script.] Extra encountered. Migrating attributes back to the original element and ignoring the tag. - associated with index.php:1
3. [The HTML that caused this error was generated by a script.] must be a child of . Content ignored. - associated with index.php:1

Any insight there?

Okay, so just as an update. I currently am using www.mydomain.com and www.mydomain.com/system as the site url and backend url. When I removed the www from the /system URL in the general configuration, it no longer gives me the Invalid File error.

However, I need the site to officially be www.mydomain.com/system and my clients will be accessing the backend this way. It's working just fine for me, but I'm worried about other issues caused by URLs not being the same. I'll keep everyone informed if any problems come up.

The important thing is that you're accessing the CP from the exact same domain as the "URL to your 'themes' folder" setting in Admin > General Configuration. You can put a redirect in your .htaccess file that enforces it.

The themes folder was definitely the fix. I always thought it was the System URL that mattered, but now everything's in order and working properly. Thanks!