Closed (fixed)
Project:
Time Tracker
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Mar 2011 at 00:30 UTC
Updated:
25 Jun 2011 at 20:28 UTC
Jump to comment: Most recent file
Comments
Comment #1
tom friedhof commentedreuploading a patch that will actually apply
Comment #2
tom friedhof commentedHere is another patch against the development version. More access control for viewing your own time on comments and nodes.
Comment #3
tom friedhof commentedOnce more with a patch that will actually apply ;-)
Comment #4
tom friedhof commentedOops forgot some stuff in that last patch
Comment #5
tom friedhof commentedOne more time
Comment #6
tom friedhof commentedComment #7
drclaw commentedThanks for the *many* patches! =P I'll add this in the next commit.
Comment #8
drclaw commentedI just read through the patch more carefully. Should the time sheet not just use the new time tracker permissions to decide whether or not you can view other peoples time sheets? It would be strange if you don't have the 'view all time tracker entries' permission, but can still 'view all time sheet entries' don't you think?
Comment #9
tom friedhof commentedYeah that's a good point, we should get rid of 'view all time sheet entries', and let 'view all time tracker entries' permission supersede that. I'll integrate the perms more so we don't have redundant perms in two different modules, and time_sheet has a dependency on time_tracker so we know that time_tracker perm will always be there.
Here is the patch again removing the redundant perms.
Comment #10
tom friedhof commentedForgot a access callback, here's the patch again
Comment #11
drclaw commentedThis has been committed to the dev version of Time Tracker. Atrium features have also been updated to match the changes (in case anyone reading this is using the atrium features from github)
Comment #12
linitrex commentedIt seems that there is a problem with the open Atrium feature.
I downloaded the dev version of Time Tracker and the Atrium features
time_tracker-6.x-1.x-dev
fuseinteractive-Atrium-Time-Tracker-e1599e2
I ran update.php that changed one of my tables (I was on time_tracker-6.x-1.0-beta1 before that)
I also enabled the new permissions despite I am the administrator of the site. Now I get.
warning: call_user_func_array() expects parameter 1 to be a valid callback, function 'time_sheet_view_access' not found or invalid function name in /home/osinetwo/public_html/pm.osinetwork.org/includes/menu.inc on line 452.
When I enable the Atrium-Time-Tracker.
Atrium-Time-Tracker is not available in the features list as well.
Comment #13
drclaw commentedYou're getting that error because you don't have the time_sheet module turned on. That was my fault, sorry! I changed the atrium feature to check for the time_sheet module before using that callback function. Try downloading the atrium feature again and let me know if it works.
Secondly, the feature doesn't show up in the features list because it doesn't actually have any 'features'... I guess it's more just a module than a feature. If you look at the module it's just a few theme function overrides and a couple drupal hooks.
Hope this helps!
Comment #14
drclaw commentedfixed
Comment #16
jelle_sI have the same error with the time_sheet module turned on
edit:
changing
to
in atrium_time_tracker_module fixed the problem for me
Comment #17
drclaw commented@Jelle_S
You shouldn't be getting that error. Are you sure you're using the dev version of time_tracker?
Comment #18
drclaw commentedI just tested everything on a fresh install of Atrium and it's working fine. Closing this issue again.