1. Open up your FTP client. If you do not have one, you can download Filezilla, a free FTP client.
2. The information below is an example and is as if your publishpath.com address was http://testing.publishpath.com.  You will need to substitute the information below in RED with your publishpath.com address that you signed up with. If you do not do this, it will not work.

• Host- ftp.publishpath.com
• Username- your email address/testing.publishpath.com
• Password- the password you use to login.

Note: Only users with the Administrators role will be able to log in to the site via FTP.

Noteworthy features:

• It will only allow uploads of files within a whitelist of extensions.  How was the whitelist determined?  It is the aggregate of all the whitelist extensions currently imposed on your CMS through the web interface.  That whitelist is currently:
  • zip, txt, html, htm, js, css, ico, xml, swf, gif, jpg, jpeg, bmp, png, aif, aifc, aiff, asf, asx, au, avi, class, flv, m1v, m3u, mid, midi, mov, mp2, mp2v, mp3, mpa,  mpe, mpeg, mpg, mpv2, mvr, rm, rma, rmi, rmv, snd, wav, wax, wm, wma, wmp, wmv, wmx, wvx, doc, docx, pdf, xls, xlsx, ppt, pptx.
• It will only allow uploads of files with sizes of 250 megabytes or less.
• It takes into account your website's storage limitations.  If you're over the limit, it won't let you upload anything.
• It will not let you delete files from any special directories.  For instance, when you attach a file to a blog post, it gets stored in the system as /Blog/<contentID>/<filename>.  Since these directories have special meanings you can't touch 'em.  You can download from them, however.
• You can create and upload to any directories you want outside the special directories.
• The templates directory is NOT marked as a special directory.  There will be complete freedom in this directory to add/delete files.  This will enable you to directly edit your templates and designs in the text editor of your choice.

What if I run into connection issues?

When you try to connect to the FTP server you get one of the following error messages: No connection could be made because the target machine actively refused it. Connection closed. Connection timeout. No response from server.

Causes/Solutions

FTP server settings

The error is occurring because there is no server listening at the host name and port you entered. Check that you have specified the correct host and port.  Port 21 is the default FTP port. 

Software/Personal Firewall Settings

Another common reason is that a firewall software (Microsoft OneCare, McAfee Total Protection, Norton Internet Security, etc) running on your system is stopping your FTP client from making outgoing connections. To fix this problem add your FTP client to the list of allowed applications in your firewall software.

Multiple Software/Personal Firewalls

If you have Windows XP firewall enabled and a third party firewall software (e.g. McAfee Total Protection, etc.) installed, disable the Windows XP firewall or uninstall the third party firewall software. There are known problems with having both firewall applications running at the same time.

Anti-virus Software

If you are running anti-virus software and having strange problems connecting, disable the "Worm protection" in Norton Anti-virus. If McAfee VirusScan is installed and the "Spyware Plugin" is enabled, go to McAfee VirusScan Console and uncheck the "Prevent FTP outbound" option in the "Port Blocking" dialog of the "Access Protection Properties".  You also might need to add your FTP client to the exception list.

LSP Layer

Software firewall applications and other utilities hook into the LSP layers of Winsock. If the hook is not properly written, connection attempts may fail under certain situations.

The solution is to identify and update the application causing the problem. Spyware and adware are known to hook into the LSP layers as well. To remove them install and run Ad-Aware. To manually remove LSP hooks install the LSP Explorer add-on for Ad-Aware. This procedure is recommended for experienced users only. It's easy to break the system.

Router Firmware

This is an unlikely case but a buggy router firmware may cause exactly the problem described above (e.g. Linksys). To fix it update the firmware of your router. You can usually update the router firmware in the router web administration interface or visit the manufacturer's website for router updates and further information.