zoon_unit wrote:

 

I am using Dreamweaver CS5 with Drupal 7.4.  The new version of Drupal fixes the old problem of Dreamweaver not being able to find related files, BUT ONE BIG BUG REMAINS.

 

Whenever one edits a CSS file and tries to save the saves, Dreamweaver crashes.  This behavior is consistent and has been happening since CS5 was released, both in Drupal 6 and 7.  This persistent bug basically makes Dreamweaver USELESS for editing Drupal files.

 

How in the world has this bug missed the numerous bug updates that Dreamweaver has released???  The whole reason I purchased Dreamweaver was to integrate with Drupal!!

 

Does anyone have a workaround for this problem??

Can we see the CSS file?

Is this happening with all CSS files related to Drupal?

Have you installed all the latest patches for CS5?

What OS are you running?

What testing server is involved?

Is the testing server on your local machine or elsewhere?

If you have extensions, besides the HTML5 one from Adobe as part of 11.0.3, can you disable them to ensure the are no conflicts?

Are you receiving an error during the crash? If so, from the OS or from DW? What is the error?

Your post gave us nothing about your situation other than to state you believe to have found a bug without any way for people to reproduce, test and see if it occurs again.  The more information you can provide the more likely we are to find a resolution to your problem.

I can confirm the same thing happens with Wordpress development.

Currently I'm working on a wordpress site in live view and tried to edit css and it's crashed 15 times in alf an hour.... I'll have to edit the css file manually with no other files open, very inconvenient.

You'll then go for a while and it doesn't do it. Adobe have fixed the crashing when connected to a sftp server, a year after cs5 release but this bug is just being ignored, all they are interested in now is making more money out of cs5.5, a useless upgrade for those of us in business.

It annoys me how a company can get away with charging for such buggy software. It's like saying to an owner of a new car "yeh mate, we know the gearbox keeps jamming in your model but we're too busy working on the next model.... we'll let you know when it's out and you can buy another one to solve the problem"

Then when you buy another one, we'll introduce some more bugs because we tried to release it too quick and couldn;t be arsed to test it properly.

p.s. mac os x here, did it in snow leopard, does it in lion

Sure hope Adobe is working on it.

No Adobe isn't working on this particular problem and the main reason is

that you don't use DW to edit any CMS websites.  They all have their own

framework to create, edit and host the sites automatically.

If you guys didn't know this then clearly you need to spend some time to

familiarize with the CMS systems and how they work to get maximum

benefits from them.

DW is fantastic to create, edit and host static sites and even

Microsoft's Expression Web 4 can't compete with DW in this respect IMHO.

hth

Is this an official adobe reply or your OHO? Anyways, it sounds like you are advising to ignore a definitely buggy behavior in an otherwise superb piece of s/w, while calling people who report the issue...ignorant? And does Drupal let you edit CSS in its GUI and visualize the page like DW does? Not to my knowledge. Do share if there is a secret trick.

JTANNA how completely misinformed you are. It's you, not us who should take time to familiarise yourself on how CMS websites work.

CMS is content management system, a system designed to manage website content without accessing code. If you take a look at adobe's website you will see they promote dreamweaver as a tool to use with Wordpress CMS, Drupal etc and live view is one of the prominent features.

Intact you wouldn't need live view if building a static website as you can see what you get on every page, it isn't database driven like CMS.

We create complete custom themes for CMS systems, something the system itself cannot do. We basically create the templates and add pup to interact with the system. Live view shows us how everything looks when the content is pulled together.

I should also point out that a CMS system doesn't host a website, a hosting company does just like a static site, however with CMS MySQL servers are required and php support.

I hope this helps you understand, pease do not be so quick to tell pro's in future we do not know what we are doing.

Ps I reported originally via the bug report form quite a few times before it got noticed

And then when Adobe finally contact you after submitting about 200 crash reports and 50 bug reports… they ask for your crash logs

After my discussion with them (nice guy) they took my files and didn't even say thank you! I spent quite some time dealing with them and even more time lost on the crash problem.

Not forgetting i paid a high price for the product (like you al) in the first place…

I run my business slightly differently as I need to keep my clients! :-o

After a long live discussion with Adobe, demonstrating the problem and many weeks of waiting…. the problem has finally been resolved for us.

We are using Wordpress CMS with Dreamweavers Live view, kept crashing.

Since the latest Lion OSX upgrade, all seems fine. All I can assume is that Adobe and Apple had some kind of conflict and have worked to resolve this.

The same may apply to Drupal, ensure you upgrade to 10.7.2

I will get to direct email address to the guy at adobe who I dealt with.is there a way of messaging you direct

Does Adobe really think we're going to keep putting up with this kind of false advertising??  I've decided end my upgrade policy with Adobe because of these kinds of shenanigans.  I was willing to pay them $100+ for a Dreamweaver upgrade to 5.5 to fix this issue, but much to my SURPRISE, I was not able to upgrade Dreamweaver alone because it is part of a Suite.  So, to fix ONE SINGLE bug, they expect me to pay them $400.  Sorry, ain't gonna happen........

 

 

Remember your customers Adobe!

If you want to continue using DW then you should stick with static websites.  To use dynamic websites and to design templates with DW, requires a lot of intelligence which judging by the sort of questions asked suggests this is not in abundance here.

I stand by what I said before: 

DW is fantastic to create and edit static sites and even

Microsoft's Expression Web 4 can't compete with DW in this respect IMHO.

Somebody said that you can create templates in DW for CMSs.  This is balderdash because template designers don't use any tools.  All they use is simple text editor.

So now one less customer for Adobe because he can't manage CMS sites in DW.  Good riddance.

hth

JTANNA you nob

If someone chooses to use DW for cms websites it doesn't give you the right to slag off their ability as a developer just because you choose to use a text editor.

Infact I hand code php etc and use very little of Dreamweavers actual features. However I choose to use live view for ease of seeing my changes as I update css and templates. In conjunction with localhost it works very well.

Do you see me slagging off other peoples abilities just because you choose to use a text editor or cssedit, or another app?

No you don't.

So if someone CHOOSES to buy DW because they advertise compatibility with Wordpress or Drupal, then that product should work with those platforms as stated.

Just because you don't choose to use them doesn;t mean Adobe should get away without fixing bugs.

You're simple a speck of dust on a shelf which will soon be dusted.

WhenI used CS5 the issue I had a discussion on skype with Adobe to demonstrate. Around 3-4 weeks after Apple released an update to OSX which resolved it.

You are right, it does happen on some themes and not others, but if you are using CS5, ensure you are at least on Lion with all updates applied (including any java updates)

After this the crashes were only when Dreamweaver decided to completely freeze up every now and again (always when I hadn't saved!), however the regular crashing from css editing mostly stopped.

Report it here https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

They do sometimes reply too