I submitted a bug report and surprisingly got an answer about 5 hours later! I quote:
Yes this is something which we are working on to fix in an update.
No ETA, but at least they're working on it.
That's why you should always submit a bug report if you find what you think is a genuine bug. The forums are not regularly monitored by Adobe employees, but the bug report form goes directly to the people who matter.
From what I have heard privately, the fix should be available fairly soon. Adobe has been closed for the past week (extended July 4 holiday), but I'm sure the engineers will be back checking the fix on Monday.
Hmmm again, forum took my email, stripped the content to place an empty forum post... edited with my reply...
On 12 Jul 2010, at 10:05, David_Powers wrote:
Make sure you back up your site definitions before applying the 11.0.2 update. It seems to wipe out FTP login details.
It left mine in-place. (EDIT: Sorry, no it didn't : usernames and passwords were stripped), exporting your site definitions before running the update is very good advice!
For those who can't remember how (the UI isn't entirely intuitive for this) repeating the steps I took:
* Site > Manage sites...
* Use Shift-click/Cmd-CLick to select sites from the list for export
* CLick Export...
(In the Export Site dialogue, created a new folder on the desktop)
* Click Save
Although the UI infers it will only save one site, it actually saves each of those you had selected into the folder.
tried sending this reply via email yesterday - the forum appears to be messing up in this regard...
On 11 Jul 2010, at 13:35, David_Powers wrote:
I submitted a bug report and surprisingly got an answer about 5 hours later!
That's why you should always submit a bug report if you find what you think is a genuine bug.
creacog - wrote:
True, but unless submitting bugs within a pre-release environment, don't expect to receive any reply or progress monitoring of a bug-form submission. Hence a reason this forum and this thread are useful
Of course, the forum is useful for conveying this sort of information. Unfortunately, a lot of people are under the mistaken impression that posting here is all they need to do. The only way to bring a bug to the attention of the engineering team is to submit the details through the official form at https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform.
Another way of getting the message through is by posting comments on the Adobe Knowledge Base pages (they have kb2 in the URL). Comments on those pages are normally handled directly by Adobe Customer Support.
>t left mine in-place. (EDIT: Sorry, no it didn't : usernames and passwords were stripped), exporting your site definitions before running the update is very good advice!
Not here. All information intact .. all FTP connection that I tried work. I am running XP SP3 so it could be an OS issue.
although it is always good advice. I export new site definitions to an external (to DW) folder the minute I create them.
Glidewell - since the update I and other team members have used the software without too many issues, so it does seem that this has been resolved.
Would be good if the same sort of fix could be applied to Acrobat!
Great to hear success stories - only nothing has worked for me so far. PC Windows Vista Home Premium SP2 here. An in contact with Adobe Tech help and hope we'll find a solution soon as my trial is running out. I really need Dreamweaver to work before I buy the license. As experiences user, do you think if I just removed CS5 and went for a CS4 instead that would work without all the headaches? I'm really getting fed up with this and rather 'downgrade' than not having it work at all. Any suggestions and insight welcome. Thanks
Same issue as many above. MacBook - Dreamweaver wouldn't open.
I was using the trial version, and wanted to enter my serial number for the paid version. 2 hours to technical support later and I can now open it.
I had to uninstall DW, then re-install it. I still couldn't open it. I don't use FireVault, so that was already switched off. I am set up as an administrator, so that wasn't the problem either.
It turns out I had a corrupt configuration file and had to change the name. So by going into Applications > Dreamweaver >US_en > Configuration - I then changed the name to Configuration.old - then went back and launched DW and it works properly now.
I fixed build 220.127.116.1109 of Dreamweaver CS5 by creating a temporary user account with file vault set to off. Dreamweaver CS5 should open in this user account. Now go to Help>Updates . . and download and install the 11.0.2 patch.
Logging out and then logging in to my primary user account (which has file vault on), Dreamweaver now opens and runs normally. I found I could not run the updater with file vault on, but this workaround enabled me to install the patch described in http://kb2.adobe.com/cps/844/cpsid_84413.html, without disturbing the file vault on my main account.
emt28q5's solution also worked for my OS 10.6.4 machine.
Thanks v much emt28q5.
I ran into this same problem and wanted to post my solution which I haven't seen mentioned on here yet.
First of all, I want to give the background of my situation:
Thanks to Adobe I was able to get my Dreamweaver to working. It had someth
ing to do with the type of computer I have. I have an Acer so they had to go int there and
change some configurations. Now it is working.
I think this will only work if you have a Acer computer. I was told to go to computer>c drive>acer> empowering technology>eDataSecurity>x86> find the file PSDProtect.dll rename it to noPSDProtect.dll...close that then go back to eDataSecurity>X64> find the file PSDProtect and change that name also to noPSDProtect.dll. .....After all that is done then close it then try to start Dreamweaver.
on Mac Pro... cs5 for dw... hate this slow down... there has to be something to fix it.
as a hint for others, copy/paste your work space and snippets then put in new config for a time saver...
extensions are another issues... have to reinstall or reactivate... pita!
Thanks for the info emt28q5. Just a note, if your running time machine you can go to username/libarary/application support/ then delete the Dreamweaver CS5 folder.
Next, go into time machine find username/library/application support/dreamweaver cs5 and restore it.
With emt28q5's post I thought of time machine and came up with the above and it works.
This seems to have worked for me (installing the HTML5 extension pack and verifying permissions - did both at about the same time, so no clue if it was one and not the other or the combo). At least I can open DW CS5 now. Sheesh, for the price, it shouldn't be this hard to get an app to run.
Thanks kanett1963 - I have an Acer Aspire AM5641-E5610A running Vista, Dreamweaver CS5 would not open, just the splash screen and a brief window appearance. I received and downloaded the Adobe update mentioned elsewhere, but that didn't fix it. Your solution worked for me.
For those who need it, here's that Acer-specific fix again:
Rename C:\Acer\Empowering Technology\eDataSecurity\x86\PSDProtect.dll to noPSDProtect.dll
Rename C:\Acer\Empowering Technology\eDataSecurity\x64\PSDProtect.dll to noPSDProtect.dll
No reboot should be required, at least I didn't need to. Thanks again!
Simply go into this folder on your MAC /Users/YOUR_USER_ACCOUNT/Library/Application Support/Adobe and rename the Dreamweaver CS5 folder to something like "X-Dreamweaver CS5". this will force Dreamweaver to create a new Dreamweaver CS5 folder. Voila.
Joe9inety....you are an angel! THANK YOU FOR POSTING. THIS WORKED FOR ME!!
Can't believe we pay so much for Adobe software, and to think it's now October 2010, and the issues are still there!!!
I renamed my CS4 folder to CS5 after trashing the current CS5 folder, it worked like a charm indeed.
I don't think I would ever want to support adobe again. If anyone knows of good alternatives, please post. It seems like the better Adobe try to be, the worse they actually become...sad.
Europe, Middle East and Africa