Changeset 41071 for branches/4.8/src/wp-includes/widgets/class-wp-widget-text.php

Timestamp:

07/18/2017 04:20:17 AM (8 years ago)

Author:

westonruter

Message:

Widgets: Discount shortcodes and leading/trailing line breaks for triggering Text widget legacy mode.

Since shortcode handling is just-in-time deferred to run after wpautop, there is no need to retain the presence of shortcodes to trigger legacy mode. Also updates Text widget legacy mode notice informing of Custom HTML widget.

Merges [41070] onto 4.8 branch.
Amends [41050].
Props westonruter, melchoyce.
Fixes #40951 for 4.8.1.

Location:

branches/4.8

Files:

• . (modified) (1 prop)
• src/wp-includes/widgets/class-wp-widget-text.php (modified) (3 diffs)

branches/4.8/src/wp-includes/widgets/class-wp-widget-text.php

@@ -96 +96 @@
 
         $wpautop = ! empty( $instance['filter'] );
-        $has_line_breaks = ( false !== strpos( $instance['text'], "\n" ) );
+        $has_line_breaks = ( false !== strpos( trim( $instance['text'] ), "\n" ) );
 
         // If auto-paragraphs are not enabled and there are line breaks, then ensure legacy mode.
@@ -105 +105 @@
         // If an HTML comment is present, assume legacy mode.
         if ( false !== strpos( $instance['text'], '<!--' ) ) {
-            return true;
-        }
-
-        /*
-         * If a shortcode is present (with support added by a plugin), assume legacy mode
-         * since shortcodes would apply at the widget_text filter and thus be applied
-         * before wpautop runs at the widget_text_content filter.
-         */
-        if ( preg_match( '/' . get_shortcode_regex() . '/', $instance['text'] ) ) {
             return true;
         }
@@ -349 +340 @@
             </p>
             <div class="notice inline notice-info notice-alt">
-                <p><?php _e( 'This widget contains code that may work better in the new &#8220;Custom HTML&#8221; widget. How about trying that widget instead?' ); ?></p>
+                <p><?php _e( 'This widget may contain code that may work better in the new &#8220;Custom HTML&#8221; widget. How about trying that widget instead?' ); ?></p>
             </div>
             <p>