Version: 2.10.3 Reporter: Stephen Lewis —
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
If a “File” field type references an image whose filename contains non-alphanumeric characters, a “File not found” error message is displayed next to the field.
I believe this bug is caused by the “fix” implemented for bug 21013 (1), which itself addressed a bug introduced in version 2.10.0.
The file in question is present on the server, and has the same permissions as “non-problem” files. It also appears correctly in the File Manager, suggesting this is an issue with the File field type and / or the Channel publish page.
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: ![alt text](https://example.com/image.jpg)
[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); } ```