There's nothing to add to the Japanese thread. You've already translated my earlier comment. All I know from my contacts inside Adobe is that they're investigating. There is no solution yet.

I don't know if it's related, but the Mac version of Dreamweaver was built using Carbon, the old Mac API. Adobe is in the process of converting Dreamweaver to the Cocoa API. I don't know how far the conversion process has got, but Dreamweaver CS5.5 certainly uses Carbon for some, if not all, parts of the program. Until Dreamweaver is completely "decarbonized", I imagine there will always be a danger of things breaking when Apple releases a new version of Mac OS X.

I'm also experiencing this and I just wanted to mention, it seems when a file is copied and then pasted, the original file icon appears. Granted it doesn't make sense to copy and paste your entire site just to get the icons to show, but on a per-file basis this works.

To bring back the lost icons (on Mac) - go to your user configuration folder for DW, (~user/library/application support/adobe/Dreamweaver/en_US/Configuration) and edit the Extensions.txt file by adding JPG,GIF,PNG,PDF to the first line (should be the line with ':All Documents')

Now files show up with DW icons and the thousands of console errors are not being generated.

Adobe should be embarassed that such a simple solution wasn't found by them for this issue. I, like many others have found the lack of communication by Adobe in supporting its products, a major negative for their company. And their lack of support will be reflected in my willingness to give them money for their products.

I think you misunderstood the thread. We're talking about file icons not showing up inside Dreamweaver's FTP browser, not files we've associated with Dreamweaver. I'm also not getting any console errors.

You guys are talking about two different things. The solution posted by crocketj (correct me if I'm wrong) is for files that you want to open with Dreamweaver not displaying a Dreamweaver icon in the finder.

The problem that mentlity has, which this thread is about, is ALL file icons not appearing inside Dreamweaver's FTP browser.

These are two totally seperate issues and one solution doesn't fix the other.

I was looking at the original post which shows icons not showing in the local view (not the remote view). But for my situation, it fixed the problem for both the local and remote view (on my laptop and my tower). If this solution doesn't work for others, sorry... good luck in finding a solution.

I can confirm that the solution posted by crockej does indeed work, I am not by any means saying that it is a perfect solution, and am sure that it is not the actual fix, but it does work, I landed up having to add JPG,GIF,PNG,PDF,SWF,FLA,ICO,SWZ,MPR,PSD,XLSX,INDD,AI all to fy file list and although this was 90% of the missing icons fixed, it still requires more like m4v etc.

Think of this as more of a temporary solution to the problem, but it does work.

This is what my /Users/XXXXX/Library/Application Support/Adobe/Dreamweaver CS5.5/en_US/Configuration/Extensions.txt file looks like now.

Well, on my system the solution of hackintoshUser and crockej doesn't work at all. Sorry. The file panel still looks the same, also after a restart of the computer. I am the author of the original post and I am running Dreamweaver CS5.5 on Lion.

Same system here, I am using Apple Lion 10.7.3 build (11D50b), I made the alteration with Dreamweaver CS5.5 closed, opened the file with a raw text editor called text wrangler, because I think a text editor like text edit might just change certain headers etc of the file, made the alterations and saved the file over the original. Launched Dreamweaver and it worked.

What text editor application did you use, I would only suggest bbedit, text wrangler, or nano / pico through terminal, these ways you will not change permissions or headers of the file you are editing.

Sorry, I am unsure as to why this is not working for your particular situation, could be multiple reasons, like maybe your Dreamweaver was installed for the root user, or possibly this solution will not work if you have more than 1 user, I am not sure, but happy that it worked for me. Sorry we will have to wait for Adobe to give us all a far better solution to this issue.