Bug in AMP version - by marat0998 - on WordPress WooCommerce support

This topic has 7 replies, 2 voices, and was last updated 4 years, 7 months ago ago by marat0998

  • Avatar: marat0998
    marat0998
    Participant
    April 25, 2021 at 08:25

    On shop page pagination not working with AMP version. We already using Proper permalink structure but when we visit shop page(AMP) and click on pagination we are redirected to home page.

    We also tested same thing on your official demo link.

    Let us know how can we solve it or just guide us which file and code we have to modified because our site is live we need to fix this soon as possible

    6 Answers
    Avatar: marat0998
    marat0998
    Participant
    April 25, 2021 at 09:24

    Why are you ignoring my guestion?

    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    April 25, 2021 at 09:37

    Hello,

    Provide URL, temporary wp-admin, and FTP access.
    Our technicians team is not available during the weekend, but they will check the problem tomorrow.
    Waiting for credentials.

    Regards

    Avatar: marat0998
    marat0998
    Participant
    April 25, 2021 at 10:32

    Done

    Please contact administrator
    for this information.
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    April 25, 2021 at 12:05

    Hello,

    Download XStore AMP plugin from this page – https://dropmefiles.com/un5YX and replace this plugin on your site.

    Regards

    Avatar: marat0998
    marat0998
    Participant
    April 25, 2021 at 14:45

    Thanks it works fine

    Avatar: marat0998
    marat0998
    Participant
    April 25, 2021 at 14:48

    Hi again

    we are using 8theme widget for filter our product but look like all 8theme widget not working with AMP version and default widget is working fine.

    Even we are calling Our Brand Taxonomy from database Brand still not showing in AMP filter.
    Can you, please solve that problem?

  • Viewing 7 results - 1 through 7 (of 7 total)

The issue related to '‘Bug in AMP version’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.