Before you open a new or add to an existing issue, please follow these guidelines:

    1. Provide an export of your Panel, and View if applicable, that can reproduce your problem. If at all possible, do so without requiring any contrib or even custom created fields. This vastly increases the chance that your issue will receive attention, as it immediately provides a baseline for the developers to work from. Otherwise they need to set up a new Drupal environment, and figure out how to emulate your precise settings as well.
    2. Search for duplicate issues.
    3. Do not hijack issues. It's confusing to everyone involved in the original issue, to other people who might have the same issue as you, and it's rude.
    4. Support requests should be very specific, narrow scope items. Broad or vague support requests or general pleas for help are best left to the forums, where you will get more eyes.
  1. When opening a new issue, failure to completely fill out all fields may result in the immediate closure of your issue due to lack of information.

    Reasons your issue may be summarily closed:

    1. Failure to follow paragraph 1.1 without any explanation.
    2. Your issue has been left marked "Postponed, maintainer needs more info" for more than 30 days.
    3. You have failed to provide enough information to begin to even guess what the problem may be. The Panels queue is hugely active, and there are not enough individuals helping to maintain it at a sustainable level. Issues that can be summarized as "it's broken. Fix it." will be closed with a pointer to this page.
    4. You are combative or argumentative in the queue, or bump your issue (make comments that are intended to raise your issue back to the top without adding further details).
    5. You are using Panels 1 (or Panels 6.x-2.x) and are requesting help for anything other than an upgrade problem.

How you can help:

Provide details. Pay it forward (if you've asked a few questions and gotten help, take one of the hours you saved and help close out a few other issues. Every bit counts.) Write a tutorial and submit it as a patch/issue to be integrated into Advanced Help.

Please read the following information for help in providing the most data in order to solve your issue quickly.

    • Version: The exact version of Panels being used.
    • Component: Which piece of Panels is the center of the issue.
      • Code: Issues working directly with Panels code.
      • API: Questions regarding the Panels API.
      • Documentation: Questions or updates for Panels documentation.
      • Miscellaneous: Items that do not fit into any other component category.
      • User Interface: Questions or problems in the UI.
      • Plugins (Content types, arguments, contexts, relationships, styles, layouts): Each plugin type has its own component, please use the appropriate one.
      • Display rendering: Issues with the actual display once it is complete and out on a page.
      • Drag and Drop display editing: Issues specifically with moving panes around within the Panels user interface.
      • Mini panels: Problems related to using Mini panels only.
      • Panel pages: Issues dealing with Panels that are handling an entire page.
      • Panel nodes: Issues dealing with overriding one or more specific nodes with Panels.
      • Views Panes: Issues with inserting Views into panes.
      • Attn -- s or Attn -- m: Do not use unless merlinofchaos or sdboyer asks you do to do.
    • Priority: Critical is reserved for bugs with complete application crashes where Panels simply does not work at all. All other issues are normal or minor.
    • Title: A short and descriptive sentence regarding the problem. "error message during creation" is not specific. ""Selection Rules" setting lost during new node_view variant set-up." is specific.
    • Description: This is the most critical. Be as descriptive as possible.
      • If your issue is about a Panel node, make sure it is categorized correctly. Describe what exactly you are attempting to do with the node.
      • Questions you should be able to answer:
        1. How often does this happen?
        2. What is the exact, complete error message? Copy and paste it into the issue.
        3. List every step you took to create the problem. Each click, each menu item. Reproducibility is the key to solving issues.
        4. Other modules that may be interacting.
        5. Completely describe exactly what you are attempting to accomplish. If your issue is only one or two sentences long, you have almost certainly not described the problem in enough detail.
      • Describe what part of the user interface you are using. The layout designer in the flexible layout is different than adding content to a flexible layout.