Version: 3.5.2 Reporter: Ponder The Web —
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
This is an edge case, but if you create a file field and choose a file upload directory all is well. But if you then delete that directory from EE the publish/edit channel pages will throw a php notice that it’s trying to get property of non-object and points to a line in the file field plugin. And the file field just stops functioning at that point.
Seems like the fallback should be to revert to allow all directories or maybe show a message that you need to assign a directory to that field.
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); } ```