Textpattern CMS support forum
The forum uses Textile markup language for posts and signatures. The forum’s Textile has few additional features, including media embedding support and syntax highlighting. If you’re not already familiar with Markdown, take a quick look at Textile reference. The few most useful Textile tags you can use to format your posts include:
Displaying code blocks
You can use the Textile
bc. tag to add code snippets to your forum posts.
bc. <txp:permlink> <txp:title /> </txp:permlink>
The forum also supports syntax highlighting. Add an optional language identifier to your code block, and it will get highlighted.
bc. html <h1 id="main-heading">Hello World!</h1>
Supported language identifiers include: apollo, bash, c, coffee, cs, clj, css, dart, go, hs, html, java, js, json, lisp, lua, ml, n, perl, php, proto, python, ruby, rust, scala, sh, sql, tex, txp, vb, vhdl, wiki, xml, xsl, xq and yaml.
You can embed media to your posts from third party services to linking to the resource using normal Textile link syntax.
"$":http://www.youtube.com/watch?v=BKQ6nINAeq8 "$":https://twitter.com/textpattern/status/386111138699935744 "$":https://gist.github.com/gocom/5431041
A link to a supported service becomes an embedded object if it is in its own paragraph. Links within text will stay as normal text links to avoid disturbing reading and text flow. We currently support embedding content from YouTube, Twitter and GitHub Gist.
Why can’t I create a forum account or receive forum emails?
The most common cause of problems when creating forum accounts are email spam filters and blacklists. You must supply a working email address in order to create an account; when you sign-up, the forum software will send you the password you may use to login, to verify that your email address is correct and working properly. Some email servers refuse to accept these emails or incorrectly intercept them as spam. This is particularly common with free web mail services.
The following email providers seem to have problems accepting email from this forum, for one reason or another:
It is therefore recommended that you use an address from another provider.
How should I ask for help on the forum?
The Textpattern CMS Support Forum is for discussion and support of all things Textpattern. Please bear in mind that it is a community forum—when you ask for assistance, you are asking volunteers and fellow users, not paid technical support staff. The usual common-sense conventions of etiquette and politeness apply.
A few rules of thumb specific to the Textpattern forum:
- Please make an effort to check the Textpattern CMS User Documentation before posting, and check for duplicate threads on the forum.
- Try to choose the most appropriate forum for your question. ‘Troubleshooting’ is for when you’ve tried something and it doesn’t work as expected. ‘How do I…?’ is self explanatory. Questions about plugins should go to the ‘Plugins’ forum, not ‘How do I…?’ or ‘Troubleshooting’.
- If you’re asking for help with a problem or error, please describe the problem clearly and unambiguously. If there is an error message, please include an exact copy of the message in your post. If something doesn’t work as expected, describe what you’re expecting to see, and the actual behaviour. A link to the page in question is usually helpful, and sometimes a screenshot might be appropriate. Descriptions like “doesn’t work” or “it’s broken” are too vague, and unlikely to receive an answer.
- Most suspected bugs aren’t really bugs, but problems caused by external factors. Unless you’ve confirmed the problem with a fresh install, or can identify the problem in the PHP source, start with a ‘Troubleshooting’ post rather than a bug report.
- Troubleshooting questions will usually be answered quicker if you include a copy of your diagnostics in your post (Textpattern → Admin → Diagnostics). Don’t post the ‘High’ detail version unless someone asks.
- Questions about templates and appearance will usually benefit from including a minimal copy of the code in question. Edit out as much irrelevant code as you can—a short snippet of code is much easier for people to quickly diagnose than an entire page.
- If you haven’t received an answer in a day or so, there’s probably a good reason: an ambiguous or rambling question, or not enough information. Don’t ‘bump’ your thread with a single-word post, it’s more likely to annoy people than attract an answer—post some more information instead.
- Don’t post a troubleshooting question as a reply to an existing thread unless your problem is exactly the same as the one described at the beginning of the thread.
- If you’re requesting a feature, this article lists some of the things you can do to increase its chances.