Fixed Wrong link at the Recent Comments block

[imthebest]

Hi,

On /media there is the gallery index which contains a Recent Comments block. On my forum one of the 5 entries on that block contains the following link:

http://www.mysite.com/media/comments/46995/

When I click on the link it transforms itself into:

http://www.mysite.com/media/in-house.65570/?page=2#comment-46995

The problem is that on that page I can see the media but no comments. It says "There are no comments to display."

However if I load the media directly:

http://www.mysite.com/media/in-house.65570/

I can see the media with all its comments (there are 10). And here appears to be problem, I allow a maximum of 10 comments per page on the media view. It looks like the system generates a wrong link (?page=2#comment-46995) when in fact there is only 1 page of comments with the latest comment being the comment #10.

Thanks,
Super120

 

[imthebest]

Btw on the Recent Comments block clicking on the avatar of the user who left the comment drives you to the media item where he left the comment which is confusing. I think the avatar should open the membercard.

 

[Chris D]

That's currently consistent with the Resource Manager blocks.

 

[Chris D]

Hi,

On /media there is the gallery index which contains a Recent Comments block. On my forum one of the 5 entries on that block contains the following link:

http://www.mysite.com/media/comments/46995/

When I click on the link it transforms itself into:

http://www.mysite.com/media/in-house.65570/?page=2#comment-46995

The problem is that on that page I can see the media but no comments. It says "There are no comments to display."

However if I load the media directly:

http://www.mysite.com/media/in-house.65570/

I can see the media with all its comments (there are 10). And here appears to be problem, I allow a maximum of 10 comments per page on the media view. It looks like the system generates a wrong link (?page=2#comment-46995) when in fact there is only 1 page of comments with the latest comment being the comment #10.

Thanks,
Super120

This is fixed in the next release, thanks.