wpautop() formats the the contents of shortcodes

[Viper007Bond]

wpautop(), the bane of my existence as a plugin developer, is at it again.

Here's an example of some PHP wrapped in a valid shortcode in a post of mine:

[code lang="php"]$text = str_replace( array('<p><p>', '</p></p>'), array('<p>', '</p>'), $text);[/code]

The content that gets passed to my shortcode function is this:

$text = str_replace( array('
<p>', '</p>

</p>
<p>'), array('
<p>', '</p>
<p>'), $text);

Expected result: it shouldn't touch the insides of valid shortcodes (like adding line breaks or anything as it is doing now).

[Viper007Bond]

See also: #6969

[Denis-de-Bernardy]

In case this gives anyone some ideas:

​http://core.trac.wordpress.org/ticket/2833#comment:11

[Denis-de-Bernardy]

see also: #4298, #3833, #6041, #2833, #9437, #7988

[azaozz]

Extreme edge case. The shortcode args are passed to the callback that can contain these strings.

[mordauk]

I may get over ruled here, but I'm changing the priority of this from trivial to normal. As an avid plugin developer that spends 80% of every day working in support forums for plugins, this is a huge issue to me. It has cost me so many hours of support time due to themes modifying wpauto() and causing the contents of my plugin's short codes to break.

[collinsinternet]

What are your thoughts about changing the priority of when the do_shortcode filter is run from 11 to 9?

Line 407 of wp-includes/shortcodes.php:

add_filter('the_content', 'do_shortcode', 9); // BEFORE wpautop()

The other alternative would be to setup new filters for special shortcodes, but this could be a major pain.

The other alternative would be to create a

[Viper007Bond]

Replying to collinsinternet:

What are your thoughts about changing the priority of when the do_shortcode filter is run from 11 to 9?

This would likely break a ton of plugins. A better solution would be a priority parameter on add_shortcode().

It's pretty easy to run (but hacky) to run your shortcodes earlier today:

​http://www.viper007bond.com/2009/11/22/wordpress-code-earlier-shortcodes/

That's the solution I've been using in my plugins for years.

[collinsinternet]

Replying to Viper007Bond:

Replying to collinsinternet:

What are your thoughts about changing the priority of when the do_shortcode filter is run from 11 to 9?

This would likely break a ton of plugins. A better solution would be a priority parameter on add_shortcode().

It's pretty easy to run (but hacky) to run your shortcodes earlier today:

​http://www.viper007bond.com/2009/11/22/wordpress-code-earlier-shortcodes/

That's the solution I've been using in my plugins for years.

---

That's what I was afraid of.

[ericlewis]

Related: #12061

[miqrogroove]

We will be discussing this tomorrow in the #feature-shortcode channel. Related: #30531.

[miqrogroove]

#12061 was marked as a duplicate.

[miqrogroove]

#24085 was marked as a duplicate.

[miqrogroove]

I've closed several tickets as duplicates, directly and indirectly. We can use this one ticket to track roadmap ideas for fixing filter priorities and registration options. Currently, this is slated for 4.5 Milestone, and we will discuss it more at today's meeting in #feature-shortcode.

[usability.idealist]

Replying to miqrogroove:

I've closed several tickets as duplicates, directly and indirectly. We can use this one ticket to track roadmap ideas for fixing filter priorities and registration options. Currently, this is slated for 4.5 Milestone, and we will discuss it more at today's meeting in #feature-shortcode.

uhm .. whats the status of this, as 4.5 is definitely shipped, and 4.6 is making its final RC-rounds?

cu, w0lf.

[adamsilverstein]

#42003 was marked as a duplicate.