Needs review
Project:
HTML Tidy
Version:
7.x-1.0-beta2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
23 Apr 2012 at 21:04 UTC
Updated:
17 Jan 2014 at 05:27 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
colanComment #2
jneubert commentedStumbled upon this in a simpletest environment with multilingual text. It gave me a very hard-to-track-down PDO error (inserting something into messages table failed).
Could be fixed with the attached patch (against beta2)
Comment #3
mgiffordThis looks like a pretty straight forward patch.
Comment #4
colan@mgifford: If you RTBC it, I'll commit it. ;)
Comment #5
mgiffordThat patch didn't apply neatly. This one should.
Comment #6
mgiffordI'm not sure where the problem for this is but in my local testing environment I got a WSOD & this Error message
on
But that might be a problem with the git repo or my local install.
Comment #7
dman commentedTesting (it's been a few years since I used this - and in D7 I usually have been trusting the htmlcorrector module and the wysiwygs)
* Downloaded current dev via git
* Enabled module on a brand new standard site
* Edited the text filter to enable it. admin/config/content/formats/full_html
* My binary was auto-detected OK
* (DISABLED htmlcorrector for testing) Enabled verbose debugging. Shifted htmltidy filter to the bottom.
* No WYSIWYG or anything is on.
* Added a page with crappy markup
... Um, nothing happened - I just got the bad text back out at me, filter didn't run.
Is the current code broken? drush+git gave me by default. 7.x-1.0-beta2
.. And on revisiting the page to edit it again I got
I think I'll try the -dev and see what's up.
(forgive my noise, this may just be my confusion, but following the WSOD at #6 I thing we are on shaky ground with this old thing.
Suggestion - we can put a link to the repository INSTALL.txt in the project page, I had to go read it to remind myself what to do
Comment #8
dman commentedMy error was unrelated and due to debugging option being on #1687846: drupal_set_html_head() should be drupal_add_html_head() for D7
BUT, I'm still not seeing the expected result - code is not being fixed by the filter, on preview, view or save.
Yet I do see the deprecated warning now so something is running.
Yes applying this patch makes the warning go away.
But is the module still working as an input filter?
Comment #9
dman commentedOK, looks like my sample bad HTML was too atrocious. Less-bad HTML does get cleaned up. HTML that is beyond help seems to fail silently though. :-(
It gives up when it sees
That is another issue.
This issue/patch however does indeed fix the split() warning :-)
Sorry for adding noise. It just looked like a quick test :-}
Comment #10
mgiffordIt would be great if there was a sample page with bad html in it to try this against.
Good to know that the patch fixes the issue at hand. Bad to know that there are still a bunch of other issues with the module.
Comment #11
colanI added that as the Documentation link. It's not showing up, but that's probably because we have to wait for the cache to clear.