Francesco Aprile

Hi, this is not completely exact because other user can click on delete icon and see the message of deleting package, what the sense of this? If works like you said the plugin have to forbidden other user to delete the other package.

Yes, thanks.
Best regards

Hi, very bad news. This is a must have feature. So if user receive a lot of packages assigned only to him he cannot search and find easily. No
Good!

Hi, yes exactly. So user will get soon that the package is added successfully.
Best regards

Try with author or agent user, won’t work.

Yes, I did.

Hi, i sue already that add-on, simply. ask to search the member(s) to assign to the package by real name and not username like work right now. If you add an option the add-on settings where admin can choose how to search the members (username or real name) would be very great.
That’s it!
Best regards

For the first I have already that add-on and I enabled as well, for the second I have this setting already in that way but once I add a package I don’t see this so I cannot edit.

Hi, about the first point I know what you said but I think that the access doesn’t work in logical way.
In your example: Package Access = Package Access + All Category Access = All Visitors + Author = All Visitors. So why do I need to select author if the package will be for all visitors? However I am talking to set access to specific member by selecting his username and not the role but I am afraid that your plugin work in the same way. So I repeat: I don’t see any reason to select role or member in add package form if these don’t do any effect. For this I asked the feature about point 3 and honestly I think should be already, because assigning a category to the package make useless the other more specific accesses like role(s) and member(s).

About the point 2 I am talking about the notification mail “new package added” to send to the member selected so he know that there is a new package added for him. I hope it’s clearer.

For the last: how user who added a package and selecting a specific member can edit this? I noticed that once I added this package with that access he cannot see this on frontend so he cannot edit for every reason. It is necessary that at least who added package can see it and manage it (edit, delete…).

Best regards

Hi, to understand better. If I assign the package to some category there isn’t any possibility to assign the package to a member? I suppose the assign the package to member(s) always override the ACL. I work only by share packages to specific members, in my case the public package are rare. So do I have to avoid to use categories in this case?
About the second question you can access to my backed with admin credentials I sent you already. However if I cannot delete so better see a message I cannot and not let me delete and after see the package again.
Best regards

Hi, I downloaded and installed the latest version of access control add-on but the issue still remains. Stil other user can see and download the “test” file.
You can check it too.
Best regards.