Bug #8115

Allowed languages for translation not working when they are set creating a NEW user

Added by José Raddaoui Marín about 7 years ago. Updated about 7 years ago.

Status:VerifiedStart date:03/18/2015
Priority:MediumDue date:
Assignee:Dan Gillean% Done:

0%

Category:Access Control
Target version:Release 2.2.0
Google Code Legacy ID: Tested version:2.2
Sponsored:No Requires documentation:

Description

To reproduce:

- Create new user adding "Allowed languages for translation" on the same process
- Log in with new user and open a description with the interface in one of the allowed laguages

Result:

- The description can't be edited in the allowed language
- The interface can't be edited either

Expected result:

- Both edit options are allowed in the allowed language after the user is created

Further testing:

- Edit the new user (the allowed languages won't be saved)
- Add allowed languages an save
- Visit a description in one of the allowed languages
- Now both edit are working


Related issues

Related to Access to Memory (AtoM) - Bug #7817: QubitAcl buildAcl method should not scan permissions belo... Verified 01/14/2015
Related to Access to Memory (AtoM) - Bug #8116: Wrong table in edit actor and repository permissions for ... Verified 03/18/2015

History

#1 Updated by José Raddaoui Marín about 7 years ago

  • Related to Bug #7817: QubitAcl buildAcl method should not scan permissions belonging to other users added

#2 Updated by José Raddaoui Marín about 7 years ago

  • Status changed from New to Code Review
  • Assignee changed from José Raddaoui Marín to Mike Gale

PR 121

#3 Updated by José Raddaoui Marín about 7 years ago

  • Related to Bug #8116: Wrong table in edit actor and repository permissions for users added

#4 Updated by Mike Gale about 7 years ago

  • Assignee changed from Mike Gale to José Raddaoui Marín

Looks good to me. Also, apparently qubot on Github thinks so too (?!) :)

#5 Updated by José Raddaoui Marín about 7 years ago

  • Status changed from Code Review to QA/Review
  • Assignee changed from José Raddaoui Marín to Dan Gillean

#6 Updated by Dan Gillean about 7 years ago

  • Status changed from QA/Review to Feedback

I could edit the user interface elements, but every time I tried to edit a description in Spanish (after creating a new user, adding them to translator group, adding Spanish as the language, and then logging in as the new user), I could get into the edit template, but never save, because when I tried, I would get a "permission denied" message.

#7 Updated by Dan Gillean about 7 years ago

Update: turns out my edits were saving.... I could see them after I logged in as the admin user. ???

Going to check the permissions on my new user and see what's up - maybe there is another permission setting that is preventing them from seeing the updates?

#8 Updated by Dan Gillean about 7 years ago

  • Assignee changed from Dan Gillean to José Raddaoui Marín

maybe you can help me out, Radda. I hate the UI for this - it's really hard to tell what the default permissions for a user are, or even a group, the way it just displays "inherit" for everything. inherit what from where????

It seems like there is maybe some problem with the default permissions for the tranlsator group that might be affecting the ability to submit edits, even if they are in the allowed language? not sure.

#9 Updated by José Raddaoui Marín about 7 years ago

You're right Dan, it looks like the description is being saved but it's also turned to draft, so the translator can't see it after that. Other problem is that I could edit the description with the translator in all the languages, not only in the allowed one.

I created this ticket after finding that the permision is saved without user in the database, but it looks like it's not working well after all. I'll take a deeper look.

#10 Updated by José Raddaoui Marín about 7 years ago

  • Status changed from Feedback to QA/Review
  • Assignee changed from José Raddaoui Marín to Dan Gillean

Users can translate in all languages if they are part of the "Translator" group. Without being in that group users can only edit the allowed languages, so that wasn't a problem (I think).

About the permission denied page, that happens because there is also a permission to publish records and, if the user doesn't have it, the description status is changed to the default publication status.

#11 Updated by Dan Gillean about 7 years ago

  • Status changed from QA/Review to Verified

Also available in: Atom PDF