I've got a request for a clients members to be able to upload their own images either into the media area or so they are shown as nodes onto the content tree, probably as custom datatypes.
So this would involve individual members creating their own folders and images into a protected area on the content tree, but the tree only showing that members folder/images.
How would I go about doing this?
Also I know that media is not protected so I would have to protect the media also.
I haven't yet decided wether a person would login to umbraco as a user and upload pictures or make an protected area on the front end where a member would upload the pictures. They would still have to be created as nodes either in media or a custom type on the content tree as the admin would need to be able to delete them if required.
Any suggestions welcome on best way to go about this.
Personally I would look to use the Media section and build custom functionality around uploading images / managing folders / etc.
You could have a custom property on the member profile that records the Media node ID of the members parent folder. This would enable control over what they can see. Depending on how you manage the members you could have this parent folder auto created when the member record is created (member event).
In terms of protecting the media, I assume you mean that the files uploaded by the member should not be directly browseable by URL - e.g. http://www.mysite.com/media/1234/image.jpg. This aspect I cannot comment on.
So which method do you think would be best for the user of the site?
Do they login to umbraco as a user and use the media area. Or would it be best to register them as a member, which allows them into a protected area which then provides them to access a page to upload pictures and a page which displays their uploaded pictures?
As a site user I think i'd prefer they have a front end client area, and they don't get to go into the umbraco admin.
Yes, i've seen the media-protect, also looking at PublicMediaTree project to deny direct url viewing of the images.
Definitely a password protected area on the front of the site. That does mean more development work to achieve but is the best solution.
With Umbraco the word "member" infers someone that can log in to a password protected area on the front of the site, a "User" is someone who has adminstrator access and can log in to the admin area. Just thought I'd mention it...
Great comments by Nigel and as he already mentioned to prevent downloading you need mediaprotect (or code a solution yourself that prevents downloading). I'm the author of that package so if you have any questions about it please let me know.
Just skipping the media protect for now, @richard / @nigel thanks for the heads up on the protect package.
I've got a basic working model setup now as a starting point with member login, member register etc , I've got an upload working that writes nodes to the media area for the folder name and image, then a page with a bit of razor that loops thru that members folders and images only and displays them.
I've now got a request from the client for public browsers of the website to be able to add comments under the image, bit like a blog post comment, and who do not need to be member of the site to add a comment. So that's straight forward, a little form underneath the image to post comment info then...
What's the best way to go about this umbraco side, have a datatype for comments folder and comments to go in that folder. But where would I put those nodes, underneath the image datatype? or make a new datatype within media called 'GalleryImages' then have comment datatype under that?
Comments is content so ideally it should go into the content section. In that case you might want to rethink your current solution as well and store the uploaded images in the content section as well. A child mediatype with comments as you suggested will also work but I think since it's content it should go into the content section.
Members own media area
I've got a request for a clients members to be able to upload their own images either into the media area or so they are shown as nodes onto the content tree, probably as custom datatypes.
So this would involve individual members creating their own folders and images into a protected area on the content tree, but the tree only showing that members folder/images.
How would I go about doing this?
Also I know that media is not protected so I would have to protect the media also.
I haven't yet decided wether a person would login to umbraco as a user and upload pictures or make an protected area on the front end where a member would upload the pictures. They would still have to be created as nodes either in media or a custom type on the content tree as the admin would need to be able to delete them if required.
Any suggestions welcome on best way to go about this.
Pete
Hi Pete
Personally I would look to use the Media section and build custom functionality around uploading images / managing folders / etc.
You could have a custom property on the member profile that records the Media node ID of the members parent folder. This would enable control over what they can see. Depending on how you manage the members you could have this parent folder auto created when the member record is created (member event).
In terms of protecting the media, I assume you mean that the files uploaded by the member should not be directly browseable by URL - e.g. http://www.mysite.com/media/1234/image.jpg. This aspect I cannot comment on.
Hope the above helps in some way.
Nigel
Maybe this package is worth considering for the protection.
http://our.umbraco.org/projects/website-utilities/media-protect
Hi Nigel
Thanks for the reply.
So which method do you think would be best for the user of the site?
Do they login to umbraco as a user and use the media area. Or would it be best to register them as a member, which allows them into a protected area which then provides them to access a page to upload pictures and a page which displays their uploaded pictures?
As a site user I think i'd prefer they have a front end client area, and they don't get to go into the umbraco admin.
Yes, i've seen the media-protect, also looking at PublicMediaTree project to deny direct url viewing of the images.
Peter
Hi Peter
Definitely a password protected area on the front of the site. That does mean more development work to achieve but is the best solution.
With Umbraco the word "member" infers someone that can log in to a password protected area on the front of the site, a "User" is someone who has adminstrator access and can log in to the admin area. Just thought I'd mention it...
Cheers
Nigel
Hi,
Great comments by Nigel and as he already mentioned to prevent downloading you need mediaprotect (or code a solution yourself that prevents downloading). I'm the author of that package so if you have any questions about it please let me know.
Cheers,
Richard
Hi Nigel
Just skipping the media protect for now, @richard / @nigel thanks for the heads up on the protect package.
I've got a basic working model setup now as a starting point with member login, member register etc , I've got an upload working that writes nodes to the media area for the folder name and image, then a page with a bit of razor that loops thru that members folders and images only and displays them.
I've now got a request from the client for public browsers of the website to be able to add comments under the image, bit like a blog post comment, and who do not need to be member of the site to add a comment. So that's straight forward, a little form underneath the image to post comment info then...
What's the best way to go about this umbraco side, have a datatype for comments folder and comments to go in that folder. But where would I put those nodes, underneath the image datatype? or make a new datatype within media called 'GalleryImages' then have comment datatype under that?
Thanks
Peter
Hi Peter,
Comments is content so ideally it should go into the content section. In that case you might want to rethink your current solution as well and store the uploaded images in the content section as well. A child mediatype with comments as you suggested will also work but I think since it's content it should go into the content section.
Cheers,
Richard
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.