This is a user-to-user forum. So, although your rant has helped you let off steam, you're addressing the wrong people. To report a bug to Adobe or make a feature request, use the form at http://www.adobe.com/cfusion/mmform/index.cfm?name=wishform. The form goes directly to the development team. The more people request something, the more likely it is to be fixed.
Actually - as a community professional likely hired by Adobe - why don't you pass this information on. Just dropped a huge amount of money on the full master suite and I'd like to think I paid for something. Here I'm using Dreamweaver CS5 and still the same crappy FTP timeout issues. I'm sticking with Cyberduck, but this is the reason real web developers don't take Adobe serious.
Community professionals are not hired by Adobe. They are Adobe customers like you and me.
For the record, I have used Dreamweaver's FTP module on Windows since DW3 (1999) without any issues.
Doesn't help you or others experiencing issues but since it doesn't affect all users, it's obviously not a trivial issue to fix for every user in every scenario.
Irish Spacemonk wrote:
Actually - as a community professional likely hired by Adobe - why don't you pass this information on.
As John Waller has pointed out, Adobe Community Professionals are not Adobe employees. FWIW, I do pass on a lot of feedback to the Dreamweaver engineering and product management teams, and improvements to the FTP features are high on the agenda. The advice that I gave the OP to submit a feature request is, in fact, the most effective way of getting the message to Adobe. Requests and bug reports submitted through that form go directly to the Dreamweaver team, whereas comments/complaints posted here won't necessarily be seen.
I feel your pain. Using Dreamweaver CS5 and FTP STILL SUCKS. HARD. I get time out errors regularly, and each and every time if I try the same thing right away with Cyberduck it works just fine. Weak sauce, Adobe.
I agree with the people who have shared their negative experiences with the ftp client in Dreamweaver. I too have had horrible experiences with it. I always assumed wrongly that I was the only one.
For me,it is quite disappointing the program does not allow for FTPS connections to increase security with better speed than SFTP. Apart from that the timeouts are cruel when you are just trying to save a file online for testing purposes to get the job done.
What all these users and I as adding my voice to this thread have done is expose the ftp client in Dreamweaver for what it truly is. A piece of trash for at least some of its users.
Because of this, working in Dreamweaver is a love / hate relationship. The ftp client in this case falls within the latter category.
It is sad to see that Abode has grown so complacent with this product that they could care less about one of the most critical elements to efficient programming for some of thier clients.
Never, it works fine.
I've used it since mx and it work fine for me, never have had any issues with it.
and now dreamweaver has the BC module placed in it, it makes working on that platform as well even easier.
perhaps you just havent spent the time to fully understand it all, or are just too impatient and get all clicky and thats when it fails.
Perhaps you might want to actually take the time to read my post instead of putting your less than helpful comments? There are many people having this problem and I am unfortunately one of them. I did not say it was a problem for all users as it is clearly not based on your less than helpful reply. There is clearly a problem for some users and I am unfortunately one of these users.
Quite frankly, I have spent all the time I wish to on this issue and your comments about my impatience or willingness to understand are invalid. You see, I have been working with computers for a very long time including building and customizing my own servers over the past 20 years so I'd like to think I know how to use a "lowly" ftp client my friend. That part of your reply is quite laughable.. so thanks for the good hearty laugh with your false assumptions...
Again, I assert my original point in that this part of the program is terrible for some users and its lack of FTPS support is really lagging. Even programs like AllwaysSync (of which I have no affiliation) -- which must have a fraction of the budget that Adobe must have -- has FTPS in its program.
If you wish to be helpful, I would love to know how to get FTPS working within Dreamweaver? (Not SFTP) Please share with me that gem of knowledge and I will be quite grateful.
Perhaps you might want to actually take the time to read my post instead of putting your less than helpful comments?
cool it soldier, my post was in relation to the ORIGINAL post. not yours.
but you do raise some valid points. yes it does not handle FTPS to the best of my knowledge. but any site I've needed to use that for I'll use an external ftp program. my point about impatience, was actually directed to the first poster, not you. and it still stands.
I use passive FTP mode
note - not sftp
note - not you Elehost
Thanks for your reply. Sorry I made an incorrect assumption on my end about you replying to my post.
By the way, I am very glad it works fine for you as that must be so nice to not have these issues I am experiencing.
If Adobe does decide to address these issues then adding FTPS would be so great to have built in. I agree with you about using an external program but I was trying to avoid that. I think adding in a more flexible error handler with multi-connections would speed up the process dramatically. Some of these basic features are in many ftp clients and have been for many years.
I have no problems with any other ftp clients from the same machine so this issues has me stumped. I do have a lot of problems with timeouts in Dreamweaver which made me assume the problem was with Dreamweaver by matter of simple logic. This seems like a fair assumption in my view.
If there is a setting I am missing I sure would love to find it but after spending a good amount of time on this, I have to admit I gave up finding a solution (for my purposes). I would say at least 25-50% of the time a transfer fails or times out. I am sure you can appreciate the amount of wasted unbillable time this adds when one is simply trying to publish a page on-line.
If there is a setting I am missing I sure would love to find it
You're not missing a setting. Dreamweaver does not currently support FTPS. However, Adobe is aware of demand for FTPS, and I would be very surprised if it's not supported in the next version of the program.
I think we are getting a little 'off topic' here. We have established that some users have problems with the FTP module so instead of unhelpful suggestions, passive aggressive and 'holier than thou' comments, how about a reply to the question and stop passing the buck.
I found http://computersettings.net/tag/dreamweaver-cs5-not-conneting-to-ftp-server which may be a solution.
The problem is intermittent so not a setting issue - most likely to do with some network config.
Putting 'wishes' in the Adobe suggestion box is really a 'non-starter' - I am sure they are aware of the problem and a solution/work around already exists.
The problem is that the FTP client isn't up to snuff with most other FTP applications and there is always a chance of having the issue. Remember, it wasn't that long ago that Dreamweaver added the ability to continue working on files while you FTP them. (Ah, the good old days.)
I will say that I experience the problem more on my Mac than my PC, but I think that has to do with hours spent on it. If you Google "dreamweaver ftp times out", you'll find that it's FAR from an uncommon issue.
I've been having this problem since it was a Macromedia product. I filed many bug reports on it then. I've filed many bug reports on it since then. It's not getting fixed.
At the root of the problem is the fact that every other FTP program that I use or have used just work. They just do. So we've got that expectation. I plug in information into FileZilla and... boom. Just works. Fetch... same thing. The list goes on and on.
Good luck getting this fixed, but it's things exactly like this that a lot of us moaned about before Adobe absorbed Macromedia. Personally, there's been a lot more good fallout than bad, but such is life.
In short... not getting fixed, don't get your hopes up, but keep complaining enough and maybe it will eventually!
Well said Snapperh3ad...
I completely agree with the last person's reply based on my experience with the FTP client in dreamweaver.
It's a little buggy yes.
[personal info deleted, forum policy]
Wow, a lot of response since that original post.
I've been a web professional for the last 13 years and have been using Dreamweaver since version 2. The FTP client has always been a buggy "POS." I have worked with tons of developers and designers who all agree, that is why pros use a dedicated FTP client like FileZilla in tandem.
I just think it would be nice to be able to hit the "put" button while I am working on a file without having to wait for timeouts and all the garbage that happens in Dreamweaver. There really is no rhyme or reason why these timeout errors happen to me, but I have found over the years that certain FTP sites and / or networks I am on will give me more problems than others.
What is consistent though is that EVERY TIME I have one of these problems in Dreamweaver I can jump to FileZilla and upload the same file without any problems at all.
Now, my question — Is it really THAT difficult for Adobe to create a reliable FTP sub-program inside of Dreamweaver since they have had several years since they bought Macromedia to do so? You would think it not to be that difficult considering the complexity of most of the software in their suite.
All of the file management in Dreamweaver sucks. Their implementation of SVN is pretty much completely useless as I have tried using it more than once and always revert back to command line or Cornerstone to do my version control. I can't imagine the future rollout of FTPS to actually work at this point.
Other than those issues I really like dreamweaver but I am getting to the point I may just jump ship and use a code editor like BBedit or something along those lines. Its hard to break old habbits and the workflow you are used to though.
Has anyone tried out CS 5.5? Is it any better? I am running CS 5 and there is no difference in the FTP client from previous versions in that respect.
I realize some people have trouble with DW's FTP but I don't. It has consistently worked well for me on both XP and Vista OS.
Do I occasionally have dropped transfers? Sure. Everyone does. My ISP alleges my DSL speed is approx. 19mb/sec but it typically falls way short of that illusive number. Additionally, errors sometimes occur when my Anti-virus is doing it's thing in the background. That's hardly something I can blame DW for.
Just my 2 cents.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
[personal info deleted, forum policy]
I disagree. The reason you have dropped transfers is probably due to DW. I have never (not even 1 time) had a dropped transfer using Filezilla. With DW itconsistently happens. The other problem is that dreamweaver doesn't allow/use simultaneous transfers making it EXTREMELY slow. In Filezilla you can set to a maximum of 10 simultaneous transfers. That means you can upload/download 10x faster than DW. I'm assuming they don't allow this because of check in/out feature.
Dreamweaver FTP is erratic and doubles time spent.
Maybe they've made it too 'clever' for some servers? ...explaining why simple Fetch etc is comparatively faultless.
but DOES ANYONE HAVE A SOLUTION???
(please do not post Adobe's troubleshooting page!)
I have never (not even 1 time) had a dropped transfer using Filezilla
I definitely have. I've watched it drop transfers.
I've been using "dreamweaver" since it was "home site" (I think made by allaire or macromedia)
read this adobe. Dreamweaver FTP sucks and it always had.
I've been using it for a lonnnnggg time, and DW FTP is consistently inconsistent.
it's gotten WORSE with CS4
for all the machines I've had; from windows 95 - 7. macromedia DW, DWMX .. etc. ALL. yes ALL of them would time out, take forever to connect.
I've had 25MB cable, 256 DSL and every make of router you can buy at a consumer level.
Each time, cuteFTP, ws_ftp, fetch, or the built in windows ftp, or filezilla ALL work faster to connect, and work more consistently than DW ftp
I won't even BUY a copy of DW since the built in FTP is a huge source of frustration.
(my major complaint, aside from an otherwise okay web tool)
for my needs eclipse, running cfEclipse is a FAR SUPERIOR solution.
I'm not sure WHY.... but if you are frustrated with DW FTP, you are not alone, and it's not the passive/active setting in DW.
just use filezilla (or another open source FTP client that works well)
stop buying adobe products until they fix them properly.
I know I did.
I agree with Tommy, it actually may be that they made it too clever for some servers. I also had my battles with it
I would love if someone came you with a brilliant soultion.
Does any have a solution for DW FTP modul. It dosent work on my danish server, have been trying for long time and it dosent look like anybody knows about in Denmark or Næstved. If any danish people read this please contack me
[personal info deleted by mod, forum policy]
Seven (7 !!!!!!!) years later and the module is still buggy and IMHO no better than the Macromedia Version. Not just connections, but also rather "simple" things like maintaining the FTP log aften just fail on my CC subscription DW, ie log output gets corrupted or (more often) it just stops. The upload might continue, but the log just stops. Not that big a deal, but it's concerning nonetheless. Ie this happens:
And the display just stops there. Note how the "Putting file" msg at the top is already at 783xxx, but display is still stuck on 502xxx - This happens to me whenever I upload large number of files, regardless of server or account.
And while we're talking about uploading a large number of file, how about a progress bar?
I also fail to see the logic in some of the restrictions imposed on me, ie expanding a local folder while something else is uploading. Why would I have to wait for server activity to finish to see local files?