Opened 18 years ago
Closed 18 years ago
#380 closed task (fixed)
P4 activity doesn't show up in Timeline view
Reported by: | Kenji Nakamura | Owned by: | ttressieres |
---|---|---|---|
Priority: | low | Component: | PerforcePlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.10 |
Description
I noticed P4 activity no longer shows up in Timeline page as the result of migration from 0.9 + the original perforce.py attached to #257, in which that function was working. Is it a missing feature, or installation / configuration issue?
Thansks,
Kenji
Attachments (0)
Change History (11)
comment:1 Changed 18 years ago by
Status: | new → assigned |
---|
comment:2 Changed 18 years ago by
Trac Release: | 0.9 → 0.10 |
---|
I used TracPerforce-0.3-py2.4.egg for 0.10. I took sandbox/vc-refactoring from svn as of 5/18/06 for Trac. I see only "Milestones", "Ticket changes", and "wiki changes" check boxes at the upright box.
comment:3 follow-up: 4 Changed 18 years ago by
I had this problem as well. After poking around I found that versioncontrol\web_ui\changeset.py
's get_timeline_filters
wasn't being called. The ComponentMeta registry ìncluded trac.versioncontrol.web_ui.changeset.ChangesetModule
but the filter in core.py's ExtensionPoint.extensions removes it from the list.
The quick solution to this was to change trac.ini's settings: (added the line in the middle)
p4trac.* = enabled trac.versioncontrol.* = enabled trac.versioncontrol.svn_fs.* = disabled
This works for me, hopefully I'll find time to dig a little deeper, some day ;)
Can someone else confirm that this does the trick? If so, we can update the PerforcePlugin wiki page.
comment:4 Changed 18 years ago by
Replying to bjornswift:
Can someone else confirm that this does the trick? If so, we can update the PerforcePlugin wiki page.
I tried the instruction, but no luck. I'm using Trac taken from sandbox/vc-refactoring
svn as of 5/18/06 . Which version are you using?
comment:5 follow-up: 6 Changed 18 years ago by
I'm using r3391, checked out 19.06.2006.
The trac.ini changes didn't do the trick? Did you restart apache/tracd after the change?
comment:6 Changed 18 years ago by
Replying to bjornswift:
I'm using r3391, checked out 19.06.2006.
The trac.ini changes didn't do the trick? Did you restart apache/tracd after the change?
Yes, I did. Did you take r3391 from trunk? My original trac.ini didn't have p4trac.* = enabled
and trac.versioncontrol.svn_fs.* = disabled
so I'm wondering if I use different codebase from yours. My code was vc-refactoring in sandbox.
comment:7 follow-up: 8 Changed 18 years ago by
No, I checked it out from /trac/sandbox/vc-refactoring
:
svn co http://svn.edgewall.com/repos/trac/sandbox/vc-refactoring
The current revision is 3551, I haven't tested this against that version - will next week.
The trac.ini changes weren't in trac.ini by default, I added them as described in PerforcePlugin#SettingupaTracenvironment
comment:8 Changed 18 years ago by
Replying to bjornswift: I upgraded my environment to r3391, and worked fine. Thanks!
comment:10 Changed 18 years ago by
Can we close off this ticket now?
Is this still a problem for people in PerforcePlugin 0.4.1?
comment:11 Changed 18 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Do you try the version of p4trac in PerforcePlugin (0.9 or 0.10) ??
I've tested it at work and at home and it works for me.
What's your Trac version ????