Posted by andrewsuth on October 18, 2009 at 2:51pm
Jump to:
| Project: | htmLawed |
| Version: | 6.x-2.7 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | alpha2zee |
| Status: | closed (fixed) |
Issue Summary
I've been trying to get my HTML pages to output using the 'tidy' option of htmLawed without success.
I added 'tidy'=>-1 to all of the default configurations (Body, Comment, etc) but it doesn't change the outputted HTML for the pages; it continues to show the HTML with tabs and a lot of spaces. I then tried to add the above configuration to individual content-types and selected the Filter content during page-display option but the results are still the same.
Any ideas what I am doing wrong?
Comments
#1
Hi,
I just re-tested the latest version of the module against a fresh, and otherwise-3rd-party-module-free installation of Drupal 6.14 on a Mac OS X 10.5/PHP 5.2 setup, and I don't see any issue.
The in-built htmLawed module settings were not changed, so for all content the 'Default' settings are used. The 'Default' settings were, however, edited by appending:
, 'tidy'=>-1
to the Config. fields for 'Body', 'Comment' and 'Other'.
Please re-check and let me know. Thanks.
#2
I've done this and am still not getting any results.
Any idea of where I could look to find the issue?
#3
Sounds silly, but can you confirm that htmLawed is working in your setup? E.g., do tags not permitted as per the 'Config.' field value actually get filtered. Also, can you tell me what other filters are enabled for the input format?
#4
I will bite on this issue... I too cannot get htmlawed to do 'safe'=>1, 'elements'=>'a, em, strong, cite, code, ol, ul, li, dl, dt, dd', 'deny_attribute'=>'id, style', 'valid_xhtml'=>1, 'tidy'=>-1
I would expect my formatting to be rendered all left aligned with line breaks after each tag, but it is not. Instead I simply see the original formatting. Additionally I tried 'safe'=>1, 'elements'=>'a, em, strong, cite, code, ol, ul, li, dl, dt, dd', 'deny_attribute'=>'id, style', 'valid_xhtml'=>1, 'tidy'=>'2s2n'
Since what I really want is mozilla compliant soft tabs.
#5
Subscribing. Thanks
#6
I have again tested the htmLawed module in an otherwise 3rd party module-free Drupal 6.14, and I do not find an issue with the 'tidy' setting.
I created an input format that used just the line-break converter followed by the htmLawed filter, and tested the input format on a post of the 'Page' content-type. The default htmLawed 'Body' setting was
'safe'=>1, 'elements'=>'a, em, strong, cite, code, ol, ul, li, dl, dt, dd', 'deny_attribute'=>'id, style', 'valid_xhtml'=>1, 'tidy'=>'2s2n'I also tested 'tidy' values of -1, etc.
As described in the htmLawed doc, 'tidy' of -1 compacts the HTML (removes white spaces), '2s2n' pretties it using two spaces for each indentation, with a leading indentation of two spaces for the HTML block, and the '\n' newline character, '1t' pretties using a tab character for each indentation, with no leading indentation and the default '\n' newline character, and so on.
Though this is apparent, I want to clarify that the htmLawed filter works only on the user-submitted content. E.g., with the 'tidy' option, only the user-submitted portion of the final Drupal-rendered web-page will have its HTML compacted (or beautified, depending on the 'tidy' setting).
#7
In my case it was a conflict with drupal filters. Perhaps you should clearly stated that default HTML filter and corrector should be disabled to avoid problems since the problem persisted after reordering.
Thanks for a very useful module.
#8