[wp-meta] [Making WordPress.org] #7065: Add additional notice to the Plugin Submission form
Making WordPress.org
noreply at wordpress.org
Wed Jun 14 20:11:47 UTC 2023
#7065: Add additional notice to the Plugin Submission form
-----------------------------+--------------------
Reporter: lukecarbis | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone:
Component: General | Keywords:
-----------------------------+--------------------
Currently the [https://wordpress.org/plugins/developers/add/ plugin
submission form] includes a notice that shows how many plugins are
awaiting review, and the current wait time.
Given that our wait times are currently very long, I propose adding a
secondary notice to this page, with text along these lines:
> We are currently experiencing long delays in plugin review times. To
help us approve your plugin sooner, please ensure that you have read the
[https://developer.wordpress.org/apis/security/ Security chapter] of the
Plugin Handbook.
>
> Our three most common reasons for not approving a plugin are:
> - The plugin contains unescaped output:
[https://developer.wordpress.org/apis/security/escaping/ Learn about
Escaping Data]
> - The plugin accepts unsanitized data:
[https://developer.wordpress.org/apis/security/sanitizing/ Learn about
Sanitising Data]
> - The plugin processes form data without a nonce:
[https://developer.wordpress.org/apis/security/nonces/ Learn about Nonces]
>
> If the code in your plugin falls into one of the above categories,
**your plugin will not be approved**. The plugin review team will refer
you back to these Handbook pages, adding further delay to the review
process.
It's my hope that this type of notice will reduce the amount of
submissions that require multiple reviews.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/7065>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list