[wp-meta] [Making WordPress.org] #5513: Registered blocks list on plugins README displaying wrong labels.

Making WordPress.org noreply at wordpress.org
Wed Nov 18 01:27:58 UTC 2020


#5513: Registered blocks list on plugins README displaying wrong labels.
------------------------------+---------------------
 Reporter:  wetah             |       Owner:  (none)
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+---------------------

Comment (by dd32):

 Just noting that to remain GPL compliant either the source files need to
 be bundled, or it's obvious where to find the non-built versions.. I
 haven't looked at the plugin, but I'm just noting that here since it's
 common for JS plugins to not include the human readable source or make it
 obvious where to find it..

 Looking at the minified JS here, using regular expressions makes it very
 hard to match, as it's hard for PHP to know that the call to `f()` here is
 a `__()` and is within a `registerBlockType()` call: `var
 d=wp.blocks.registerBlockType,f=wp.i18n.__, ..... d("tainacan/carousel-
 collections-list",{title:f("Tainacan Collections Carousel","tainacan"),`

 We do have some JS-based parsing that should detect these blocks (Stored
 as `e2e_blocks` in the directory) which was intended on replacing this
 regex method, but that hasn't been done (yet?)

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


More information about the wp-meta mailing list