Defect #3
ajax pagination of projects
| Status: | Closed | Start: | ||
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected version: | Resolution: | |||
Description
Is it just me or is the AJAX project pagination broken in .4.1?
I'm testing with more than 15 projects and the Next and Page 2 links are not working.
I can research more, but perhaps this is a known issue?
Associated revisions
Commit messages are now scanned for referenced or fixed issue IDs.
Keywords and the status to apply to fixed issues can be defined in Admin -> Settings.
Default keywords:
- for referencing issues: refs, references, IssueID
- for fixing issues: fixes,closes
There's no default status defined for fixed issue. You'll have to specify it if you want to enable auto closure of issues.
Example of a working commit message: "This commit references #1, #2 and fixes #3"
History
2007-01-19 12:21 - Jean-Philippe Lang
I've just tested with 50 projects and it seems to work fine.
Can you tell on which screen you have the problem and what the
problem exactly is (what does happen when you click on the pagination
links ? an error occurs ?).
Thanks
2007-01-21 08:37 - Todd McGrath
No errors, but I was running it locally on WebBrick. I'll
report back if I find something more specific. Thank you
for looking at this
2007-01-21 15:00 - Jean-Philippe Lang
It should work fine on webrick too.
Tell me if you it's not the case.