Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Issue information

Issue ID
#035541
Status
Fixed
Version
2.5.1
Fixed in
2.5.1
Severity
1 - Low

Issue Confirmations

Yes (6)No (0)

0

Marketplace using Chrome is slightly broke

Posted by GC-Flitterkill on 24 January 2012 - 10:49 PM

Chrome browser, unless the Marketplace category has sub-categories, it will only display one item per page.

For example, Nexus under the Marketplace has two pages but only displays a single item on each page. Firefox correctly displays ten on the first and the rest on the second. This affects gallery and downloads as well as they are the other Marketplace categories without sub categories.

3.3 related? Strange as hell... Confirmed on my desktop and laptop Chrome instances. Everything is fine on FireFox and IE 9 as far as I can tell.

Not sure if this is a IPB site bug or a Nexus bug or a 3.3 bug. Move as needed.

Back to top

teraßyte

moved issue from IPS Web Site and Client Area (not for software issues)

bfarber

Jan 25 2012 10:41 AM

Sounds like a query inside a loop, but I can't imagine how that would only affect Chrome and not other browsers.

Back to top

bfarber

changed status to: Confirmed - General

bfarber

Jan 25 2012 10:41 AM

Oh, I can reproduce in Firefox.

Back to top

Freeborne

Jan 25 2012 10:12 PM

I have this problem on Firefox, Chrome and Safari.

Tested on 3 different computers.

It only happens when you get to the last 'category' in the left-hand menu for any area.

Eg:
IP.Board is fine
IP.Board > Skins is fine
IP.Board > Skins > Dark Skins is not (only shows 1 item per page).

Back to top

bfarber

changed status to: Fixed,

changed version to: 2.5.1,

changed fixed-in version to: 2.5.1

bfarber

Jan 26 2012 10:23 AM

Was already fixed locally it appears. Applied the fix to the co forums. Believe this is due to the item marking changes, which I already have a private report about sorting in the next release anyways (topic marker changes have a new API that would prevent this issue beyond the fix already implemented).