WordPress.org

Make WordPress Core

Opened 5 years ago

Closed 5 years ago

#9744 closed feature request (wontfix)

wpautop - Enable/Disable option in options-writing.php or options-misc.php

Reported by: sc0ttkclark Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: Formatting Keywords: wpautop autop tinymce
Focuses: Cc:

Description

There really needs to be an option for WP Admins to turn off wpautop globally for the WP installation.

It would need to consist of two fixes if the option is unchecked:

  1. Remove filter for wpautop
  2. Disable tinymce autop (like TinyMCE Advanced plugin currently does)

Change History (8)

comment:1 Denis-de-Bernardy5 years ago

  • Milestone 2.8 deleted
  • Resolution set to wontfix
  • Status changed from new to closed

as you highlight in the bug description, this is plugin material.

comment:2 follow-up: sc0ttkclark5 years ago

  • Cc scott.clark@… added
  • Milestone set to 2.9
  • Resolution wontfix deleted
  • Status changed from closed to reopened

I disagree, these are formatting issues that shouldn't require the user to install a plugin.

There's *already* an option "WordPress should correct invalidly nested XHTML automatically". However, this is related to a different function.

An option to enable/disable the "autop" function should be included as an option, as it's attempting to auto-correct the HTML in a similar fashion as the option mentioned above. It *should* be optional, but can remain enabled by default.

comment:3 in reply to: ↑ 2 Denis-de-Bernardy5 years ago

Replying to sc0ttkclark:

I disagree, these are formatting issues that shouldn't require the user to install a plugin.

Well, you can re-open, and I don't disagree with you, but that won't change the fact that this ticket will remain open for years... until someone gets tired of seeing it and acknowledges the obvious -- i.e. it will not get fixed, and especially not if there is no patch.

There's *already* an option "WordPress should correct invalidly nested XHTML automatically". However, this is related to a different function.

There also happens to be a ticket that suggests this option should be dropped and that it should be on by default.

comment:4 sc0ttkclark5 years ago

I've been meaning to start contributing to the core for a while. I'll submit the patches required for this when I refresh myself how to create / submit patches.

comment:5 Denis-de-Bernardy5 years ago

To generate a patch using the command line:

svn co wordpress/trunk trunk

cd path/to/trunk

edit the files

svn diff > ticket.diff

see also #9724 for useful shell scripts

comment:6 sc0ttkclark5 years ago

Cool, thanks for help. I've been using TortoiseSVN, so I'll probably just update my trunk, add my fixes and generate the diff files from there.

comment:7 Denis-de-Bernardy5 years ago

  • Component changed from General to Formatting

Ok... But quite honestly, I wouldn't bother much with this ticket if I were you. I'd just acknowledge the state of things and close it.

There are so many years-old wpautop tickets around that it's bound to get ignored just like the other ones. And I'd be very surprised to see an ages old WP feature turn into something optional.

Moreover, there's a TinyMCE version of the wpautop (and of its reverse). This can potentially complicate your patch quite some bit.

comment:8 Denis-de-Bernardy5 years ago

  • Milestone 2.9 deleted
  • Resolution set to wontfix
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.