We're experimenting again with our Matrix install, and trying to compose a page with a number of nested content items.
Is there a way to force HTMLTidy to correct validation issues (e.g. <P> instead of <p>, <H4> instead of <h4>) with the nested content?
[quote]We're experimenting again with our Matrix install, and trying to compose a page with a number of nested content items.
Is there a way to force HTMLTidy to correct validation issues (e.g. <P> instead of <p>, <H4> instead of <h4>) with the nested content?[/quote]
Nested content will need to be verified with HTML Tidy on each applicable source asset. HTML is checked and modified at "commit time", not upon access.
Thanks Mark. The nested content items are individual assets being built using asset builders. As far as I can tell the problem with the upper cased tags is actually in the design that's painted on the assets during page creation.
It also looks like we have a problem with our HTMLTidy install - I'm seeing 'HTMLTidy failed to validate this content' ?
[quote]Thanks Mark. The nested content items are individual assets being built using asset builders. As far as I can tell the problem with the upper cased tags is actually in the design that's painted on the assets during page creation.
It also looks like we have a problem with our HTMLTidy install - I'm seeing 'HTMLTidy failed to validate this content' ?[/quote]
This means that the content supplied could not be sufficiently cleaned by HTML Tidy. Please verify that the path to HTML Tidy is correct on the "External Tools Configuration" screen under "System Configuration".
If you are a Squiz client, please lodge a support ticket and so we can take a look at the particular asset and the supplied HTML that is causing this to occur.
[quote]This means that the content supplied could not be sufficiently cleaned by HTML Tidy. Please verify that the path to HTML Tidy is correct on the "External Tools Configuration" screen under "System Configuration".
If you are a Squiz client, please lodge a support ticket and so we can take a look at the particular asset and the supplied HTML that is causing this to occur.[/quote]
Well, I've edited an existing test page, and committed the changes, and HTMLTidy while having the correct path and looking ok under External Tools didn't clean it, so I'll raise a job about that.