Is there Tidy support in a new item asset? It is using the WYSIWYG to add text, but it does not convert special characters such as & and therefore throws up some errors. Is there any way to turn off the WYSIWYG for the News Item asset, or make tidy work for this? I have Tidy installed, and turned on.
It sounds like the WYSIWYG attribute (which is what the News Item is using) is not passed through Tidy when its saved. Could you log a bug for this?
Support is checking this before I log it as a bug…
Ok, we got tidy fixed and working. But I thought that Tidy would make everything XHTML compliant, such as changing a <br> to <br /> this is not working. It does close tags and such, but I thought our test system before made everything XHTML compliant.
[quote]Ok, we got tidy fixed and working. But I thought that Tidy would make everything XHTML compliant, such as changing a <br> to <br /> this is not working. It does close tags and such, but I thought our test system before made everything XHTML compliant.
[right][post=“15132”]<{POST_SNAPBACK}>[/post][/right][/quote]
Tidy should be making everything XHTML compliant. Remember to check on the frontend – not in WYSIWYG editor. Also, I recommend checking with Firefox and not Internet Explorer as IE tends to screw up HTML when you view it.
I checked the front-end and it was correct. Was getting mixed up looking at the source in the WYSIWYG.
[quote]I checked the front-end and it was correct. Was getting mixed up looking at the source in the WYSIWYG.
[right][post=“15140”]<{POST_SNAPBACK}>[/post][/right][/quote]
Yeah, the WYSIWYG Editor changes the code back to (bad) HTML4. Its one of the reasons we have HTML Tidy in the first place. 
I see this post is quite old. Any ideas if this is going to be fixed or if it is on the drawing board? i.e. when using the WYSIWYG editor, code view, XHTML code is stripped out (e.g. <br /> becomes <br>) Not very good for validation :blink:
[quote]when using the WYSIWYG editor, code view, XHTML code is stripped out (e.g. <br /> becomes <br>) Not very good for validation :blink:
[right][post=“15994”]<{POST_SNAPBACK}>[/post][/right][/quote]
The WYSIWYG Editor will never be XHTML compliant. This is why HTML Tidy support is built into Matrix. The HTML code is submitted by the WYSIWYG editor to HTML Tidy, which then makes it XHTML compliant.
Always do your validation on the front-end output code. That should be XHTML compliant, assuming HTML Tidy is enabled and working.
What did you do to get it working? I don't get any tidy icon for the WYSIWYG in my summary or body divs for my news items and as such my <br> tags aren't valid in the frontend.
Just discovered that I get an HTMLTidy message of "unable to validate this content" for new pages I'm creating as well. Old pages appear to validate fine.
Update: If I modify existing pages that have ben validated (green tidy icon), when I commit them, they are suddenly no longer validated.
This usually means there is a configuration problem with HTML Tidy, either it is no longer executable or the binary has changed and is not returning the correct data. If you are a Squiz client, you may want to log a support request so that we can take a look at it for you.
I'm not a squiz client.
Tidy runs fine from the commandline against html files without any problems.
Just checked my apache error_log and get the following:
HTML Tidy: unknown option: p
HTML Tidy: unknown option: r
HTML Tidy: unknown option: s
HTML Tidy: unknown option: r
HTML Tidy: unknown option: v
HTML Tidy: unknown option: -
HTML Tidy: unknown option: t
HTML Tidy: unknown option: t
HTML Tidy: unknown option: s
Error: Can't open "yes"
On the External Tools configuration screen, are there any red warnings?
Nope. Tidy trying to run from /usr/bin/tidy.
Anything in your Matrix error.log file?
Only lots of lines about a favicon.ico not found
Hmmm. What has changed since HTML Tidy worked?
The only thing I can think of is that I have upgraded to 3.16.0. I tried checking tidy on a fresh 3.16.0 install and the same thing happens there too.
Ok, we'll need to wait for Greg -- this may have to be logged as a bug.
You'll need to upgrade HTMLTidy so Matrix can use a new command line arg.