Support » Plugin: AMP for WP - Accelerated Mobile Pages » Internal 500 errors

  • Today I got a message from Google to tell me that there are a few hundred pages from my site with internal 500 errors.
    Those pages end with /amp while the pages from the site all end with /?amp
    Why do those errors don’t redirect to my 404 page?
    Any clues?

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

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Contributor ampforwp

    (@ampforwp)

    Hi @foodstyling,

    Did you recently enable the “Change End Point to ?amp” option?

    Let us know.

    Thank you

    When trying to access the page I get following message:

    CF7 Polylang Module Extension requires Contact Form 7 & Polylang plugins, and has therefore been deactivated!

    Also you told me to use the AMP extension ?amp instead of AMP, because my Polylang menu wasn’t working, a problem you never fixed.

    For now when i use ?amp the pages are showing up
    When using ?amp/ I get the original no AMP page

    And this in addition of the error 500 pages.

    Can you please fix all those problems?
    Thanks

    Plugin Contributor ampforwp

    (@ampforwp)

    Hi @foodstyling,

    Sorry for the inconvenience.

    We’ve already created a ticket for the internal 500 error issue, And it is in under development & forwarded to the testing department. However, this issue is very critical for those who have changed there AMP endpoint to ?amp. So, I’ll mark this ticket as very urgent and add in the next update.

    Here is the ticket link: https://github.com/ahmedkaludi/accelerated-mobile-pages/issues/2480

    Hope it helps.

    Thanks for the answer, I hope you find a solution, but I remember you that you told me to use /?amp instead of /amp because you couldn’t solve the polylang menu.
    I’am using the polylang extension, and I really don’t understand what this extension its used for

    Plugin Contributor ampforwp

    (@ampforwp)

    Hi @foodstyling,

    Making endpoints to ?amp will help you get the amp in tricky setups with taxonomies & post types. And coming to the polylang issue, we’ve added this support feature with AMP in a tricky setup. The question mark in the URL will not make any difference in the SEO.

    Hope you understand.

    Thank you

    Thanks and I hope the 500 issue will get fixed soon!
    And as the Polylang menu concern, I just noticed that the menu works quit well with /?amp with the exception of the submenus, which are working with the non-AMP pages.

    Plugin Contributor ampforwp

    (@ampforwp)

    Hi @foodstyling,

    We’re soon adding the above GitHub ticket in the upcoming updates. Hope you’re all issues will get fixed.

    Thank you

    I just disabled AMP, to much stress.I found out that my regular pages load as fast, and sometimes faster than AMP pages!
    The submenu’s with AMP pages didn’t work neither.
    So I’ll wait till Google AMP gets adult to try it again

    Thanks

    Plugin Contributor ampforwp

    (@ampforwp)

    Hi @foodstyling,

    Sure, however the above ticket we’ve resolved and added in the v0.9.97.41 which will be releasing on next week.

    Hope it helps.

    May be i’ll try for the last time. I hate to tell you that after almost every upgrade some new problems arose, so I think I’ll wait till this AMP thing gets more adult, if ever…

    Plugin Contributor ampforwp

    (@ampforwp)

    Hi @foodstyling,

    Before releasing the update, we test the latest version on several local servers and it’s forwarded to the security & general testing dept and then we push the updates.

    However, every user have a different WordPress use-case scenario or the environment and we can’t test on their environment but we try our best to give the better AMP experience to the user and stable updates. In rare cases, some users get the new issues with the latest version and we act immediately & solved in the next update.

    Can you please list out the issues which you’re facing? I’ll personally check and will make sure everything will work perfectly on your website as well. Please give us a once chance.

    Hope you understand.

    Thank you

    Hi,
    Google’s rules are sometimes a little weird, like the one for images…

    My personnel issues are: errors 500, submenus are not working,and most of all, my regular site loads fast, about the same time then the AMP version, and I like the non-AMP version better. And on top of that since redirected AMP, almost get a significant increase in visits…

    But I’ll certainly try your new version

    Thanks!

    Plugin Contributor ampforwp

    (@ampforwp)

    Hi @foodstyling,

    Regarding the error 500, We’ve fixed the issue in the latest version. Please update the plugin

    And for the sub-menus, it should work. However, please contact to our paid plugin’s technical team. I’ll tell them to act your query very quickly and fixed the issue witin a short time. And I assure you that you’ll not get these type of errors in the future.

    Sure, you can try our new version.

    Hope it helps.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Internal 500 errors’ is closed to new replies.