• Resolved stormdiscount

    (@stormdiscount)


    Plugins page in backoffice not accesible.

    mysite/plugins.php HTTP ERROR 500

    Logfile: FastCGI sent in stderr: “PHP message: PHP Fatal error: Call to undefined function ampforwp_is_non_amp() in /mysite/wp-content/plugins/accelerated-mobile-pages/accelerated-moblie-pages.php on line 404” while reading response header from upstream

    Just started this morning.

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

    (@ampforwp)

    Hello @stormdiscount

    Can you please contact me on team@magazine3.com so I can check it and will solve it for you.

    Thread Starter stormdiscount

    (@stormdiscount)

    Hi already did send the email to team@magazine3.com

    Regards,

    Bernhard

    Plugin Contributor ampforwp

    (@ampforwp)

    Hello @stormdiscount

    Ok, our team will look into this issue there and will solve it for you.

    I have the same issue/ticket open. Still waiting for a resolution. From all the reports of the same issue I am guessing this is a bug and you will fix it on a new release?

    Hi @stormdiscount just out of curiosity, did you get the issue resolved?

    Same problem here @ampforwp, please publicly help solving this here instead.
    Others like @havig and me would like an online solution for people to Google for.

    • This reply was modified 5 years, 11 months ago by djvdorp.

    @djvdorp I concur. I have been trying to work with the @ampforwp team by providing them admin access to one of my sites and I ended up having to restore the site from a previous backup. Now the site works like a charm.

    It is quite hard to trust with credentials when the site is left with more issues, other plugin’s data missing, etc.

    I just offered them creating a staging site for them to work on and see if they can come up with a solution. After waiting for 2 days in a row until after midnight my time to work with them and help solve the issue. If they believe there is a plugin conflict, I could have either help with it or reach out to those developers for a fix. I was stood up both times.

    Let’s hope they positively respond to this offer or they come up with a new release that actually works. I really don’t have much more time to invest on this.

    AMP is not a ranking factor. Speed is. My site is extremely fast and as an SEO I like to try and test new technologies. I think AMP is a very interesting way to make more developers think about speed, better code, less javascript dependency and I have seen WP theme developers going that route. But Kinsta has even pulled out of AMP, I may follow suit. I would love to stay but I don’t have the resources to support this effort more than I already do.

    Here’s to hope.

    Thread Starter stormdiscount

    (@stormdiscount)

    Hi Havig,

    Actually the two updates after receiving this error did not solve the problem.

    There was a request from the team to have ftp acces, but i actually decided to turn of this amp module for the time being and wait some time for a new version. The regular APM module amp-wp works without any problems.

    Not that i do not trust the tech people from ampforwp team, but actually i do not run an ftp on my own server. And in general i do not allow third party to my system since i also run a commercial website on it where i receive payments and such. WordPress i actually only use for SEO.

    Conclusion, problem not yet solved. But i guess this is also because i did not provide accces to solve the issue. In my opinion these people work hard to deliver a good product. And you cant complain for such a free module with great support. Ill just wait it out untill its solved.

    @stormdiscount I fully agree with you. That’s why I am even offering the creation of a staging area for them to play in on my server. If that’s not willingness to help I don’t know what is.
    If you retrieve their version before these two updates (0.9.91) you will be good on the meantime with a much better looking AMP version of the page.
    I am waiting to see if they want me to create that staging site and will also wait it out. But if too much time passes I cannot have a plugin that’s outdated for security reasons and also because AMP changes so much.
    I don’t mind paying for their Premium version either. I would gladly come back to it, if I can get some piece of mind.

    Plugin Contributor ampforwp

    (@ampforwp)

    Hello @havig,@stormdiscount

    Can you please update the plugin to 0.9.96 version and check if the issue gets fixed or not.

    Please let us know.

    Thread Starter stormdiscount

    (@stormdiscount)

    Good Day ampforwp,

    Thank you for the follow up. Applied the update and upgraded to 0.996 and the issue is solved.

    Thanks you for your support. One of the best i have seen.

    Regards,

    Bernhard.

    Plugin Contributor ampforwp

    (@ampforwp)

    Hello @stormdiscount

    Glad to hear your issue get fixed now.

    We always try to give best “I mean very best” possible support to our users but in very rare case some users might not get our reply quickly because of we have so many users request for help.

    BTW, now happy because your issue is fixed.

    Hi @ampforwp ! This is great news! I am so glad it worked for @stormdiscount.

    I am not close to where I can update and then bring back the old version if it fails so I will try it in a couple of days and keep you posted.

    Meanwhile, and this is a question where all can benefit. You have a new field under the Analytics Tab. You suggest filling it out with “googleanalytics”. What exactly are we indicating here?
    a- that we use google analytics and not adobe analytics? or
    b- the type of implementation of the tag: analytics tag (.js and .ga) vs google tag manager?
    If option b is true, what if the value that is expected for GTM? a- GTM, b- googletagmanager, c- other?

    Thank you so much for answering this question in advance and I look forward to having a successful plugin update process!

    Hello?

    Plugin Contributor ampforwp

    (@ampforwp)

    Hello @havig

    I have replied to the thread which you have opened please check it.

    Now I am closing this thread because the issue is resolved.

    Thank you.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Call to undefined function ampforwp_is_non_amp()’ is closed to new replies.