The following are the simple copy/paste replies to the most common requests.
Profanity:
What defines profanity is up to you. Just be reasonable.
[moronic expletive]
Large code excerpts:
Large is less of an issue now than it was before we fixed the forum code. Still, if it’s a whole template or stylesheet, remove it.
[Large code excerpt removed by moderator per <a href="http://codex.wordpress.org/Forum_Welcome#Posting_Code">forum rules</a>. Please use <a href="http://wordpress.pastebin.com/">the pastebin</a> for all large code excerpts. It works better anyway.]
Signatures:
You can just delete them or leave this if you want.
[Signature removed by moderator per <a href="http://codex.wordpress.org/Forum_Welcome#Signatures">forum rules</a>.]
Email addresses:
You don’t have to delete emails, but generally people will come back in 6 months asking you to delete the post and let’s just head ‘em off at the pass.
[Email deleted]
Bumps:
Generally we only have to do this when someone’s doing 10 bumps in a row.
[Per the <a href="http://codex.wordpress.org/Forum_Welcome">Forum welcome</a> we ask you NOT bump posts. We use the 'no replies' search on these forums regularly to find people who still need help. By bumping, you remove yourself from that list and make it HARDER for us to find you!]
Closing Posts:
If you have to close a post for any other reason, such as people getting way out of hand, you can use this.
[Per the <a href="http://codex.wordpress.org/Forum_Welcome#Closing_Posts">Forum welcome</a>, we reserve the right to close any post that are deemed to be non-productive support/WordPress discussions.]
Hosting provider recommendations:
Close the topic and leave the following (or similar) remark.
Per the <a href="http://codex.wordpress.org/Forum_Welcome#Closing_Posts">Forum welcome</a>, we close topics like this due to the amount of spam that they attract. The WordPress team has provided a list of <a href="http://wordpress.org/hosting/">a few recommended hosting providers</a>. For more details and other recommendations, please search through the forums or via Google (or your preferred search engine).
(Note: By closing this post I neither support nor condemn the use of the servers listed on the wordpress.org official hosting page, and encourage you to search around.)
Requests for post deletion or editing
Generally speaking, posts are only edited or removed where to do otherwise might lead to serious consequences. Previous examples have included posts that accidentally incorporated proprietary code or where the poster asking has reason to fear for their online safety. Having a posted site url come up in Google in NOT a serious consequence. In each case, use your best judgement or ask for a second opinion. If the final decision to to leave the post “as is”, use something like:
It is not the general policy to edit or delete forum posts. When a post is made and people contribute answers to an issue, that then becomes part of the community resource for others to benefit from. Deleting posts removes this added value. In extreme circumstances, the moderation team might be persuaded to remove sensitive information but. generally, your best course of action is not to publish anything that you wouldn't want to be public. I'm sorry but this is not an extreme case.
Offering to Pay
Close the topic and leave the following (or similar) remark.
Please try one of the following sites:
http://directory.codepoet.com/
This topic has now been closed as per the Forum Rules
Ipstenu (Mika Epstein) 2:08 am on August 14, 2012 Permalink |
When people complain that ‘wordpress is hosting a site.’
This normally comes with take down demands.
WordPress.org does not providing hosting for sites, it provides the software for other people to use their own sites on their own hosts. WordPress's <a href="http://wordpress.org/about/philosophy/">philosophy</a> and bill of rights permit people to use WordPress software for any reason they want, without any enforcement over legality or illegality. We leave that up to the webhosts. In cases of theft, abuse, harassment, or other such behavior, your best recourse is to contact their web host directly. You can use WHOIS to determine where they're hosted, as well as resources like http://www.whoishostingthis.com to find relevant information.esmi 12:05 pm on August 31, 2012 Permalink |
Requests for post deletion or editing
Generally speaking, posts are only edited or removed where to do otherwise might lead to serious consequences. Previous examples have included posts that accidentally incorporated proprietary code or where the poster asking has reason to fear for their online safety. Having a posted site url come up in Google in NOT a serious consequence. In each case, use your best judgement or ask for a second opinion. If the final decision to to leave the post “as is”, use something like:
It is not the general policy to edit or delete forum posts. When a post is made and people contribute answers to an issue, that then becomes part of the community resource for others to benefit from. Deleting posts removes this added value. In extreme circumstances, the moderation team might be persuaded to remove sensitive information but. generally, your best course of action is not to publish anything that you wouldn't want to be public. I'm sorry but this is not an extreme case.esmi 12:06 pm on August 31, 2012 Permalink |
Offering to Pay
Close the topic and leave the following (or similar) remark.
Please try http://jobs.wordpress.net/This topic has now been closed as per the <a href="http://codex.wordpress.org/Forum_Welcome#Offering_to_Pay">Forum Rules</a>
Ipstenu (Mika Epstein) 3:11 am on September 2, 2012 Permalink |
Hacked?
You need to start working your way through these resources:
http://codex.wordpress.org/FAQ_My_site_was_hacked
http://wordpress.org/support/topic/268083#post-1065779
http://smackdown.blogsblogsblogs.com/2008/06/24/how-to-completely-clean-your-hacked-wordpress-installation/
http://ottopress.com/2009/hacked-wordpress-backdoors/
Additional Resources:
http://sitecheck.sucuri.net/scanner/
http://www.unmaskparasites.com/
http://blog.sucuri.net/2012/03/wordpress-understanding-its-true-vulnerability.html