Making WordPress.org

Opened 4 years ago

Closed 2 years ago

#1724 closed defect (fixed)

Readme parsing bugs

Reported by: dd32 Owned by:
Milestone: Plugin Directory v3.0 Priority: normal
Component: Plugin Directory Keywords:


  • URL's are marked up even when contained within a shortcode, for example in the woocommerce readme it's converted to this: <p>[youtube <a href="https://www.youtube.com/watch?v=1KahlicghaE%5D" rel="nofollow">https://www.youtube.com/watch?v=1KahlicghaE%5D</a></p>

Change History (20)

#1 @dd32
4 years ago

In 3180:

Plugin Directory: Split the Markdown specific items into their own class.

See #1724

#2 @dd32
4 years ago

In 3181:

Plugin Directory: Fix shortcodes containing links by not running make_clickable() on the content, this breaks standalone links, so needs to be fixed.

See #1724

#3 @dd32
4 years ago

In 3182:

Plugin Directory: Handle UTF-16 files.

See #1724

#4 @dd32
4 years ago

In 3213:

Plugin Directory: Imports: When importing a plugin for the first time, set the date correctly.

See #1724

#5 @dd32
3 years ago

In 3348:

Plugin Directory: Support markdown in plugin short descriptions.

See #1724

#6 @dd32
3 years ago

In 3349:

Plugin Directory: Only use the first line of the description for the short description of the plugin.

See #1724

#7 @dd32
3 years ago

In 3358:

Plugin Directory: When sanitizing the contributors in the readme, ensure that we match the case of the user login.

See #1724

#8 @dd32
3 years ago

In 3360:

Plugin Directory: Better parsing for the short_description. We don't want to allow extra HTML/markdown in the short_description.

See #1724

#9 @dd32
3 years ago

In 3473:

Plugin Directory: Avoid $current from the last section bleeding into $upgrade_notices.

See #1724

#10 @dd32
3 years ago

In 3553:

Plugin Directory: Cut down the length of the short_description after we've transformed and stripped any HTML and markdown.

See #1724

This ticket was mentioned in Slack in #meta by obenland. View the logs.

3 years ago

#13 @dd32
3 years ago

In 4194:

Plugin Directory: Readme Parsing: Use UTF8-aware line splitting to avoid matching newline charaters half way through a utf8 character byte.

See #1724.

#14 @dd32
3 years ago

In 4196:

Plugin Directory: Readme Parsing: Standardise on user_nicename rather than user_login for the Contributors header.
On WordPress.org we've got a lot of accounts for which the Login contains spaces, uppercase characters, email addresses, etc. Standardising on user_nicename simplifies the rest of the code.

See #1724

#15 @dd32
3 years ago

In 4197:

Plugin Directory: Switch Contributors from being stored as post meta to a taxonomy to allow for more efficient querying.

/author/$author/ / author_name queries are now based on this taxonomy rather than by the post_author.

See #1724, #1840.

#16 @dd32
3 years ago

In 4198:

Plugin Directory: Base the [developers] shortcode off of Contributors rather than Contributors+Committers.
This is required after r4197.

See #1724

#17 @dd32
3 years ago

In 4564:

Plugin Directory: Allow importing of plugins which lack a trunk readme.txt file but have tagged versions.
This is currently supported by the existing directory, and a number of older (and some recent) plugins rely upon this behaviour, since it's easy to support, we might as well continue to do so.

See #1724

#18 @dd32
3 years ago

In 4565:

Plugin Directory: When performing an initial import of a plugin, ensure that the post_modified date is not overridden by the current date.

See #1724.

#19 @Ipstenu
3 years ago

  • Keywords close added

I think we can close this and open up new ones as needed.

#20 @dd32
2 years ago

  • Keywords close removed
  • Milestone set to Plugin Directory v3.0
  • Resolution set to fixed
  • Status changed from new to closed

Please open new tickets for future issues.

Note: See TracTickets for help on using tickets.