BuddyDev

Search

[Resolved] MediaPress type=photo pagination not working

Tagged: ,

  • Participant
    Level: Master
    Posts: 279
    Richard Foley on December 9, 2017 at 2:12 pm #12200

    hi Brajesh,

    I’m having a couple of issues using the following shortcode to display images only:

    [mpp-list-media type=”photo” component=”members” status=”public” per_page=12 pagination=1]

    The pagination does not work (it seems to work fine with galleries). Regardless of which parameter is passed/clicked eg; “?mpage=33”, the display always reloads from what would be mpage=1. The variable is visible in the location URL, but the display is always the first page.

    Is there a way to influence the “order by” (date) which is returned?

    I’m using MPP v1.2.0

    R.

  • Keymaster
    Level: Yogi
    (BuddyDev Team)
    Posts: 2952
    Ravi on December 9, 2017 at 11:51 pm #12203

    Hello Richard,

    Brajesh sir is away that’s why I am posting here.

    I have tested this shortcode with MediaPress version 1.1.9 and it is working fine for me. Is there any custom code you are running for MediaPress.

    Yes, MediaPress Media list has order by support into the shortcode. You can use this. Other supported values for this attribute are “none, id, user, title, slug, date,modified, random, comment_count, meta_value,meta_value_num, ids”

  • Participant
    Level: Master
    Posts: 279
    Richard Foley on December 10, 2017 at 8:52 am #12204

    hi Keymaster,

    thanks for the response. I’ll double-check whether something else is stepping in and taking over the mpage pagination step. Then I’ll feedback here.

    Cheers

    R.

  • Participant
    Level: Master
    Posts: 279
    Richard Foley on December 13, 2017 at 7:39 am #12316

    Ah, it seems that when I use /media/ as the url root of the page for this shortcode, I see the NON-paging behaviour I describe in the bug report.

    However, when I change the url root to something else, say /photos/, then I see the correct paging that would be expected.

    While it’s not a complete fix, it’s enough to suggest this might not be a MediaPress issue, so, closing as resolved. Weird though 🙂

You must be logged in to reply to this topic.

This topic is: resolved