Version: EE 2.0.0b02 20091023 Reporter: Brandon Jones —
This is an archived bug report. If you are experiencing a similar issue, upgrade to the latest release and if that does not solve the problem, submit a new bug report
A few suggestions for this page - see discussion at http://ellislab.com/forums/viewthread/133349/
1. Coming from the CI side of things, it would be nice if it were explicitly stated that a module can load models (and libraries, language files, etc) the same as a CI app.
2. It is not clear in the docs (or CP, really) that Module Access Permissions in the CP only refer to the *CP side* of the module, and that the module will only show up here if it has CP functions. This led to some confusion. This could be stated right under #3…
3. In the section titled “The Control Panel file”, it would be helpful to show what is required even if the module has no CP functions. This actually exists in another page (under “If your module does not have a control panel, you still need an mcp file in the format:†in docs/development/conversion/modules.html). I suggest it be added to the Module Tutorial page for clarity. I would not think to look at the Module Conversion page since I am creating a new module with the tutorial.
ExpressionEngine implements Markdown Extra and BBCode. Please see the Markdown Extra docs and the BBCode Wikipedia article for a full reference.
**bold**, __bold__, *italics*, _italics_, ~strike/del~, `code()`
bold, italics, strike/del, code()
Link: [link title](https://example.com)
Image: 
[blockquote]...[/blockquote], [quote]...[/quote], and Markdown style:
> Some quoted text. > > This is all one quote.
[code]...[/code], and you can also specify the language for syntax highlighting, [code=php]...[/code]
GitHub flavored Markdown code fences are also supported:
```
public function decoderRing($str)
{
return str_rot13($str);
}
```