[support] HTML filter and <table> tags

Metzler, David metzlerd at evergreen.edu
Thu Sep 20 15:45:20 UTC 2007


Yep,  I think if you change from escape all html (which I think ignores
the allowed tags by design), and then clear your cache, you'll be ok. 

You will need to clear your cache.  Mysql> delete from cache; 
Alternatively download the devel module to do this.  There's a block for
clearing the cache in that module. 

I verified the exact same behavior with this configuration on my own
site, and was able to fix it using these steps. 

Dave

-----Original Message-----
From: support-bounces at drupal.org [mailto:support-bounces at drupal.org] On
Behalf Of Chris McGinlay
Sent: Wednesday, September 19, 2007 3:45 PM
To: support at drupal.org
Subject: Re: [support] HTML filter and <table> tags

On Wednesday 19 September 2007 22:30, Metzler, David wrote:
> Take a look at your input format configuration first.  (Admin->Site
> Configuration->Input formats) Configure the filtered html input
format.
>
>
> If you look at the configure tab, you likely have filtered html set to
> escape all tags, and that table tags are not listed in the "Allowable
> HTML tags" field.  Be sure to list all tags you want to pass through.
>
> I might also recommend changing this to "Strip disallowed" rather than
> "Escape all tags".
>
> Hope this helps.
>
> Dave
>
Thanks for the rapid reply. I've checked my filter settings again. My
allowed 
tags in FilteredHTML are
<a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <table> 
<caption> <thead> <tr> <th> <td> <img> <blockquote> <span>

I do have it set to escape all tags at present. It seems all HTML is
being 
escaped, regardless of filter. 

http://www.swantrust.org.uk/history

Even the <a> tags are stripped in the above post, which is real bad.
I've just 
noticed that my book posts are now no longer showing the normal book 
navigation mechanism. I wonder if these are linked issues?

Chris
>
> -----Original Message-----
> From: support-bounces at drupal.org [mailto:support-bounces at drupal.org]
On
> Behalf Of Chris McGinlay
> Sent: Wednesday, September 19, 2007 3:14 PM
> To: support at drupal.org
> Subject: Re: [support] HTML filter and <table> tags
>
> On Wednesday 19 September 2007 21:05, Metzler, David wrote:
> > Couldn't help but notice that not all your pages are affected.
> >
> > 2001 Tall Ships Leg2 looks bad.
> > 2003 St. Andrew's looks good.
> >
> > So it seems like something in the editing process.  My bet is some
>
> kind
>
> > of check_plain being executed in the code somewhere. But are the
>
> tables
>
> > really related to image_assist in some way?  Are the pieces of
content
> > all using the same input format?
> >
> > I can't think of a reason that image_assist would affect tables.
> >
> > Also, are you using a wysiwyg html editor, or are you hand editing
the
> > content.
> >
> > Dave
>
> Thanks Dave, the ones that look good (as you pointed out above)
actually
> have
> input format set to Full HTML, which is not what I want. The content
> <table>
> and related tags are hand edited, no WYSIWYG on that site. Only auto
> generated code was from img_assist.
>
> Disabling img_assist (just tried that) makes no difference. Sigh.
> Looks like I will have to try to recreate the problem on a fresh test
> installation.
>
> Chris
> --
> [ Drupal support list | http://lists.drupal.org/ ]
-- 
[ Drupal support list | http://lists.drupal.org/ ]


More information about the support mailing list