Version: 2.11.7 Reporter: Brian Litzinger —
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
In preparing for a PHP 7 upgrade I stumbled upon this bug in 2.11 and fixed it. https://expressionengine.com/support/bugs/22897/A-non-numeric-value-encountered-ee-legacy-core-Loader.php-line-731
A couple days later when attempting to edit a custom field, I was getting this error: Unable to load the requested file: col_settings_tmpl.php
While debugging I realized it was an issue with the fix in bug 22897. Changing it from a + to . did correct the PHP 7 error, but it quietly introduced a new one. The issue seems to be that current() is getting the array’s value, which is true or false, and comparing it to the view file path, thus it was always true. I believe it should be using the array key, which is a view file path, to compare it to another view file path. Note this issue occurs in PHP 5.6 and PHP 7.
Change
current($this->_ci_view_paths) == $removed . 'views/')to
current(array_keys($this->_ci_view_paths)) == $removed . 'views/')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);
}
```