I recently did a self-installation of WP 2.6.2 for my boss. She intends to transfer her old iWeb blog over to WP. The WP blog is now up and running but there is a problem. I am unable to do any file management through WP admin.
For example: I attempted to import the blogs from the old iWeb blog by way of an RSS import. When I attempt to upload the rss.xml, I get the following error:
Unable to create directory /usr/local/pem/vhosts/154599/webspace/httpdocs/wordpress/wp-content/uploads/2008/09. Is its parent directory writable by the server?
I checked the file permissions on the server using the latest version of FileZilla and even other ftp methods. The file permissions were set to allow user and group write. I became frustrated and set them to 775 globally (except the admin folder) just to see if somehow there was some obscure file causing the problem. Still same error.
I contacted the web-host's tech support, but they wont offer any support whatsoever as it is a self-installation. They also didn't seem to give a care about anything I had to say. If it were my site I would switch to a different host. AllDomains sucks!
Another thing worth noting: I tried to set up permilinks but it told me it could not modify the .htaccess due to file permissions. But this one went a step further when I ftp'd to make the chagne... There was no .htaccess, furthermore when I attempted to create my own (simply by copy and past of the code WP gave), I uploaded the file and within 5 seconds it disappeared.
I contacted the tech support on this also and they said that they cannot offer any support (again) but that if the .htaccess was formatted properly it would have been accepted.
So I copied the .htaccess from my own WP installation on my own web-host (which is awesome) and when I uploaded it that disappeared also.
Can anyone help me out here? It seems to me to be a problem with the web-host somehow but they swear their servers are flawless.
Is there some setting I am missing in WP or something?
I don't mind ftp'ing any changes to the template files, but to have to manually port the old blog to the new one would just be crazy!