There are a couple of typos on the warning message displayed when previewing a followup to a bug report.

Please make sure you provide as much usefull information on your issue as possible. If it is a feature request, ask yourself: Would I want to spend the time neccessaray to implement it?

usefull -> useful
neccessaray -> necessary

Comments

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (fixed)

no longer relevant. someone completely re-worded the text and the current version has no typos.

Wolfey’s picture

Wolfey commented
Component: web site » Textual improvements
Status: Closed (fixed) » Active

(Apologies for bumping - and reopening - an old, closed issue, but...)

It seems the message has reverted to what jimt mentioned in his description - it also has the same two typos.

(Also, I had to change the component when submitting this comment - it's a required field and, since "web site" is no longer in that list, I selected what I felt was the most appropriate choice from what was available.)

Wolfey’s picture

Wolfey commented

That's odd...it doesn't seem to show up (or only shows up) for certain issues, and I have no idea why. I've noticed that one of three messages will be displayed when commenting on an issue:

  1. Nothing - there's no message at all before the comment.
  2. The message jimt described.
  3. A completely different message, which has no typos - is this the re-worded text?
    If you are reporting a bug, it needs to consist of three things:

    * What are the steps required to reproduce the bug?
    * What behavior were you expecting?
    * What happened instead?

Please include as much information as you can: OS, webserver name and version, PHP version, Drupal version, Drupal path, and everything else you might feel is relevant. There is no such thing as a bug report that is too detailed.

I should have posted that in my last message, but didn't notice it at the time - sorry about that.

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (fixed)

This is a per-project setting. Many projects customize this help text to be more relevant or appropriate for their needs. Clearly, some projects just cut and pasted the old, typo-ful message that core used to provide. In that case, create an issue in that project's issue queue as a minor task and ask them to fix it.

Cheers,
-Derek

Wolfey’s picture

Wolfey commented

So it's per-project then? That would explain why different messages were being used - thank you very much for clearing that up for me. I'll be sure to notify the owners of projects using this message so it can be taken care of.

My apologies for reopening this issue by mistake - I honestly thought this was an issue with Drupal.org, rather than individual projects.