Answers.Body: <p>I'd probably re-think my approach.  Creating/extending a field type will give plugins access to the settings area below the horizontal rule in your screenshot, but that's on a per-field type basis and Craft doesn't provide a way to hook into where you're looking.</p>
  
  <p>What are <code>min_vis</code>, <code>def_vis</code>, and <code>max_vis</code> actually being used for?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-10T18:13:31.187Z
Answers.Text: These 3 columns would add a field visibility setting for each field. So when we can set the fields to have a minimum, default, and maximum. Their possible values are private (only viewable to owner), authed (logged in users), and public (everyone).
  
  Then we can show content based on the visibilities and allow for setting at a per entry basis as well using min and max as the bounds on content in that entry. Maybe a bit to heavy to try and expand craft in this nature.
Answers.UserDisplayName: Bill Columbia
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-10T18:04:01.887Z
Answers.LastActivityDate: 2015-11-10T18:04:01.887Z
Answers.UserDisplayName: Brad Bell
Body: <p>I'm trying to find a way to extend the meta fields inside a custom field definition. To illustrate:</p>
  
  <p>I need a <code>min_vis</code> <code>def_vis</code> and <code>max_vis</code> column for each field (or anytime a new one is added). Preferably these would be right under the <code>name</code>, <code>handle</code>, <code>instructions</code> text fields. So in this illustration below, there would be a select box added for each of these 3 new meta (or columns) after the instructions meta field.</p>
  
  <p><a href="https://i.sstatic.net/wNcOu.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/wNcOu.png" alt="where extra fields should appear"></a></p>
  
  <p>I know it probably isn't a good idea to modify the core stuff, including the fields table, so should I use a plugin to define some a new model and record? Should I extend the form for fields registration to add these additional attributes as select boxes? Should I give the new attributes their own table (via record class) and set <code>BELONGS_TO</code> where they are related to each field?</p>
  
  <p><a href="https://i.sstatic.net/4yrLX.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/4yrLX.png" alt="column list"></a></p>
  
  <p>If there is a better way to approach this, or if I'm pushing to hard for something custom no worries just give me a heads up that I shouldn't be extending the core fields attributes.</p>
  
  <p><a href="https://craftcms.stackexchange.com/questions/10191/how-can-i-add-attributes-to-craft-field">I did look at this issue but wasn't sure if it actually pertained to my question?</a></p>
  
Tags: <plugin-development><field><attribute>
Title: Add or extend attributes (table column) to fields table
ThreadText: # Add or extend attributes (table column) to fields table
  
  (Asked by: username_0 on 2015-11-10)
  
  I'm trying to find a way to extend the meta fields inside a custom field definition. To illustrate:
  
  I need a `min_vis` `def_vis` and `max_vis` column for each field (or anytime a new one is added). Preferably these would be right under the `name`, `handle`, `instructions` text fields. So in this illustration below, there would be a select box added for each of these 3 new meta (or columns) after the instructions meta field.
  
  [![where extra fields should appear](https://i.sstatic.net/wNcOu.png)](https://i.sstatic.net/wNcOu.png)
  
  I know it probably isn't a good idea to modify the core stuff, including the fields table, so should I use a plugin to define some a new model and record? Should I extend the form for fields registration to add these additional attributes as select boxes? Should I give the new attributes their own table (via record class) and set `BELONGS_TO` where they are related to each field?
  
  [![column list](https://i.sstatic.net/4yrLX.png)](https://i.sstatic.net/4yrLX.png)
  
  If there is a better way to approach this, or if I'm pushing to hard for something custom no worries just give me a heads up that I shouldn't be extending the core fields attributes.
  
  [I did look at this issue but wasn't sure if it actually pertained to my question?](https://craftcms.stackexchange.com/questions/10191/how-can-i-add-attributes-to-craft-field)
  
  **Tags:** plugin-development, field, attribute
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-11-10. Score: 0 | Accepted answer
  
  I'd probably re-think my approach. Creating/extending a field type will give plugins access to the settings area below the horizontal rule in your screenshot, but that's on a per-field type basis and Craft doesn't provide a way to hook into where you're looking.
  
  What are `min_vis`, `def_vis`, and `max_vis` actually being used for?
  
  > **Comments:**
  > **username_0**: These 3 columns would add a field visibility setting for each field. So when we can set the fields to have a minimum, default, and maximum. Their possible values are private (only viewable to owner), authed (logged in users), and public (everyone).  Then we can show content based on the visibilities and allow for setting at a per entry basis as well using min and max as the bounds on content in that entry. Maybe a bit to heavy to try and expand craft in this nature.  
  
  ---
  
  