Why not? This is counterintuitive. This nonassociation will inevitably, eventually, cause users to upload duplicates since they can't find it in the media browser.
Should I be using a different field for attaching images or download files to pages?
Not sure if this is what you mean, but if you go into the developer section of Umbraco and edit the Media Picker datatype, there should be an option in there to show a thumbnail preview. It's not activated by default, but if you check it then it should show a thumbnail of the image in your content editor. It doesn't work for files though, so I tend to create a new media picker data type specifically for images when using this feature.
You're right that an Upload field does not store the uploaded file in the media library. The rule of thumb is pretty much, if you want something to be re-usable, use the Media Picker. If it's a one-off file that relates only to a specific content node, you can use an Upload field.
Here are a couple related threads where you might get some more info:
Yes, this is what I suspected, I just didn't want to face it because it's so lame. I can't see any reason why there would even exist a field which would upload media unrelated to the media library, and even so, why would the syntax for writing it to the page be different? For Media Picker you have to use GetMedia() and for an Upload Field you can just use {image}. So this makes things such that now I can't change these fields without changing all my front-end code. Ugh! Well thanks for all your attention on this issue, guys.
Upload Field - Files Do Not Appear in Media
Why not? This is counterintuitive. This nonassociation will inevitably, eventually, cause users to upload duplicates since they can't find it in the media browser.
Should I be using a different field for attaching images or download files to pages?
Thanks,
Garrett
Hi Garret,
Not sure if this is what you mean, but if you go into the developer section of Umbraco and edit the Media Picker datatype, there should be an option in there to show a thumbnail preview. It's not activated by default, but if you check it then it should show a thumbnail of the image in your content editor. It doesn't work for files though, so I tend to create a new media picker data type specifically for images when using this feature.
Hope this helps...
Hi Garrett,
You're right that an Upload field does not store the uploaded file in the media library. The rule of thumb is pretty much, if you want something to be re-usable, use the Media Picker. If it's a one-off file that relates only to a specific content node, you can use an Upload field.
Here are a couple related threads where you might get some more info:
Hope this helps,
Tom
Ah, nice one Tom - I got completely the wrong end of the stick!
Tom--
Yes, this is what I suspected, I just didn't want to face it because it's so lame. I can't see any reason why there would even exist a field which would upload media unrelated to the media library, and even so, why would the syntax for writing it to the page be different? For Media Picker you have to use GetMedia() and for an Upload Field you can just use {image}. So this makes things such that now I can't change these fields without changing all my front-end code. Ugh! Well thanks for all your attention on this issue, guys.
//Garrett
is working on a reply...