Hi,
For some time I had <table> tags in a 'page' posted on a drupal site, working fine.
Today, although I have not edited the site, the <table> (and related) tags are being escaped.
http://www.swantrust.org.uk/node/14
My filter order is HTML 0 Line break converter 1 Inline Images 10
The node is set to 'filtered HTML'. My allowed HTML tags are:
<a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <table> <caption> <thead> <tr> <th> <td> <img> <blockquote> <span>
So the table tags should NOT be stripped.
I'm running Drupal 5.2
Cheers Chris
On 9/18/07, Chris McGinlay chris@ascentsoftware.org.uk wrote:
Hi,
For some time I had <table> tags in a 'page' posted on a drupal site, working fine.
Today, although I have not edited the site, the <table> (and related) tags are being escaped.
Did this happen after an upgrade or after moving/importing the database on a different server? Does editing and saving the node correct that? Does this also happen with new nodes created, or only with existing ones?
My filter order is HTML 0 Line break converter 1 Inline Images 10
The node is set to 'filtered HTML'. My allowed HTML tags are:
<a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <table>
<caption> <thead> <tr> <th> <td> <img> <blockquote> <span>
So the table tags should NOT be stripped.
I'm running Drupal 5.2
Cheers Chris
On Tuesday 18 September 2007 22:13, Cog Rusty wrote:
On 9/18/07, Chris McGinlay chris@ascentsoftware.org.uk wrote:
Hi,
For some time I had <table> tags in a 'page' posted on a drupal site, working fine.
Today, although I have not edited the site, the <table> (and related) tags are being escaped.
Did this happen after an upgrade or after moving/importing the database on a different server? Does editing and saving the node correct that? Does this also happen with new nodes created, or only with existing ones?
Hi, thanks for response. A few days back I upgraded img_assist from 5.x-1.4 to 5.x-1.x-dev (due to incompatibility issue with image-5.x-1.4)
Editing the nodes in question doesn't make any difference. Newly created nodes also suffer the same problem. Full HTML works, but I really don't want to enable that all over the place.
Chris
On Tuesday 18 September 2007 23:10, Chris McGinlay wrote:
On Tuesday 18 September 2007 22:13, Cog Rusty wrote:
On 9/18/07, Chris McGinlay chris@ascentsoftware.org.uk wrote:
Hi,
For some time I had <table> tags in a 'page' posted on a drupal site, working fine.
Today, although I have not edited the site, the <table> (and related) tags are being escaped.
Did this happen after an upgrade or after moving/importing the database on a different server? Does editing and saving the node correct that? Does this also happen with new nodes created, or only with existing ones?
Hi, thanks for response. A few days back I upgraded img_assist from 5.x-1.4 to 5.x-1.x-dev (due to incompatibility issue with image-5.x-1.4)
Editing the nodes in question doesn't make any difference. Newly created nodes also suffer the same problem. Full HTML works, but I really don't want to enable that all over the place.
Chris
Shameless bump! Anyone?
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
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Chris McGinlay Sent: Wednesday, September 19, 2007 1:50 PM To: support@drupal.org Subject: Re: [support] HTML filter and <table> tags
On Tuesday 18 September 2007 23:10, Chris McGinlay wrote:
On Tuesday 18 September 2007 22:13, Cog Rusty wrote:
On 9/18/07, Chris McGinlay chris@ascentsoftware.org.uk wrote:
Hi,
For some time I had <table> tags in a 'page' posted on a drupal
site,
working fine.
Today, although I have not edited the site, the <table> (and
related)
tags are being escaped.
Did this happen after an upgrade or after moving/importing the database on a different server? Does editing and saving the node correct that? Does this also happen with new nodes created, or only with existing
ones?
Hi, thanks for response. A few days back I upgraded img_assist from 5.x-1.4 to 5.x-1.x-dev (due
to
incompatibility issue with image-5.x-1.4)
Editing the nodes in question doesn't make any difference. Newly
created
nodes also suffer the same problem. Full HTML works, but I really
don't
want to enable that all over the place.
Chris
Shameless bump! Anyone?
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
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
-----Original Message----- From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Chris McGinlay Sent: Wednesday, September 19, 2007 3:14 PM To: support@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
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@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Chris McGinlay Sent: Wednesday, September 19, 2007 3:14 PM To: support@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/ ]
just noticed that my book posts are now no longer showing the normal book navigation mechanism. I wonder if these are linked issues?
Chris
Sorry, my error with user permission caused the book problem! I'm obviously too tired and getting a bit irrational in trying to fix this. Problem with allowed HTML tags in HTML filter not being allowed persists.
Stopping for tonight though!
Chris
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@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Chris McGinlay Sent: Wednesday, September 19, 2007 3:45 PM To: support@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@drupal.org [mailto:support-bounces@drupal.org]
On
Behalf Of Chris McGinlay Sent: Wednesday, September 19, 2007 3:14 PM To: support@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/ ]
On Thursday 20 September 2007 15:45, Metzler, David wrote:
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.
Hi David,
Thanks for that. Changing as you specified, clearing cache tables in database did the trick. Perfect.
Chris
If you are interested in a Adobe Dreamweaver third-party extension for novice to advanced theme developers please contact me privately. This extension would aim to ease the development time in creating simple to advanced templates for Drupal 5/6 and so on if there is enough interest. When you contact me please let me know if this would be for work, personal use or both and how much would you be willing to pay for something like this extension?
I apologize in advance for the cross post but I need these responses as soon as possible.
Thank you,
Peter Apokotos
-
Chris McGinlay -
Cog Rusty -
Metzler, David -
Peter Apokotos