Version: 3.5.6 Reporter: bigbytes —
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
The issue described here: https://expressionengine.com/support/bugs/21831/missing-language-files-of-third-party-addons seems still not to be fixed.
I can confirm this. Switched to “german” for a test user which works fine until a plugin without a german language file is loaded (which is most of them…) - then EE throws an error instead of using the default english language file.
I’m on 3.5.6 … this still seems not to be fixed. Why?
Interstingly this is NOT the case for every plugin/view, since i can access Channel Images for example and SOME tags / titles are actually in english (CI just having the standard english language folder) and some tags/titles are KEYS … and aren’t replaced by the english string…
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);
}
```