[wp-trac] [WordPress Trac] #50683: Parse content for shortcodes instead of using regex
WordPress Trac
noreply at wordpress.org
Thu Jul 16 21:15:33 UTC 2020
#50683: Parse content for shortcodes instead of using regex
--------------------------------------+---------------------
Reporter: cfinke | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: 5.6
Component: Shortcodes | Version:
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests | Focuses:
--------------------------------------+---------------------
Changes (by johnbillion):
* version: trunk =>
* milestone: Future Release => 5.6
Comment:
Thanks for working on this @cfinke.
Are you able to provide some performance comparisons of the current
implementation versus your parser please? That way we can assess whether
there is any change in performance when parsing shortcodes from post
content.
For example it would be great to see before-and-after figures for how long
it takes to process:
* A long post containing just one shortcode
* A long post containing many shortcodes
* A short post consisting of mainly nested shortcodes
* etc
--
Ticket URL: <https://core.trac.wordpress.org/ticket/50683#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list