Linting / Syntax Error Checking

[Paul-M]

I tested Linting in DW CC 2018 it only works when I save the document. If I understand correctly it should work while editing the document by default (Note I have not made any changes to default limiting preferences.

Also l note that if I open a document with php extension the language defaults to php in the linting status bar, if I change it to html it still won't report html errors.

[Nancy OShea]

That's how Linting has worked since 2017.

Nancy

[osgood_]

Energize  wrote

I tested Linting in DW CC 2018 it only works when I save the document. If I understand correctly it should work while editing the document by default (Note I have not made any changes to default limiting preferences.

Also l note that if I open a document with php extension the language defaults to php in the linting status bar, if I change it to html it still won't report html errors.

LInting in any editor you can name is crap at best, especially when you have html, php, javascript etc in one document. Live linting has not worked in DW since CC2015, you now have to save the document

Whilst linting may help identify some issues it will not identify every issue. The only sure way of checking is running the page via the W3c validator. That is the only validator with any credibility - all the inbulit 'interpretation' validators, in every single editor I've ever used. are mostly rubbish.

We had editors in the past just pushing the open page to the W3c validator with effective results. I have no idea what have happened to current editors save to say they have taken a few setps backwards in a lot of areas.

The workflow I now use is setting my local server up to catch any php errors, the browser console to identify javascript errors and the wc3 to report any html errors after the page has been complied

[Nancy OShea]

To check HTML code in .php files, use Live Code and run Live Document Validation.  See screenshot.

NOTE:  You will need a local testing server to work with Live Code in PHP files

[Paul-M]

Maybe I'm explaining this wrong.

Live Linting is NOT working in DW CC 2018, the output panel only updates when I save the document (CTL+S) it does NOT update as I type.

Live linting works fine in DW CC 2015

In CC 2018 is this be design or some glitch/bug or a setting I don't know about possibly?

I have NOT edited/touched any of the default linting preference files

I exported the same site from CC 2015 and imported it into CC 2018 to test, so nothing to do with the site settings either

[osgood_]

Energize  wrote

Maybe I'm explaining this wrong.

Live Linting is NOT working in DW CC 2018, the output panel only updates when I save the document (CTL+S) it does NOT update as I type.

That's how it now works in the current version of DW. You need to save the document rather than as in previous versions i.e., 2015 the linter identified potential errors as you typed.

[Jon Fritz · Accepted solution]

There is no Live Linting function in DW any longer. It was removed in CC2017.0 and has not been re-added to the program.

If you feel strongly about it, make sure to start, or support, a feature request over in the DW Feature Request/Bug Report forum...

Adobe Dreamweaver CC: Feature Ideas

[Paul-M]

That's a retrograde / backward step, all part of the shambles of shoe-horning Brackets into Dreamweaver when it had a perfectly solid code editor that just needed some TLC and a few new features.

[Jon Fritz]

Half of the "errors" that come up in DW's linter aren't errors at all, that along with the "no longer firing when you change code" are the main reasons I stopped using it all together after CC2015.

I'd rather use Firefox's html validator plug-in when I preview since it's based on the W3C validation tool, if I'm going to be forced to save my file to see issues anyway.