Asking for help¶
Guidelines and Examples¶
If you need help with an error or problem: before asking the question, please take a few minutes to read the guidelines below. It is important to know how to state questions, because once you learn it, you will get better answers back more quickly.
Asking help on support and discussion forums¶
By stating a well-phrased question you increase the likelihood of fast and helpful responses to your question.
Here are some general key rules users need to follow in creating a new topic.
ALWAYS start with searching before you ask a question. Most of your questions were probably already answered by someone else in the past. Save your and our time by searching the web first.
Where to search:
Google - Before asking for help, make a Google search with related keywords. Pick meaningful keywords from the log entry. Sometimes searching for the entire error message works!
Plone Community Forums - help and discussion forums
StackOverflow - some FAQs are maintained here
Troubleshooting tips and common error messages - for enabling debug mode and common tracebacks
GitHub issue tracker - for known related issues
Documentation issue tracker - for documentation related issues
If at any point you see any kind of error message (including error codes) – put them in your question. Never write anything like “I see some error message”. Be specific.
See Basic troubleshooting in case of an error
Follow netiquette while visiting and writing on forum or mailing list (give respect = get respect). This includes:
Be patient – sometimes the problem cannot be solved within minutes or hours. You might need to bump the topic few times until an experienced person comes to the site and sees it, but usually if you do not see any response after a day or two it probably means we do not know the answer to your question, or perhaps your question needs to include more detail.
Do not use bad words. Respect others and what they are doing.
Do not completely edit/erase your posts after you posted them on the forum (except for small corrections - they are allowed) Remember that once you sent them, they belong to the community and shall be used by anyone who needs it.
How to write a good topic¶
Keep in mind, that if you ask a question and all you hear is silence, it might be a good indicator that something is wrong with your topic. Read the hints below and try to match your topic with specified pattern.
Subject lines: most people will read a message only if it appears to be intelligent. Your subject line is your sales pitch, so you should make your subject line specific and easy to understand.
A poor subject line:
GET METHOD!! URGENT HELP!!!!
A better subject line:
FooError in Passing GET variables to FormController
The big picture - An opening sentence should state the general problem that you wish to solve.
A snapshot of your environment - For Plone and for other relevant products: provide version numbers. e.g., “I’m running Plone 5.0.4 under Python 2.7.11.”
Steps to reproduce the issue - Give information about your ideas of how this error appeared, what caused it or anything that could lead to reproducing the error on another computer, including your buildout.cfg, versions.cfg, version numbers of installed add-ons, detailed command lines, the complete error message stack. Mention your expected result.
Asking for help in online chat¶
(To use Gitter you must log in using a free GitHub or Twitter account, which allows you to receive notifications when there is a response to your question. IRC does not require you to log in, but you will receive notifications of responses only while you remain connected).
Here are useful hints for using online chat:
Remember that chat participants are volunteers; they are not paid to provide support.
Do not ask permission to ask a question, but directly start the conversation having the all necessary input. Follow the example below:
Be specific - tell us why you are trying to accomplish something and then tell us what the problem is. Here are some guidelines on how to form a good question for Internet discussion.
Do not copy-paste text to chat. This disrupts other people chatting about other topics. Instead please paste the full traceback error log to pastie.org and then paste the link to your error log or code (from your browser’s address bar) to the chat.
Do not send direct messages to chat participants unless you have a clear reason to do so
Keep the chat window open at least 30 minutes so that someone has time to pick up your question. Be patient.
Do not repeat yourself - people might be busy or not able to help with your problem. Silence doesn’t mean we’re ignoring you, it means that nobody is online right now who knows the answer to your question.
Do not overuse CAPS-LOCK writing, since it is considered shouting and nobody likes when others shout at them. Do not use excessive exclamation marks (!!!) or question marks (???) as it makes you look unprofessional and discourages others to help you.
There are many people discussing simultaneously - if you address a message to a particular person, use his or her nick name. Hint: you can use Tab key to autocomplete nick name after typing few letters.
Chat is a real-time communication tool. Keep in mind, that since you write something, and send it, it cannot be taken back.
Try to respond to all questions other users have. Chat is much more fluid and dynamic than the forum, so don’t worry if you forget about putting something in the first message – you can still keep up.
Do not worry if you are not fluent in English - Plone is a global community, and people will usually try to ask you more detailed questions in a way that the message gets through.
An ineffective chat question:
“Anyone here using product XYZ? Anyone here have problems installing XYZ?”
A question that is more likely to gain attention and a positive response:
“Hi, I’m using product XYZ on Plone 5.x.x, I have a problem with the feature that is supposed to doABC— I get error BlahBlahError — what might be wrong? Here is a link to the error log on pastie.org:http://pastie.org/123123”
When there is an error, a Python program always produces a traceback, a complete information where the application was when the error happened. To help you with an error, a complete traceback log is needed, not just the last line which says something like “AttributeError”.
Copy full tracebacks to your message (discussion forums) or pastie.org link (chat). The most reliable way to get the traceback output is to start Plone (Zope application server) in foreground mode in your terminal / command line (see these debugging tips)
First, shut down Plone if it’s running as a service / background process. Then start Plone in foreground mode.
On Linux, OSX or similar systems this is (navigate to Plone folder first):
On Windows command prompt this is
cd "C:\Program Files\Plone" bin\buildout.exe fg
Zope outputs all debug information to the console where it was started in foreground mode. When the error happens, the full traceback is printed to the console as well.
If Zope does not start in foreground mode it means that your add-on configuration is bad and you need to fix it and the related traceback is printed as well. In production mode, Zope ignores all add-ons which fail to load.
This how-to originated as an informal, user-friendly alternative to Eric Raymond’s How to Ask Questions the Smart Way. ESR’s doc is long and offensive, though once you realize that ESR is your crusty old merchant-marine uncle it can be fun and helpful.
The error report format is adapted from Joel Spolsky’s comments on bug tracking, e.g., in Joel on Software.