Version: 4.3.1 Reporter: H Media Webmaster —
[mod note- reported in v3 but moved to v4 for confirmation and fix.]
I am upgrading an EE2 site to EE3. In there process I am seeing PHP errors for an undefined index regrading custom member fields.
There errors only apply to custom member fields created in EE2.
Any new member fields created after the EE3 upgrade have 2 columns in the database instead of one.
m_field_id_1 m_field_ft_1
Should the EE 3 upgrade add columns to existing EE 2 member fields?
This stack exchange post explains further. https://expressionengine.stackexchange.com/questions/39367/undefined-index-in-custom-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: 
[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);
}
```