Contact the CoursesWeb Forum moderators
You can reach the forum moderators by email at hello@coursesweb.net. The same address is used for the parent site, CoursesWeb, so put "Forum" at the start of your subject line. That helps the message reach Teodora Vance or Callum Iwu, the two staff moderators.
What to send us
The address is for matters that need a person. The most common ones are these.
- Removal requests. You want a post of yours, or a detail inside it, taken down. You do not have to give a reason.
- Bug reports. A page that does not load, a form that rejects a valid post, a code block that renders badly or a layout that breaks on your phone.
- Moderation reports. A post that is spam, abusive, advertising or exposes someone's private details.
- Corrections. An answer, including a staff answer, that is wrong or out of date.
- Questions about the forum itself. How an account works, how accepted answers work or what the forum stores. The privacy page has the details.
What to include
Paste the full web address of the thread or post you mean, and say what you would like to happen: a removal, a correction, a fix or an answer. For a bug, say which browser and device you use, what you did and what you saw instead. A screenshot with nothing private in it helps. For a factual correction, include the source that shows what is right, such as the MDN page, the PHP manual or the official release notes. That lets us fix the post instead of debating it.
What not to send us
Please do not put any of these in an email, in a forum post or in a screenshot:
- Passwords. Not for your site, your hosting, your database or your account here. We never need one.
- API keys, tokens and database logins. If you pasted one into a post by mistake, treat it as exposed. Change it with the service that issued it first, then email us the post address so we can remove it.
- Private code you may not share. Code from an employer or a client, or code under a licence that forbids sharing, should not be sent to us or posted. Reduce the problem to a small example you wrote yourself.
- Personal data about other people, such as customer lists or database exports.
If you send something sensitive by mistake, tell us so we can delete the message.
Reporting a post
Email the post address and the reason. Posts that expose personal information, harass someone, advertise a service or paste credentials are handled first. You do not need to explain at length.
Corrections to staff answers
Staff answers should be accurate. If one is wrong, uses a deprecated approach or leans on a weak source, tell us. When we correct a staff post we add a visible note in the thread saying what changed, rather than editing it silently.
Removing your content
Members who have an account can edit their own posts for 30 days after posting. For a removal you cannot do yourself, or a question about what the forum holds about you, email us. Because the forum keeps only a scrambled form of your email address, include the post address so we can find your content. Where a post identifies a private person, we remove the identifying details or the post.
Copyright and licence notices
Send copyright notices to the same address with the subject "Copyright notice". Include the address of the material, a description of the work, your contact details and a statement that you believe in good faith the use is not authorized. If someone has posted code that you wrote and that carries a licence, tell us the licence and what you want done.
Press and research
Journalists and researchers may quote public threads with a link back to the thread. If you want to contact a member, ask us and we will pass the message on. We do not share members' email addresses.
Accessibility
If a page is hard to use with a screen reader or a keyboard, tell us which page and what happened. We treat it as a bug.
Not a support desk for your project
We cannot debug your code by email. Post the question in the right section, where staff and members can see it, and follow the guidelines so that people can help quickly.