Last updated 7 June 2014. Created on 12 March 2012.
Edited by acabouet, Christopher James Francis Rodgers. Log in to edit this page.


The recommended way to most quickly get answers for module-specific or theme-specific questions at is within the 'Issues' pages for that specific project.

Note: Although Drupal 'modules' are distinct from 'themes', they are both classed at as 'project' (s).


Tech short-cuts:
- Modules
- Themes
- Project's home page:
- Project's issues page:

1.) Search project's issues: Enter your search terms into a project issue's landing page 'Search for' field-box, and click the button 'Search'.

2.) Ask: Click an project issue page's 'Create new issue' link; and for 'Category', if in doubt, specify 'Support request'.



Go to the 'Issues' page for the project; via the project's Home page if necessary.

On the issues page for your specific project, and search for your answer.

If that search does not help, you are welcomed and encouraged to post your question by clicking the 'Create new issue' link on any of that project's issues' pages.

On the 'create new issue' form, I recommend the 'Category' choice (required) drop-down menu item 'Support request'-- if in doubt.

In addition to any other person that might see your post and be able to help you, the module's developer(s) is(are) sure to see it. (Assuming the project is under active development)

I would caution you against ever posting a question on any Handbook-'Documentation' (per se) page since these pages are generally a static reference library and are Not frequented by a project's administrators.

The issue que for a project is the closest you can get to true live help of an unlimited nature.

Go to the issues page for your project in question, or if you do not know that location, you can find a link to the project's issues page on the project's 'Home' page.

Find the Project's Issues page via that project's 'Home' page.

To find the project's home page, start at either the 'Themes' or the 'Modules' main starting pages:

Modules -

Themes -

  1. Add search term keywords (the project name, for example) into the text field-box following 'Search Modules' (or 'Search Themes').
  2. 'Sort by:': "Relevancy" - I always change 'Sort by:' from "Most installed" to "Relevancy" when I know all or part of the project name and I have entered the project name (or part of that name) into the 'Search Modules' field-box (or 'Search Themes' field-box) above.
  3. Click the button 'Search', and hopefully the project you are looking for appears in the search results.
  4. Click on the title/'Project Name' and you will be taken to the project's home page.

At the project's Home page.

You will now be at...

...except that #specific_project_designated_url_name# will instead be the URL characters assigned to that project at


From a project's home page, click the right sidebar button 'Search'-- No search terms are required.

That will take you to the project's 'Issues' landing page.

At the Project's Issues Landing page

You will now be at...
...except that #specific_project_designated_url_name# will instead be the URL characters assigned to that project at


A Project's Issues Page is a Search results page.

A project's issues landing page is simply the first of a fifty-issue-per-page listing of every issue the project ever had.

To get to additional fifty-page issue listing pages (as applicable), you must use the links near the page bottom:

1 2 3 4 5 6 7 8 9 … next › last ».

A project's issues are sorted by column heading: default "Last updated": most recent first.

The default issues landing page starts with the column heading 'Last updated' selected and highlighted; and the order is by default newest-to-oldest. 'Last updated' refers to the issue's time of creation or, if applicable, to the time of its most recent comment's creation.

Click a different column heading to re-sort the list of all the project's issues (not just those issues already displayed) according to the topic specified by that column's heading name.

Column headings: 'Summary', 'Status', 'Priority', 'Category', 'Version', 'Component', 'Replies', 'Last updated', 'Assigned to', 'Created'.

The default sorting order for any column heading will be newest-to-oldest (or A-to-Z depending on its context). To reverse the sorting order to oldest-to-newest (or Z-to-A), click the active (highlighted) column heading. Clicking the highlighted column heading again will again reverse the list to what it had been originally by default for that column.

Project issues page-top search parameters

If you have reached an issue's landing page via that project's home page 'Search' button (and if you had left the search field-box blank before clicking the search button), then the text input field-box 'Search for' at the top of the issue page should be blank; And all of the search parameters should display "- Any -".

The other search parameters: 'Status', 'Priority', 'Category', 'Version', and 'Component' each have a drop-down menu that displays when you click in within its selection field-box (or if you click its down-pointing arrow).

Each of the drop-down menu choices for each parameter will serve to limit your next search to only those issues for which your parameter choice applies.

To cancel a menu choice you have previously selected for a parameter, and return that parameter to a non-filtered state, click that parameter's menu choice '- Any -'.

'Advanced Search' Page - Additional parameters; but No '- Any -'.

If you click the 'Advanced search' link (just to the right of the 'Create new issue' link) on any issues page, you will get the four additional search parameters: 'Assigned', 'Submitted by', 'Participant', and 'Issue tags'.

The most note-able thing I have found out about the Advanced search page is that although the page starts out with all parameters cleared, there are No '-Any-' menu choices for the parameters. And so if you select a parameter menu choice, you can Not clear that choice unless you click the 'Advanced search' link again.

Search the project's issues for your answer

Enter 'keyword(s)' into a project's 'Issues' page-top text-input field-box 'Search for', and click the button 'Search'.

Additional searches to exhaust Before you 'Create a new issue'

You were not expecting this, were you?

This step may not be as much fun as immediately posting a new issue, but this step might eliminate your need to create a new issue; or will undoubtedly enlighten you more and enable you to be more specific about your needs and desires if you do create a new issue.

  • Read the project's Home page where you will sometime find links to tutorials and documentation.

  • Google - WebWide search
    1. Go to
    2. In the text-input field-box, enter your 'keyword' or space-separated set of keywords.
    3. Click the button 'Google search'.
  • Google search limited to the website
    1. Go to
    2. Type "" - In the Google text-input field-box, enter "" (without the double-quotation characters; and note that there must be No-space between the semi-colon ":" and the 'd' of, and then add a blank space before any keywords.

      Add a blank-space and type your...

      - keyword
      - or space-separated keywords
      - or use double-quotation-marks around a "Keyword Phrase".

      (Note: Google searches are Not case-sensitive)

    4. Click the button 'Google search'.
  • Site-wide search: Enter you keywords into the search box at the right within the header at the top of any page; and click the button 'Search'.

If the above searches do not get you the information you want, then you can confidently 'Create a new issue' knowing that you have done all you can on your own.

Notably, your searches will likely have helped you to refine how you can word your issue so that you clearly and succinctly explain it.

"Create a new issue" for a specific project from one of that project's 'Issues' pages, and use 'Category': "Support request".

Starting from any issue page for the specific project you seek help with:

  1. Click the link "Create a new issue" located just above the search parameter field-box 'Search for'.
  2. On the new 'Create Issue' page for that module:
    1. 'Version:' - Select the module's version # that you are using.
    2. 'Component' - Select one of the four choices. I do not think your choice here is critical since the module's developers will see your issue regardless of your choice.
    3. 'Category' - Select 'Support request'. ..unless one of the other three choices seems more appropriate.
    4. 'Title' - The title is limited to 128 characters. To aid other people's future searches for the same issues that you have, please use as many keywords to your issue as you can within the title. The full title will display in all searches that return your issue page, so be as specific as you can so that future users can more easily decide whether your issue page is relevant to their needs.
    5. 'Description' - Detail your issue; and consider including an explanation as to why you are doing what are, as well as what specifically you have tried to do.



Tips for posting to the Drupal forums
including tips that are also helpful
for you posting anywhere at


Good luck and have fun.

"All the best; intended."

Looking for support? Visit the forums, or join #drupal-support in IRC.