CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.6 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Feature #32110

User Authorization possible

Added by Harald no-lastname-given over 1 year ago. Updated 8 months ago.

Status:Closed Start date:2011-11-27
Priority:Should have Due date:
Assignee:Michael Knoll % Done:

0%

Category:-
Target version:YAG 2.0
Votes: 0

Description

Hello YAG-Team!

I miss the way through the galleries of different user access control.

Although it is the "Access" option available. However, this does not really. The Gallery at hiding or albums will still be displayed. I have the feeling, because something is not working properly? Am I doing something wrong or is there now, "yet" the opportunity to do so?

Because I for different people want different galleries on the same page offer that is a very big wish of mine.
Images are or can be something very personal. I think this is the reason why I would need this urgently.
Thank you very much
Harald

History

Updated by Michael Knoll over 1 year ago

Hello Harald,

to be honest, I don't get all of your issue. As far as I can see, you want to have to possibility to restrict the access of the images for some of the FE-Users.

At the moment, the only way to do this is by putting several content elements on a page and restrict the access to this content elements via standard TYPO3 access restrictions in content elements. You cannot set access rights within YAG (yet). It would be not a big issue to implement this, but at the moment, it is not possible.

So there are 2 solutions:

1. You implement this feature and send us a patch. We will review and add it.

2. We think about how to implement it, calculate the costs and wait for someone to pay us for this.

We would really like to implement all the stuff that you guys think is cool and useful but unfortumately, we do not have the time. So if anyone pays for it - here we are... or you just have to wait until we need the feature and implement it.

Greez

Mimi

Updated by Michael Knoll over 1 year ago

  • Category set to Waiting for Sponsorship
  • Status changed from New to Accepted

Updated by Michael Knoll over 1 year ago

  • Category deleted (Waiting for Sponsorship)
  • Status changed from Accepted to On Hold
  • Target version set to Waiting for Donation

Updated by Harald no-lastname-given over 1 year ago

Hello Mimi!

Thank you for the quick reply. Yes that was exactly my question. Restricting access to a content item I've found. I could already solve my problem, if one could assign individual galleries several albums. Is that somehow possible?
Multiple selection for albums. Assigning two Galleries the same album

That would be a simple solution if I could assign one album to more galleries!

Example:
3 users + 3 albums

(access control) Plugin >> Gallery-Users-A

  • Album-A <<< multible Album

(access control) Plugin >> Gallery-Users-B

  • Album-A <<< multible Album
  • Album-B <<< multible Album

(access control) Plugin >> Gallery-Users-C

  • Album-B <<< multible Album
  • Album-C

Is this possibly to be implemented with TYPO Script?

Thank you very much

Harald

Updated by Michael Knoll over 1 year ago

Hi Harald,

assigning multiple albums to a single gallery seems to be an easy solution when it comes to using it but actually it is a rather hard solution when it comes to implementation. So you should not rely on such a solution as it won't be implemented like that any time soon. We are thinking about something like a category-system which is about the same as you want, but it won't be finished any time soon.

Be aware that even if you would solve this like you mentioned, it is still possible for advanced FE-Users to manipulate the URL in such a way, that he / she can see restricted content, as yag itself will not check, whether a user is allowed to see a certain album or not. So this is not a secure solution!

We will be thinking about an access restriction.

Greez

Mimi

Updated by Michael Knoll about 1 year ago

  • Assignee set to Michael Knoll
  • Target version changed from Waiting for Donation to YAG 2.0

Since we are taking enable fields into account, we can solve this issue by "simply" using tce_forms in backend for editing albums / galleries / items. User access can than be set within these forms.

Updated by Michael Knoll about 1 year ago

  • Status changed from On Hold to Accepted

Updated by Thierry Brodard about 1 year ago

Hi Michael,

It would be sure a very usefull and needed feature to allow "ACL" for galleries. It's really a need for multisite environnement.
A good customer of mine need it in the next 8 weeks. Do you think it will be then available ?

Thanks again for this great extension !
Thierry

Updated by Michael Knoll about 1 year ago

Hi Thierry,

we are kind of working at that issue atm. It is possible to add access rights for FE users right now via editing the records via list module once you created them in the yag backend module (this is a little complicated and we will try to make it easier any time soon).

For backend users, you can achieve this functionality by using different PIDs for storage which will be possible with 2.0 which we plan to release before mid August. If you want to try it earlier, get the latest development branch from github:

https://github.com/michaelknoll/yag/tree/feature12571-respect-pid

PIDs are almost stable!

If you need anything for commercial use in your projects, you are free to sponsor a feature, so we will focus on that!

Best regards

Michael

Updated by Thierry Brodard 11 months ago

Hi Michael,

I come back now to the project. I've just tried to clone the last version from Github: I'm not able to create gallery or album record in another page than the page "0".
If I make it in a sysfolder record, then, the record doesn't appear after saving. I think it's a normal behaviour for such records, but make impossible to have different PIDs for storage.

Is the version on Github dependent on newer versions of pt_extlist or pt_extbase ?

Updated by Michael Knoll 8 months ago

  • Status changed from Accepted to Closed

PIDs and user rights are respected in version 2.0. So backend user rights are respected.

When it comes to frontend, each gallery, album and item can be edited in list module and user access rights can be set. Records that don't have the required access rights won't be displayed to users in frontend anymore.

So - besides a better user interface, this issue is closed.

All required changes will be available in version 2.0

Also available in: Atom PDF