I really love the way PhpED parse the project and headlines any errors it finds, many a time has it helped me quickly identify a problem. There is a BUT though, for example:-

On some sites a make use of a CMS system called Perch, it's great as it allows me to easily add CMS features to an existing static site. However Perch uses custom tags in templates such as:-



All the <perch:content xxxxxxxxxxxxxx /> tags show an error.

So is there any way of excluding these and similar errors that show up but which aren't in fact strictly errors?

The problem is that technically Perch breaks HTML syntax standards, so these are strictly errors. Even adjusting the PhpED config files isn't going to help. I tried your example in 4 different HTML editors and all of them interpreted it differently with different errors shown.

NuSphere would probably have to add explicit Perch support. Whilst Perch is popular, it probably isn't so commonly used that I'd imagine NuSphere would be inclined to add support it, unlike Smarty which PhpED does support. If an editor did support Perch, the Perch syntax does actually make it difficult to reliably show issues, because it looks like elements embedded within elements.

Thanks for the reply. Yes I can see the problem and I don't disagree at all that strictly these are errors, there are other examples that arise to that aren't Perch related. On help would be to be able to exclude specific folders form error checking at start up. Most of the tags like this fall in the template folders in the Perch structure. That would at least cut down on the list of errors reported by a faction of 95%. At least then visually scanning the list becomes a non demanding task.

I suppose another possibility is to have a custom entry such as <!--- PHPIDEIgnore: perch:content --> on a page eg:-

<!--- PHPIDEIgnore: perch:content -->

Not ideal I guess as it would then not find legitimate errors in the tags that used such tags.