Hi Jim,

Thanks for your feedback.

You are right, the upload image editor does not prevent users with "read-only" access from changing the images (either by uploading or removing).

I must admit I hadn't noticed this, and I'm not sure if there is an easy/clean way to prevent this from happening inside the editor.

I will look into this asap.

Another (and probably easier) solution would be to hide the public folder in the media section (having it available through media pickers only).

Would that work for you?

Grtz

L

Hey Lennart,

Thanks for the great plug-in! (except for the mentioned issue). I'm not exactly clear what you mean. If it allows users to select and use media that is available across all users but not update/add/delete and have a "private" media folder that they can modify, then it sounds like it may accomplish our goal. Another option is to hide the upload tab in the public folder and hide the check box to remove file. This would be more preferable but may be much more difficult. I believe that there is a demand for such a set-up but perhaps I'm the only one demanding it. :-)

Any updates you would make to accomplish these thing would be greatly appreciated.

Jim

Hi Jim,

My apologies for the delay.

What I would like to do is hide the public folder in the Media section for non-admin users.

This should not be a problem as these users are not to modify the contents of this folder anyway.

Users with read-only access will then only be able to pick content from the public folder in the Content tree (either through built-in or custom media pickers).

I will update the package somewhere this week, keep you posted

Grtz

L

Will they still be able to update their own media folder? We are trying to allow users, when they go to the media library to be able to add media (like their own logo, picture of their particular store, etc.) to a folder that only they have access to AND have a public folder that only admin users can modify to put media in for all users to use (brand logos, etc.) The way it works now would be perfect if when non-admin user go to the public folder it would just hide the upload tab and hide the remove checkbox.

My concern is that if you hide the public folder the user will not even know it is avaiable to choose from. Perhaps I am not fully grasping how your soluton works. Thanks you for you time and effort. I appreciate your thoughts and help.

Jim 

Hello Lennart,

Just checking in to see if you have made any progress. I appreciate the effort and I'm not trying to be pushy. I am just being asked "When can we expect updates?" so I thought I would just check in to see how it was going. Is there anything you need me to do? I look forward to testing you changes when they are completed.

Jim Manson

Umbraco Newbie

Hi Jim,

I have not come up with a solution just yet.

In a first attempt I wanted to prevent the media from being saved (or updated) for which I used the Media.BeforeSave event but it seems I cannot prevent the properties from being saved (http://www.aaron-powell.com//the-great-umbraco-api-misconception). There may be a workaround to this but that seems a bit dirty.

Pretty occupied this week but I'll try to keep you posted on my progress (in case you're wondering I'm pretty sure we'll find a solution ;-))

Grtz

L

Hi Jim,

I have uploaded a new version of the package (1.2.0.0) which includes a fix. 

The save button of the node in the media section is now hidden for users that have read-only access.

Jeroen pointed me to his code snippet which did the trick: http://our.umbraco.org/forum/using/ui-questions/5493-Undelete-in-media-section-?p=2

You can either uninstall and reinstall the package, or simply extract and overwrite the DLL file in the bin folder (TheseDays.Umbraco.Media.PublicMediaTree.dll).

Let me know if that works for you.

Grtz

L

Hi Lennart,

Thank you for the new version.  I downloaded it, and installed it, and  It fixed the issue discussed above.  I found a bug in the new version.  I get the error message below when I:

1.  Login as an editor

2. Go to the Media section

3. Click on [Create] button above the content tree. This opens "Create Media."

4. Click on any node under "Public" folder and click "OK" button

Though this bug does not prevent user from performing any functions intended, I thought you might be interested in looking into this.

Thank you.

Takki

Server Error in '/' Application.

No Document exists with Version '2b2d27fa-cfb4-4d5d-b4c0-6be4b90f3a7f'

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentException: No Document exists with Version '2b2d27fa-cfb4-4d5d-b4c0-6be4b90f3a7f'

Source Error:

Stack Trace:

[ArgumentException: No Document exists with Version '2b2d27fa-cfb4-4d5d-b4c0-6be4b90f3a7f']
   umbraco.cms.businesslogic.web.Document.setupNode() +1067
   umbraco.cms.businesslogic.CMSNode..ctor(Int32 Id) +89
   umbraco.cms.businesslogic.Content..ctor(Int32 id) +45
   umbraco.cms.businesslogic.web.Document..ctor(Int32 id) +60
   umbraco.dialogs.create.CheckCreatePermissions(Int32 nodeId) +70
   umbraco.dialogs.create.Page_Load(Object sender, EventArgs e) +405
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
   System.Web.UI.Control.OnLoad(EventArgs e) +99
   umbraco.BasePages.BasePage.OnLoad(EventArgs e) +49
   System.Web.UI.Control.LoadRecursive() +50
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627

Version Information: Microsoft .NET Framework Version:2.0.50727.4216; ASP.NET Version:2.0.50727.4209

Hello Takki,

Glad to hear the fix works for you, and thanks for your feedback.

In order to simulate the issue you are experiencing I have setup a blank Umbraco 4.5.2 install (.NET 4). The error already occurs without installing the package however, and it seems to be a bug in the Umbraco version you are using. Here's the link to the workitem I found on codeplex, which has been resolved in Umbraco Juno (4.6.1): http://umbraco.codeplex.com/workitem/28730

In order to resolve this issue I would recommend upgrading Umbraco (from my experience the best upgrade path from 4.5.2 is 4.7.0 and then 4.7.1). I am not sure whether this is feasable for your project, but I can definitely recommend it as we have succesfully completed this excercise for several medium-sized websites.

Grtz

L

When we upgrade we will post back with the results.

is working on a reply...