[wp-meta] [Making WordPress.org] #4311: Forums: Add notice not to report vulnerabilities
Making WordPress.org
noreply at wordpress.org
Thu Mar 21 20:52:14 UTC 2019
#4311: Forums: Add notice not to report vulnerabilities
----------------------------+---------------------
Reporter: Ipstenu | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone:
Component: Support Forums | Resolution:
Keywords: |
----------------------------+---------------------
Comment (by benlk):
The current text on forum submit pages is this:
When posting a new topic, follow these steps:
Read the Forum Welcome https://wordpress.org/support/welcome/ to find out
how to maximize your odds of getting help!
Search https://wordpress.org/support/search/ the forums to see if your
topic has been resolved already.
Update to the latest versions of your plugins, themes, and WordPress.
Note the exact steps needed to reproduce your issue.
Provide any information you might think is useful. If your issue is
visual, note your browser and operating system. If your issue is
technical, note your server environment.
Suggested revisions:
- Change the first step to: "Read the Forum Welcome
https://wordpress.org/support/welcome/ to find out how to maximize your
odds of getting help! If you're here to report a vulnerability, exploit,
or security issue with a plugin, please read how to do so safely
https://developer.wordpress.org/plugins/wordpress-org/plugin-security
/reporting-plugin-security-issues/. "
- Add information on reporting security vulnerabilities
https://developer.wordpress.org/plugins/wordpress-org/plugin-security
/reporting-plugin-security-issues/ to the Forum Welcome page
https://wordpress.org/support/welcome/
This ticket results from the discussion in Slack's #meta at
https://wordpress.slack.com/archives/C02QB8GMM/p1553200752319200
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/4311#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list