In article
<
joshuafwhalen-E43...@news.eternal-september.org>,
Sorry for taking so long to get back with you - I was out running around
town with the wife! : )
Ok so I tried deploying your stuff to my own server to see what's going
on. Just for good measure, I sniffed the connection to my FTP server so
I could see the transactions.
From what I can tell, if the "Application Path" field in the Deploy
window is empty, Dashcode tries, and fails, to create the directories up
to the deploy path specified in the FTP Destination (in Preferences),
and then gives up with the error "The folder ³(null)² cannot be created
on the server.". Dashcode obvious has some growing up to do in its
handling of this information.
I still don't see where you are getting the path
"
http://www.occupyeverything.info/~feeds/NYCGA//ftp://fe...@www.cocupyeve
rything.info/~feeds/NYCGA/". But I think perhas you are just putting the
wrong information in the wrong places in Dashcode.
If you type the name of a directory into the "Application Path",
Dashcode will dutifully create it, if needed, and then upload the
content. Then the content will be available on the server in the correct
location.
Here's what you should do:
1. In Dashcode Preferences > Destinations, make sure the Path field
contains only this: /home/feeds/public_html
2. In the Run & Share window, make sure the Application Path field
contains only this: NYCGA
3. Dashcode will assemble the FTP path (/home/feeds/public_html) and the
Application Path (NYCGA) when it uploads the content to get the content
in the right place.