<p>Sure, this should be possible from a plugin. But you could also suggest this as a new core feature on the <a href="http://feedback.buildwithcraft.com" rel="nofollow">Craft Feedback</a> page. I'd definitly vote for this! ;)</p>

CC BY-SA 3.0
2015-09-02T13:55:38.053Z
I thought it would be a plugin Job.

Thank you for your answer though and I will post that as a request for sure :)
Oli
CC BY-SA 3.0
2015-09-02T14:03:24.587Z
Don't forget to update your question with the link to the feature request, to receive some attention ;)
carlcs
CC BY-SA 3.0
2015-08-27T14:33:49.090Z
2015-08-27T14:33:49.090Z
carlcs
<p>So this is just a question to see if something is actually doable.</p>

<p>When you double click an asset, you get a little modal opening where you can see see custom field attached to said asset.</p>

<p>Would it be possible (plugin work I'm guessing) to open this model as a full publish form like entries have..?</p>

<p>Just wondering... :)</p>

CC BY-SA 3.0
2015-08-27T14:29:22.830Z
You mean from the assets tab, not from an entry's assets field, right?
carlcs
<assets>
Editing assets custom fields in a full page publish form
# Editing assets custom fields in a full page publish form

(Asked by: username_0 on 2015-08-27)

So this is just a question to see if something is actually doable.

When you double click an asset, you get a little modal opening where you can see see custom field attached to said asset.

Would it be possible (plugin work I'm guessing) to open this model as a full publish form like entries have..?

Just wondering... :)

**Tags:** assets
> **Comments:**
> **username_1**: You mean from the assets tab, not from an entry's assets field, right?  

---

## 1 answers

### Answer by username_1 on 2015-08-27. Score: 1 | Accepted answer

Sure, this should be possible from a plugin. But you could also suggest this as a new core feature on the [Craft Feedback](http://feedback.buildwithcraft.com) page. I'd definitly vote for this! ;)

> **Comments:**
> **username_0**: I thought it would be a plugin Job.  Thank you for your answer though and I will post that as a request for sure :)  
> **username_1**: Don't forget to update your question with the link to the feature request, to receive some attention ;)  

---

