Opened 5 years ago
Closed 5 years ago
#6224 closed defect (bug) (invalid)
TinyMCE configuration removes DIVs unnecessarily
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | TinyMCE | Version: | 2.3.3 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
source:branches/2.3/wp-includes/js/tinymce/tiny_mce_config.php@5700#25 forces TinyMCE to try and replace <DIV>s with <P>s. This seems completely unnecessary and breaks any use of microformats in blog posts. Even more annoyingly it is different for blogs hosted on wordpress.com, where this configuration is not present.
@@ -23,5 +23,5 @@
// Set up init variables
- $valid_elements = 'p/-div[*],-strong/-b[*],-em/-i[*],-font[*],-ul[*],-ol[*],-li[*],*[*]';
+ $valid_elements = '-div[*],-strong/-b[*],-em/-i[*],-font[*],-ul[*],-ol[*],-li[*],*[*]';
$valid_elements = apply_filters('mce_valid_elements', $valid_elements);
Change History (5)
comment:1
offmessage — 5 years ago
comment:2
offmessage — 5 years ago
I think possibly i should give up at this point!
http://trac.wordpress.org/browser/branches/2.3/wp-includes/js/tinymce/tiny_mce_config.php#L25
- Resolution set to invalid
- Status changed from new to closed
Closing as invalid for now. Please test trunk (2.5), I believe this issue is resolved there.
comment:4
offmessage — 5 years ago
- Resolution invalid deleted
- Status changed from closed to reopened
I see that it's fixed in trunk, but would hope that the fix would be back ported to the 2.3.x branches? It's a bug there too, and lots of people aren't going to update to 2.5 straight away.
- Resolution set to invalid
- Status changed from reopened to closed
Backporting this to the 2.3.x branch would mean an upgrade to TinyMCE3, which is far too invasive for a maintenance update and will therefore not make it into any possible 2.3.x maintenance releases.
Reclosing as invalid because of that.

Damn - I meant source:branches/2.3/wp-includes/js/tinymce/tiny_mce_config.php@5700#25