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

user losing access to abstract after adding another owner #430

Open
twachtler opened this issue Dec 19, 2018 · 2 comments
Open

user losing access to abstract after adding another owner #430

twachtler opened this issue Dec 19, 2018 · 2 comments
Assignees

Comments

@twachtler
Copy link
Member

There were two or three cases where a user added another user as owner to an abstract and then could not access the abstract any more (500 internal server error), although the database still had the user as owner. A restart of GCA was necessary to restore order. There were other cases where adding another owner did not cause any problems, so this may be hard to figure out, but it is a serious issue and should be fixed.

@mpsonntag
Copy link
Contributor

This might be related to issue #86.

@fschrader1992 fschrader1992 self-assigned this Jan 2, 2019
@fschrader1992
Copy link
Collaborator

fschrader1992 commented Jan 2, 2019

If someone is removed as owner, the abstract might still be listed to her/him in "my abstracts", but access is denied. Conference owners might also be able to edit abstracts, if they were abstract owners before.

@mpsonntag mpsonntag self-assigned this Jan 23, 2019
mpsonntag added a commit to mpsonntag/GCA-Web that referenced this issue Jan 23, 2019
Using the 'isOwner' instead of 'contains' method
in the abstract 'update' method. It is suspected
that the 'contains' method does not work as expected.
See issue G-Node#430 for details.
mpsonntag added a commit to mpsonntag/GCA-Web that referenced this issue Jan 23, 2019
Using the 'isOwner' instead of 'contains' method
in the abstract 'update' method. It is suspected
that the 'contains' method does not work as expected.
See issue G-Node#430 for details.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants