No changelog events to see in ticket

I had this issue, but I found I needed to install simplejson:

easy_install simplejson

Yes, but I'm using Python 2.6, and simplejson is built-in. I had to change the source from "simplejson" to "json"

(In [9250]) Fixed #7746

Richard,

Importing the "json" library doesn't fix the problem. I couldn't install the plugin without that fix, so I manually fix the code. Plugin seems to be installing well, but I'm unable to view the changelog, even with the TICKETLOG_VIEW permission.

Any idea's?

You can check the following:

1. Browse Source works, and you can see the target changelog
2. The plugin is installed properly, you can see it in Admin -> Plugins
3. You have the TICKETLOG_VIEW permission
4. The target changelog match the regex setting

Thanks, I figured out the regex is not working. I was using a ":" character right after the ticket number. Changed the regex to: log_pattern = \s*#%s+(:)\s+.*

Fixed now!

I, too, cannot see a changelog.

Replying to richard:

You can check the following: 1. Browse Source works, and you can see the target changelog 2. The plugin is installed properly, you can see it in Admin -> Plugins 3. You have the TICKETLOG_VIEW permission 4. The target changelog match the regex setting

Yes to all those.

I'm unclear as to when the information should appear on the ticket - should there always be changelog section? If I view the generated page source should I expect to see a reference to the changelog plugin?

Other queries: does it work with old changesets logged in with the correct format? Can it deal with multi-line comments?; Can a single changeset refer to multiple tickets?

Replying to andrew.hardy@gl-group.com:

I, too, cannot see a changelog. Replying to richard:

You can check the following: 1. Browse Source works, and you can see the target changelog 2. The plugin is installed properly, you can see it in Admin -> Plugins 3. You have the TICKETLOG_VIEW permission 4. The target changelog match the regex setting

Yes to all those.

If all work as expected, there should be something wrong.

Did you enable javascript of your browser? If yes, you can watch what's happening with firebug in firefox.

I'm unclear as to when the information should appear on the ticket - should there always be changelog section? If I view the generated page source should I expect to see a reference to the changelog plugin?

The changelog list is done by Ajax query after the whole page is loaded. So, you can't see it in page source.

Other queries: does it work with old changesets logged in with the correct format? Can it deal with multi-line comments?; Can a single changeset refer to multiple tickets?

Yes. This plugin just query the trac database table, so old changesets is ok.

It can display multiline comments, with plain text instead of wiki format, and joined lines.

This plugin did not support multiple tickets with it's default regular expression rule, but you can make one easily by changing the log_pattern setting. The default is:

[ticketlog]
log_pattern = \s*#%s+\s+.*

I can see a jquery that seems to be asking for the ticket/changeset information. The returned json does not contain any changeset details. From FireBug I see:

post:

JSON
		
 
	
ticket_id
	"190"
Source
{"ticket_id":"190"}

reponse:

{"status": "1", "data": {"headers": ["Changeset", "Author", "Time", "ChangeLog"], "header_width": ["5em", "6em", "8em", ""], "ticket_id": "190", "revisions": []}}

JSON

 
	
data
	Object { headers=, more...}
 
	
header_width
	["5em", "6em", "8em", ""]
 
	
0
	"5em"
 
	
1
	"6em"
 
	
2
	"8em"
 
	
3
	""
 
	
headers
	["Changeset", "Author", "Time", "ChangeLog"]
 
	
0
	"Changeset"
 
	
1
	"Author"
 
	
2
	"Time"
 
	
3
	"ChangeLog"
 
	
revisions
	[]
 
	
ticket_id
	"190"
 
	
status
	"1"

My changeset comment is:

#190 Modified job_name created by amfr_messaging for faxes to be 'more' unique than prevously. Problem observed whilst monitoring in production.
Removed spurious comments from tpda_data_acquisition.

OK... just refreshed the screen and now the changelog details are appearing! I don't know what is happening - perhaps a timing issue or caching?

I'll let you know if the problem resumes.

Got it working finally. Seems it was fixed following some steps for tracstats. https://github.com/mrjbq7/tracstats

Troubleshooting ===============

If you use Git (i.e. the GitPlugin for Trac) and are not able to see any of the code statistics, you likely need to configure it to cache the repository to make it work:

[git] cached_repository = true persistent_cache = true

You might need to run trac-admin <trac repos> repository resync "*" after the change.

Example: trac-admin "E:\Documents and Settings\riccopy\BitNami? Trac Stack projects\xxxx" repository resync "*"