Defect #3

ajax pagination of projects

Added by Todd McGrath over 15 years ago. Updated over 9 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:


Target version:-
Resolution: Affected version:


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

Revision 473
Added by Jean-Philippe Lang about 15 years ago

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"


#1 Updated by Todd McGrath over 15 years ago

I apologize. This was my fault entirely. I was updating
the layouts/base.rhtml page and removed the <div
id="content">. From what I understand, the ajax
requires it, so that's why it appeared not to work.

#2 Updated by Jean-Philippe Lang over 15 years ago

It should work fine on webrick too.
Tell me if you it's not the case.

#3 Updated by Todd McGrath over 15 years ago

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

#4 Updated by Jean-Philippe Lang over 15 years ago

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 ?).


#5 Updated by Jean-Philippe Lang over 15 years ago

I'll have a look at this issue this evening.

Also available in: Atom PDF