Closed (fixed)
Project:
Translation Overview
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Jan 2009 at 06:48 UTC
Updated:
4 May 2009 at 10:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
ShutterFreak commentedAccidentally posted a comment for another issue. Still no clue for this issue though. Sorry for the noise.
Comment #2
drewish commentedcould you post a screen shot of what you're seeing?
Comment #3
ShutterFreak commentedHere's a screenshot of admin/content/translation_overview_manage.
Comment #4
Docc commentedsame here
Comment #5
drewish commentedreally odd... can you disable Internationalization and see if it's conflicting with it? i wonder if it's their query rewriting.
Comment #6
ShutterFreak commentedI disabled all modules that rely upon Internationalization, and disabled Internationalization as well. I still get the same output when going to "Administer" → "Content management" → "Translation overview", which leads me to http://example.com/admin/content/translation_overview_manage.
I do not fully understand the permission system of the "Transaction Overview" module, hence I initially did not assign any role to the "manage translation overview priorities" or "view translation overview assignments" permissions. When logged on as Drupal super user I did not see the assignments.
When I added the "view translation overview assignments" permissions to the authenticated user then I 'automagically' saw the assignments.
I suggest automatically adding both privileges for the Drupal super user, and issuing a warning when no roles are assigned the 'view translation overview assignments' permission (like in: "No roles are currently assigned the 'view translation overview assignments' permission. The translation overview table will never be displayed.").
Hope this helps!
Best regards,
Olivier
Comment #7
drewish commentedAh, great thanks for the follow up. Warning if the permissions haven't been granted is a good idea.
Comment #8
ShutterFreak commentedBut shouldn't the Drupal super user in addition always be granted all privileges?
Best regards,
Olivier
Comment #9
drewish commentedIt's not calling user_access() or special casing for uid==1. Here's the relevant part of the code that's doing the check:
I think you could easily make an argument either uid==1 should always return true, or we should be calling user_access() which would have the same effect.
Comment #10
ShutterFreak commentedThanks for your quick reply!
I see. Probably the same "user check" is also currently absent when checking the other Translation Overview permission.
I would strongly recommend adding this check wherever permissions are being checked.
Best regards,
Olivier
Comment #11
drewish commentedHumm... Yeah, I'm actually not sure why I did this as a separate variable rather than using Drupal permissions... I could have been concerned about creating the permissions dynamically. I'm really not sure.
Comment #12
drewish commentedI think doing these as permissions is actually a better way to do it. It lets us drop a bunch of code and make the configuration a lot simpler to setup and understand. This replaces the 'manage translation overview priorities' permission with separate per language manager permissions. The update function will assign the permissions to the roles that are setup to manage.
Comment #13
drewish commentedDid more testing with this and I'm pretty happy. Also rolled in some PHP warning fixes I encountered while testing.
Comment #14
drewish commentedfound one bug and decided to pull the PHP fixes out into their own patch.
i'm pretty close to committing this.
Comment #15
drewish commentedcommitted this to HEAD.
Comment #16
ShutterFreak commentedThanks!