[wp-meta] [Making WordPress.org] #5653: Plugin Directory: Track reasons for Rejection
Making WordPress.org
noreply at wordpress.org
Mon Jan 29 01:57:16 UTC 2024
#5653: Plugin Directory: Track reasons for Rejection
------------------------------+---------------------
Reporter: Ipstenu | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Plugin Directory | Resolution:
Keywords: has-patch |
------------------------------+---------------------
Comment (by dd32):
> Added all the replies to the private handbook as separated handbook
posts to be able to get the text from there. Created as classic, so hope
that getting the HTML from there might not be an issue.
Thanks! The rejection emails are currently plain-text, but I can upgrade
these to HTML as part of this to better communicate the email.
I think there was a bit lost-in-translation on the notion of a handbook
page here though - mostly because I wasn't very clear; I was thinking this
would be a public handbook page that expanded on a single paragraph in the
email.. ie.
{{{
Your plugin has been rejected due to {blah}, we feel that plugins of this
nature are not suitable for the directory, yadda yadda.
For more details on the reasoning behind this, please view
https:...../handbook/rejected-for/unsuitable
}}}
I don't think that's necessarily needed, but thought it might be a way to
keep the emails a bit more to the point.
But what that does mean is that I'm going to have to copy the contents
from the handbook and move it to PHP templates instead, as I don't think
we can realistically pull the contents from the handbook and email that to
plugin authors, and have future editors of the handbook to realise
whatever is on the page is going to go the author.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5653#comment:9>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list