Answers.Body: <p>If you're looking for a setting you can apply to the plugin that corresponds to your custom field, it doesn't look like such a setting exists.</p>
  
  <p><strong>Update:</strong> I was just made aware of this <a href="https://github.com/lindseydiloreto/craft-cpjs/" rel="nofollow">Craft CP JS plugin</a> in another question. It looks like you could potentially hide your plugin from displaying. It's not as elegant as a first-party solution but it may be worth a shot</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T03:23:51.150Z
Answers.Text: Opinion: I could see it being useful to have a way to toggle which fields are available for quick edits (maybe only required fields?).
Answers.UserDisplayName: Tyler Willingham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T03:29:44.177Z
Answers.Text: I agree that this feature would be useful, but as in my case, I don't want it to be optional. I would love for a way for the plugin to the force this behavior anytime the Field Type is being used.
Answers.UserDisplayName: Peter Tell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T03:30:51.673Z
Answers.Text: Can you provide some context for when this doesn't make sense? Does the visual representation of your field not make sense within the confines of the modal?
Answers.UserDisplayName: Tyler Willingham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T03:39:05.857Z
Answers.Text: Pretty much. I have a plugin that opens up a modal for it's management and you'd start getting modals in modals, and it could cascade.
Answers.UserDisplayName: Peter Tell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T03:42:00.960Z
Answers.Text: Seems like a good use case for such a setting. I'm convinced :)
Answers.UserDisplayName: Tyler Willingham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T16:51:21.333Z
Answers.Text: I was just made aware of [this Craft CP JS plugin](https://github.com/lindseydiloreto/craft-cpjs/) plugin in another question. It looks like you could potentially hide your plugin from displaying. It's not as elegant as a first-party solution but it may be worth a shot.
Answers.UserDisplayName: Tyler Willingham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T18:01:05.780Z
Answers.Text: I was able to use this method to get this to work! It's definitely a bit hacky but it works. Do you want to break this comment out into an answer or edit this answer and I'll accept it?
Answers.UserDisplayName: Peter Tell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T18:04:08.733Z
Answers.Text: Great! I just updated my answer. Thank you
Answers.UserDisplayName: Tyler Willingham
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-12T03:22:35.567Z
Answers.LastActivityDate: 2014-07-12T18:45:57.787Z
Answers.LastEditDate: 2014-07-12T18:45:57.787Z
Answers.UserDisplayName: Tyler Willingham
Body: <p>Is it possible to hide a custom field from the modal that appears when you double-click on a related entry inside a Entries field?</p>
  
  <p>In other words, I don't want my custom field to be visible within the modal that comes from getEditorHtml.</p>
  
  <p>===== Updated based on accepted answer below =====</p>
  
  <p>Based on the accepted answer from @Tyler Willingham I used the following code in my plugin's main plugin file:</p>
  
  <pre><code>public function init()
  {
      parent::init();
      if (craft()-&gt;request-&gt;isCpRequest()) {
          craft()-&gt;templates-&gt;includeJsResource('myPlugin/js/myJs.js');
      }
  }
  </code></pre>
  
Tags: <plugin-development>
Title: Is it possible to hide a custom field type plugin from the popup tab when double clicking an entry?
ThreadText: # Is it possible to hide a custom field type plugin from the popup tab when double clicking an entry?
  
  (Asked by: username_0 on 2014-07-12)
  
  Is it possible to hide a custom field from the modal that appears when you double-click on a related entry inside a Entries field?
  
  In other words, I don't want my custom field to be visible within the modal that comes from getEditorHtml.
  
  ===== Updated based on accepted answer below =====
  
  Based on the accepted answer from @username_1 I used the following code in my plugin's main plugin file:
  
  ```
  public function init()
  {
      parent::init();
      if (craft()->request->isCpRequest()) {
          craft()->templates->includeJsResource('myPlugin/js/myJs.js');
      }
  }
  
  ```
  
  **Tags:** plugin-development
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-07-12. Score: 2 | Accepted answer
  
  If you're looking for a setting you can apply to the plugin that corresponds to your custom field, it doesn't look like such a setting exists.
  
  **Update:** I was just made aware of this [Craft CP JS plugin](https://github.com/lindseydiloreto/craft-cpjs/) in another question. It looks like you could potentially hide your plugin from displaying. It's not as elegant as a first-party solution but it may be worth a shot
  
  > **Comments:**
  > **username_1**: Opinion: I could see it being useful to have a way to toggle which fields are available for quick edits (maybe only required fields?).  
  > **username_0**: I agree that this feature would be useful, but as in my case, I don't want it to be optional. I would love for a way for the plugin to the force this behavior anytime the Field Type is being used.  
  > **username_1**: Can you provide some context for when this doesn't make sense? Does the visual representation of your field not make sense within the confines of the modal?  
  > **username_0**: Pretty much. I have a plugin that opens up a modal for it's management and you'd start getting modals in modals, and it could cascade.  
  > **username_1**: Seems like a good use case for such a setting. I'm convinced :)  
  > **username_1**: I was just made aware of [this Craft CP JS plugin](https://github.com/lindseydiloreto/craft-cpjs/) plugin in another question. It looks like you could potentially hide your plugin from displaying. It's not as elegant as a first-party solution but it may be worth a shot.  
  > **username_0**: I was able to use this method to get this to work! It's definitely a bit hacky but it works. Do you want to break this comment out into an answer or edit this answer and I'll accept it?  
  > **username_1**: Great! I just updated my answer. Thank you  
  
  ---
  
  