Version: 2.2.2 Reporter: Greg Ferrell —
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
It seems that when you have more than one third party custom field, and those fields do $this->EE->table->add_row(), In the edit/create field screen, their custom field settings will persist even if you have chosen another field:
For example:
- I have two third party custom field types, ‘Dogfood’ and ‘FT_Test’.
- Both fields use the display_settings() function to output a field named ‘new_item_name’ with a default value.
- I go to add a new custom field for Dogfood.
- When i go to save, the default value for FT_Test gets saved into the settings instead of what i entered for dogfood because the added rows for FT_Test were just hidden instead of removed or moved outside the form element.
This might be a minor bug, but I can see it getting worse as more third party developers create field type add-ons with custom settings.
A solution might be to use jQuery to move the hidden data outside of the form until that type is selected so the data doesn’t get posted.
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); } ```