When i enable the module HTMLTidy and try to create content on my site the following error occurs:
"* Failed to find htmltidy executable at '', not using tidy."
I contacted the hostingcompany and they confirmed that HTMLTidy is installed in /usr/bin/tidy and the supporter even tried to set up a testsite and use tidy. He did so succesfully.
I've tried:
- Using htmltidy with other modules such as html2book, token, etc.
- Using htmltidy alone by disabling the other modules
- Using htmltidy alone by removing the other modules by ftp (deleting the folders on the server)
- Using htmltidy on a brand new Drupalinstallation. Removed Drupal totally and reinstalled it. Installed htmltidy - still not working
- Using htmltidy on a brand new Drupalinstallation together with the other modules. Of course this did not work either - but it was worth a try.
Expressed in another way I'm not able to create new content, edit existing content or do any handling (such as editing which menuitem that is parent, who the owner of the contentfile is, who the author is or which date it was created) of any my content when htmltidy is enabled.
Drupalversion: 6.15
MySQL version: 5.0.32
PHP version: 5.2.12-0.dotdeb.0
Apache version: Apache/2.2.3 (Debian)
PHP register globals: Off
PHP Safe Mode: Off
Additionally I have to note that I do not have any configurationoptions of HTMLtidy. The module is not located in /admin/settings and i can't find any configurationmenus.
What to do next?
Comment | File | Size | Author |
---|---|---|---|
#6 | htmltidy-readme-20100328.patch | 1.06 KB | dman |
Comments
Comment #1
mollerz CreditAttribution: mollerz commentedNo answers at all?
No one that haves a clue? Not even the slightest one?
Comment #2
annajonna CreditAttribution: annajonna commentedThe module seems to run at my installation. It reports:
I am planning to upgrade to the development branch and I will report back if I can get it running.
Best regards,
Comment #3
annajonna CreditAttribution: annajonna commentedComment #4
annajonna CreditAttribution: annajonna commentedI installed the development branch and everything seems ok.
The settings are at:
/admin/settings/filters
There You will find a list of the most common input settings:
Filtered HTML and
Full HTML
There is a link to configure Filtered HTML.
Clicking that, brings You to another menu. In there is a tab
called configure.
There are the options You want to change
Best regards,
Comment #5
ak CreditAttribution: ak commentedThis module doesn't work for me either. I don't want a input filter, I'd rather want to tidy the entire drupal output as advertised in the readme of the module. There are no settings anywhere on the site for this, I just see the input filter ones that I don't want. As nothing is tidied up when I look at my output I suggest the html tidy lib is missing, but theres no direct download link provided that I could follow neither a feedback on the reports page of what is going wrong. On the official tidy page I don't know witch version/binary/installer/exe I have to download for my server. I placed several files ans version in a bin directory in the tydies modules directory but my site output didn't change.
I must say I'm kind lost now. Has anybody got some helpful instructions to get this working?
Comment #6
dman CreditAttribution: dman commentedThe "fix everything on output" option was removed in the D6 port. Looks like the README should be updated a bit.
It seems that the only reason you'd need to run the post-processor on output every single page load is if your theme code itself was broken. The real answer to that is to validate your theme code and fix those errors.
This htmltidy logic has instead migrated into only applying to the known-bad user-input. Stuff that people type probably needs repair. Then the repaired code is cached and saved.
It used to be that the settings were global, and the process happened last. Then it was both. Later the inefficient post-processing option was removed altogether. Seems to have been split here: #140599: Making HTMLTidy work in Drupal 5.x
Here's a fix for the documentation
Comment #7
michaelfavia CreditAttribution: michaelfavia commentedThank you. Fixed with small edit for instruction number.