Button to push notifications, does not appear!

Hi,

That’s extremely strange,

Can you confirm if it was working before?

We recently made some changes which were suggested by the OneSignal team, maybe that might have changed some settings, but we have tested before releasing.

Are you sure it was working and then it stopped working? Or you were never able to get it working?

Hello Ahmed,

First of all, I am grateful to respond and care about the issue.

The notifications feature never worked for us. I’ve tried to do everything for the function to appear on the AMP pages, but it does not work, it does not even show anything related to this. However, the One Signal plugin notifications are in perfect working condition on normal, non-amp pages.

I do not understand why, although I’ve never seen it work on any other site that makes use of AMP for WP.

I hope you can help me by investigating this issue.

Thank you very much and congratulations on the great plugin!

I’ll wait for you! ??

Hi @fabinhoalmeida

I guess few people are having this issue because One Signal is the first ones to integrate push notifications on AMP and we are the ones to integrate on this scale.

I am working with One Signal team on solving this issue. Can you please contact us on https://ampforwp.com/support/

So we can have a look in-depth into it.

Hello Mohammed

First, thank you for your attention.

I’ve reported the problem a long time ago for your support, but I have not received a response.

I ask for urgent help, because this problem causes a very big loss for us as we are failing to collect thousands of signatures a day due to lack of correction.

Thank you very much and I look forward to your due assistance.

Hi @fabinhoalmeida

I am sorry for the inconvenience that we might have caused.

I found two emails from you. One was about the AFSanalytics and another about Ads,

But I couldn’t find any recent emails.

Also, I wonder how the push notification’s not working might have caused you loss?

Please help me understand the situation so that we can keep these things in mind and improve in the future.

Hello Ahmed,

First of all, I want to thank you for your response!

The loss I am referring to is the subscribers of notifications that we have failed to collect, since currently the AMP pages of our site are very accessed.

We very much need the One Signal Signature button to work on the AMP pages. We have already followed all the steps recommended in your tutorial, but the push notification feature does not appear on the AMP pages.

Maybe my call does not appear because I must have filled in with our corporate email, “[email protected]”, please see this registration.

I hope you can help us quickly.

Thank you very much for your attention!

Hi @fabinhoalmeida

I’m very sorry for the delay in getting back to you. I was unable to work for a week due to an event in personal life.

I understand that you are facing the issues, Let’s make sure that you got the setup right:

1. Make sure OneSignal info is correct.
2. HTTPs is implementation is correct
3. Test push notifications through AMP CDN.

and then send me the URL so that I can test it as well.

Hello Ahmed,

1. Yes, all OneSignal info is sure.
2. My site is HTTPS, as the function requires.
3. I already did the AMN CDN test, and none of this worked.

Follow the link for you to check:

https://www-areavip-com-br.cdn.ampproject.org/c/s/www.areavip.com.br/novelas/o-outro-lado-do-paraiso/o-outro-lado-do-paraiso-mercedes-revela-segredo-do-passado/amp/

Thank you!

Hi @fabinhoalmeida

That’s really strange then, We have implemented as per their standard practice.

I would recommend you to get in touch with One Signal team to see what might be the issue.

Hello friends

I finally figured out what affects the operation of push button notifications from OneSignal on my amp pages.

It happens that the file that is invoked (…/wp-content/plugins/accelerated-mobile-pages/includes/onesignal-integration/amp-helper-frame.html) is an html file and, because our site is old, we have made changes to the url (slug / permalink) of WordPress posts over the years. So we had to redirect the posts with “.html” to “/” (https://site/category/post.html >> to >> https://site/category/post/) and this rule affects the file html required by the Amp for Wp plugin.

My host’s team tried to isolate this rule only for the permalik not to reach the plugin, but they said it was not possible in our case that it is a Ngnix account.

Is there any alternative solution you can give me in this case?

Thank you very much

Hi @fabinhoalmeida

Can you please setup a staging site with that permalink and reach out to us on [email protected] ?

I will have my developer test on it, and make sure we find the issue and fix it.