We are using 9.03 at work on XP and VISTA machines.  I'm using the 

beta version at home on a Windows 7 machine.  They are all running OK.

Quoting lkupersmith <forums@adobe.com>:

Doesn't work for me. Installs, but upon running the report I get the 

following error and it freezes Dreamweaver:

Š

Adobe have released the Validator as an extension for Dreamweaver CS5 --- just as Randy had stated.

[Validator extension for CS5 now available@http://forums.adobe.com/thread/661022?tstart=0]

{message:id=661022}

Message was edited by: DavidMozer

Who wants W3C Validator? Yuk!  We want the old validator back.  So far the

best way around it is to stay with cs4.  That's what my office is planning

to do.

Thank you very much for providing the extension.

Like all the developers I know, I find the Dreamweaver validator very efficient to use often during development and then validate using W3C before final launch.

I suggest Adobe consider changing their methodology for selecting their focus groups to insure they represent a better cross-section of their user base.

Thanks again!

Understandable point of view Murray, and good on you and others for pushing rich feature development, though I will say that most people I know, or have read comments/posts/emails from wrt the DW validation tool are all of a similar mind; "It's a fantastic, convenient first step toward validation".

We know it isn't comprehensive, we know it isn't 100% accurate, but it is useful, within the IDE, and picks up basic errors *while you're working on files*.

Let's compare this "convenience feature" to something like Templates - I use them sometimes (when a website is manageable in size) because I can easily go through pages and re-apply them to a Template because, let's face it, Template updates don't always work. I can understand the trade-off between devoting time to improving the DW validation tool and fixing Template bugs. I can't understand the trade-off if it is forwards porting the DW validation tool to a new version of DW, but *not improving it*.

Time vs Money vs Features.

I wish it weren't an issue!

May I humbly ask the DW folks and those who asked to have the validator on CS5 removed: what do you use for HTML validation on local files?

I would ask that you bring back the validator on CS5 (yes the CS4 extension works) and support it, as you did in the past.  Dreamweaver is the go to editor for everyone.  Not just high-end developers who may have the expertise to get around this situation.  Dreamweaver is not only the Maserati of web design, it is also the Volkswagen, Chevrolet, Ford and Toyota for users who need this ability.

I would think there are more of the "ordinary" people who pay for this product than Corporations or higher-end developers.  These are the people who really need this ability to check pages for HTML errors (especially for local files).

I would ask on their (and my) behalf that Adobe reinstate this tool.

Thank you,

Daryl

I dunno. So far, the only solid reasons expressed have been along the lines of "It needed updated, so we opted not to to try."

That's hardly a valid reason. At least, it's not valid from the perspective of delivering a complete, top-notch tool to the paying customers.

Amen @ dreaming-on, The Real Thorzdad, dferny.

The only reason that Adobe would possibly think of removing something like the validator is that they aren't paying enough attention to the workflow of their customers. Seriously, $400 web authoring software WITHOUT a validator? Come on Adobe...

In the past, it has worked great for me, but if it wasn't up to your standards spend a little effort and work to IMPROVE it, dont' remove it.

Doesn't the w3c validator do its job? It's free.

I notice that the W3C validator keeps coming up as a solution . . . the W3C validator is great but very inefficient for use during development. The request to bring back and support a CS5 Dreamweaver validator is all about efficient workflow . . . checking code quickly as we work. Having to cut and paste or validate on a Web page during development is not an option for me.

As someone stated a few posts ago . . . a validator should be a standard feature when buying the top-end html editor out there and paying the prices that Adobe is able to charge.

I dont' have a problem with Adobe's pricing, in fact as a professional developer I like that it's a considered expensive by some . . . but I do believe for the prices we pay basic workflow resources should be provided.

It's great that I can use an extension to use a validator from two versions ago, but why does Adobe think that they don't need to keep the feature current?  I think the answer is simply because they can get away with it . . . some legitimate competition would be a good thing in my opinion.

Other than validating right within the app itself, of course

function(){return A.apply(null,[this].concat($A(arguments)))}

hmhamed wrote:

 

Hi Randy,

 

Thanks very much for supplying us with this information and extension!  I find having the validator within the program it very convenient.

Agreed 100%!

And why is the Validator button there if that feature has been taken out?

I haven't used it (the validator) in a while, but I tried to validate an old page that for some reason is not working anymore. I find this deprecation "mind numbingly" stupid on the part of Adobe.. Yet another WTF moment...

Let's see, late to the party with HTML 5 support, ignoring JavaScript in CS3, CS4, and CS5, no more basic HTML validation.

Clueless. Taking away a basic feature that really doesn't require any development, is a benefit to most on some occasions, and makes life easier for those of us that may have to support old web sites, of which there are about a billion in existence...

Yeah, good move Adobe..

At least someone had enough sense to make it available...

Only problem is that when I try to downlaod it, I am asked for my username and password even though I am logged in, so the page does not let me in. Another bug in the Adobe setup?