[wp-meta] [Making WordPress.org] #2638: Linebreaks in FAQ section

Making WordPress.org noreply at wordpress.org
Thu Mar 30 03:33:26 UTC 2017


#2638: Linebreaks in FAQ section
------------------------------+------------------
 Reporter:  ccprog            |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:  has-patch         |
------------------------------+------------------

Comment (by dd32):

 I think I looked into something like [attachment:2638.diff], but
 unfortunately IIRC it had unintended consequences (which I can't recall
 now that it's been so long) - probably specifically about intentional new
 lines.

 Here's how that readme was parsed in the old directory:
 {{{
 <p>There is limited support for use in multisite environments. There is no
 option for a network
 wide installation; the plugin <strong>must</strong> be enabled for each
 individual site. Projects and
 their associated rights are also specific to the individual site, local
 administrators have
 access to these settings as usual.</p>
 }}}

 Here's the readme being parsed in the new directory:
 {{{
 <p>There is limited support for use in multisite environments. There is no
 option for a network
 wide installation; the plugin <strong>must</strong> be enabled for each
 individual site. Projects and
 their associated rights are also specific to the individual site, local
 administrators have
 access to these settings as usual.</p>
 }}}

 I'm assuming that the difference is that we now have WordPress display
 filters running over the content - probably `wpautop()` specifically.

 I think I'm okay with this, and am happy to intentionally break anyone who
 is reliant upon this specific markdown format of new lines. A bunch of
 plugins will need to update to match the new directory in many ways, I
 don't see this as being one of those ways as being a bad thing.
 If we leave it as-is, it'd probably be best to add a `nl2br()` call into
 the parser to solidify that we're intentionally doing this.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2638#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list