What kind of attitude on the forums is that?
"It's either your fault or theirs"
Huh??
Nobody knows what YOU could have done to your own computer.
So trying to pass some drivel off like that as fact is about as elegant as the things you will find on the ground in cow a pasture.
The reality is if you care to read up on it is that Dreamweaver has had cache and preferences issues from day one. Adobe knows this and many on the Dreamweaver development team have stated that these issues will be gone when CS5 releases (albeit the release will probably have a new name and it looks like we won't see it until maybe Fall).
As far as your episode being a continuous barrage, there's probably more complexity to it than just blaming one or the other. I have on occasion had the cache issue. The only time I have had the non-cache issue was because of my own doing.
If you have had the non-cache issue where you are just getting JavaScript errors, this is likely because you have a corrupt configuration folder. While reinstalling some extensions may fix it short term, this is not the preferred way of handling it.
The real solution would be to first rename the configuration folder to something like configuration-old. Then Dreamweaver will automatically create a new one on the next startup.
Then, reinstall the extensions and you will likely have fixed your barrage issue.
