Ticket #2881 (closed defect (bug): wontfix)
XHTML CDATA Buglet
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Template | Version: | |
| Severity: | normal | Keywords: | |
| Cc: |
Description
wp-includes/template-functions-post.php file line 57 -
$content = str_replace(']]>', ']]>', $content);
This line causes problem if any filters applied to content inject XHTML comments into your pages (for example script blocks...).
Symanticly this feature should not exisit in this context as it is itself a kind of filter, If desired, it should be re-implimented as a filter so the user can choose to disable the feature.
Change History
I concur! Now my blog is back to being 100% valid xhtml. he-he Thanks!
Using 1.5.3 beta 1 BTW...
Note: See
TracTickets for help on using
tickets.

I agree with reporter in that this should actually be a filter. Whether it should default to be included in the startup chain of filters... that's another matter.