Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross db mount record access vs. "Restrict to one group" #10

Open
kitzberger opened this issue Oct 30, 2018 · 4 comments
Open

Cross db mount record access vs. "Restrict to one group" #10

kitzberger opened this issue Oct 30, 2018 · 4 comments

Comments

@kitzberger
Copy link

When setting a user to "Restrict to one group" it's possible to have a user switch to one role, "copy" a record, switch to the next role and try to "paste" that record onto a page with a different db mount. If both roles come with different db mounts, pasting is impossible but the user is not informed of that and nothing happens. Only in the log module an error message shows up:

Attempt to copy record "tt_content:24010" which does not exist or you do not have permission to read

This might actually be a core bug ("no error message when trying to paste a non-readable record") but I thought this should at least pop up in this tracker here, because I cannot think of any other way of having a record's reference in the clipboard that's non-readable anymore all of a sudden but switching the role with this extension here. And maybe you come up with a super easy solution too ;-)

PS: with copy/paste I mean TYPO3's clipboard functionality.

@IchHabRecht
Copy link
Owner

Hi @kitzberger,

By reading the issue, I don't know how to solve this problem. The only thing that came to my mind was, I need to ensure the clipboard is cleared. Without having access to a record, it is not possible to copy/move it to any other page.

@kitzberger
Copy link
Author

Hi @IchHabRecht,

sorry for the late feedback on this here ;-/

I think part of this problem is that editors in general think that copying a record actually copies it and not just the reference to it ;-)

Clearing the clipboard could be a solution, but I'm afraid it could be too harsh for some cases, e.g. when there are sufficient permissions to actually do the "cross-role/db-mount" copying. Maybe it's possible to only clear the clipboard when the permissions wouldn't be enough?

Now that I'm thinking about it: isn't that rather a core issue that needs to be fixed on that end? I assume there could be scenarios where such a situation could occur without your extension being involved.

@IchHabRecht
Copy link
Owner

Hi @kitzberger,

I don't think it is a real core issue, as there isn't currently any feature to change ones usergroup on the fly. In the context of how the core works, you either have access to one record (and can copy/move it) or you haven't. As far as I know there isn't any "in between". That is why I wrote the extension ;-)

I will try to implement the reset of the clipboard (only for records the current usergroup has no access to), in the next couples of days (or weeks as Christmas comes very close). Would you mind to test a patch ones it is available?

@kitzberger
Copy link
Author

Yeah, sure. Glad to help out here ;-)

Regarding the core: it could be that user A is copying a record and user B is changing that records pages permissions, right? It's a rare case for sure but resulting in the same weird error message, i assume.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants