I'm open to trying any crazy solutions you guys can come up with, so let me have em.
I know that Hak5 uses domain.com as their hosting, and they really enjoy domain.com. I do too. Mostly. Actually, for everything except this specfic issue. So I'm not here trying to flame domain.com, they're a great host, and I'm sure they have their reasons for why they keep telling me this isn't anything they support.
I come here looking for creative solutions that don't involve me switching my hosting to linux (I have .net web apps and for that I need a windows host).
My problem is that on my windows hosted website I have a wordpress installation that I plan to heavily modify, and as such can't use the one-click install that domain.com provides.
This wordpress installation has a particular problem with uploading images from within wordpress using their media manager. Specifically I receive an error indicating that the file was unable to be written to the wordpress's upload folder from the temp upload location.
Seems pretty straight forward, probably a permissions issue right? Well you aren't wrong. It is a permissions issue.
The issue is that the owner of the upload folder, differs from that of the user php is running under, so when php tries to write the uploaded image to the upload folder, the user doesn't have permissions to the folder.
Domain.com's web based admin panel, does not provide the ability to alter the owner of the upload folder. The only permission's it allows you to alter are the groupings of anonymous web user, application pool identity, and the ftp user.
The only permissions I can assign to these groups are the standard 'read', 'write', and 'execute'.
It was suggested by Domain.com's support people that I use FTP to upload the images, which is all fine and good, but that's a lot of extra work to upload the images via ftp, and then log into the wordpress install, go into the media manager, load the image into wordpress and then attach it to my post or use it in the post.
I know I can't be the only person to run into this issue, and I know that there has to be a better solution than what was suggested by their support team.
Does anyone have any ideas?