Make WordPress Core

Opened 10 years ago

Closed 10 years ago

#6224 closed defect (bug) (invalid)

TinyMCE configuration removes DIVs unnecessarily

Reported by: offmessage Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.3.3
Component: TinyMCE Keywords:
Focuses: Cc:


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)

#3 @lloydbudd
10 years ago

  • 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.

#4 @offmessage
10 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.

#5 @Nazgul
10 years ago

  • 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.

Note: See TracTickets for help on using tickets.