• Resolved egonzaleztest

    (@egonzaleztest)


    Since the last AMP update, we’ve encountered this issue. We use <!–nextpage–> to paginate our big features on desktop/mobile. AMP has always ignored this code and presented those features as one page. Now, though, our AMP pages are killing all content after it hits a <!–nextpage–>, meaning that our readers aren’t seeing our full content. We’re trying to avoid having to unpaginate all our features as a temporary fix.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Ahmed Kaludi

    (@ahmedkaludi)

    Can you please share some screenshots related to your issue?

    Thread Starter egonzaleztest

    (@egonzaleztest)

    Here is a screencap of our code. On desktop/mobile, the pagination loads perfectly (see here). Since we started using the AMP plugin, it has consistently ignored <!–nextpage–> and presented lists like this as a single page, but since the latest update to the plugin, it is no longer being ignored; rather, it is now effectively killing the content. See here for the AMP version of the list, when ends at number 91 out of a Top 100 list.

    Thread Starter egonzaleztest

    (@egonzaleztest)

    Ahmed. My apologies, but it seems like my programmer sent me in the wrong direction. We are using another AMP plugin. Sorry for the inconvenience, though if it helps, I wish we were using yours!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Pagination Error’ is closed to new replies.