By Jeromy Waunch on Friday, 13 January 2017
Posted in General Issues
Likes 0
Views 282
Votes 0
If I should have posted more than one ticket, please let me know.

I just installed web push notifications, but am having a couple odd issues.
1. The welcome message is displaying the field name rather than a welcome message. (I disabled the welcome message until we can get it fixed.)
2. All other messages were displaying the field names, but after a forum search I copied the files recommended in Titlethis thread, and most seem to be resolved.
3. Notifications for someone "liking" a post are attributing the "like" to the first one who liked it, rather than the most recent person to click "like."
4. The icon on the notifications is not the user's avatar, but rather its onesignal's logo.
5. I haven't seen any chrome or firefox notifications, so I think they are not working (all notifications have been from Safari on Mac so far)

Thank you.
Hi Jeromy Waunch,

For this issue, it is okay to to put multiple inquiry as it is related with one another
As I'm running windows OS I've test the web push notification was not working on Chrome and Firefox, It might some misconfiguration in the onesignal setting.
Perhaps, can you provide us with your onesignal login credential so we can have a look on that.
I'll ask my colleague to test it on Safari as well

You can add the information needed by edit your first post in the Details section or you can just include your site's access once at http://stackideas.com/dashboard/site rather than needing to keep adding them in your replies
·
Friday, 13 January 2017 15:21
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you. It's edited.
·
Friday, 13 January 2017 23:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Jeromy,

Can you please edit your first post to also include the site and FTP access as well.

P/S: Please leave the onesignal login details under the "Others" section.
·
Saturday, 14 January 2017 00:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Mark. I've updated my login info on my http://stackideas.com/dashboard/site page.
·
Saturday, 14 January 2017 01:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

I've checked your OneSignal configuration seems configured correctly, I suspect because of your subdomain causing the issue so the OneSignal manifest JSON file unable to load correctly.

Can you try download my attached file and replace into this following file location and see how it goes?

JoomlaFolder/media/com_easysocial/apps/user/onesignal/onesignal.php

If the issue still persists, can you update your FTP user account to have the permission to access your current site Joomla root folder? Because now I was unable to access it, you can refer on my second screenshot below.
·
Saturday, 14 January 2017 12:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry about that! I've adjusted (and tested) the ftp account so that you can have root access. The safari web push messages so far seem to be giving the correct text, but the rest of the issues in the first post seem to still exist. Thank you!
·
Saturday, 14 January 2017 12:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Jeromy,

We have inspected your site and there is 2 major issue that caused your push notifications to fail:

1. The SDK files which you downloaded from https://documentation.onesignal.com/docs/web-push-sdk-setup-https MUST be placed on your root folder. This is a requirement from web browsers to allow push notifications. See my screen shot here, http://take.ms/LuzTC . I have helped you to move these files to your www folder, http://imarklee.stackideas.com/Monosnap_2017-01-14_13-21-18.png

2. Your manifest.json contains invalid codes, http://take.ms/znSHl . It should just be a double quote.

The push notifications is working fine now
·
Saturday, 14 January 2017 13:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Mark for the fix and letting me know where my error was. Things are much better, but I am still having a few issues. I also updated to the latest version of the Web Push app this morning, but it didn't make a difference as far as my issues are concerned. My issues, in no particular order:

1. Mac Safari notifications are still showing the OneSignal logo rather than the user's avatar. (though the logo is working fine with Chrome, and it looks so nice I really want it in my main browser. )
2. The notification in Chrome for liking my comment displays a title of "COM_EASYSOCIAL_LIKES_ITEM_SYSTEM_TITLE" of an invite only group. But when posted on the user's page, it gives a correct notification. (image attached)
3. The Push App welcome message is displaying field names for the welcome message. (image attached). I also have it currently turned off, so that the field names don't confuse my users.
4. On the backend, the switch to turn the welcome message on & off displays the field names for labels (image attached)
·
Sunday, 15 January 2017 00:12
·
0 Likes
·
0 Votes
·
0 Comments
·

1. Mac Safari notifications are still showing the OneSignal logo rather than the user's avatar. (though the logo is working fine with Chrome, and it looks so nice I really want it in my main browser. )

I believe Mac Safari doesn't allow overriding of the notification icon Perhaps you could upload your own logo when configuring the app? http://take.ms/8vWME


2. The notification in Chrome for liking my comment displays a title of "COM_EASYSOCIAL_LIKES_ITEM_SYSTEM_TITLE" of an invite only group. But when posted on the user's page, it gives a correct notification. (image attached)

Are you still able to reproduce this?


3. The Push App welcome message is displaying field names for the welcome message. (image attached). I also have it currently turned off, so that the field names don't confuse my users.

I have fixed this as the language file didn't get updated during the update.


4. On the backend, the switch to turn the welcome message on & off displays the field names for labels (image attached)

I have fixed this as the language file didn't get updated during the update.
·
Sunday, 15 January 2017 14:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks Mark, all the language file issues seem to be resolved. You all have done a ton of work on these issues, and it's greatly appreciated! As far as the Safari Web Push Notification goes, I've uploaded the image file to use for the Safari push notifications, and I'm still getting the OneSignal logo on my notifications. I've tried .png and .tiff format. I'm not sure why it isn't changing.
·
Monday, 16 January 2017 09:02
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Jeromy Waunch,

Perhaps can you try to upload image format .ico with size 256 x 256 as lined in the safari's setting documentation and see how it goes?
https://www.screencast.com/t/ixbe78pAHH
·
Monday, 16 January 2017 11:42
·
0 Likes
·
0 Votes
·
0 Comments
·
Wow oops!!! I feel foolish now. I'll check it out in the morning.
·
Monday, 16 January 2017 11:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Sure Jeromy
·
Monday, 16 January 2017 13:32
·
0 Likes
·
0 Votes
·
0 Comments
·
Just tried using a .ico file, 256x256, and it's still using the OneSignal logo rather than the image I uploaded. I can't think of what I'm missing... I've attached it as a zip file (because .ico was unsupported), just in case it helps.
·
Monday, 16 January 2017 13:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Jerome,

Seems like the old icon was cache in your browser. Perhaps can you try to follow this steps:
To see your updated icon set, simply remove notification permissions for your Safari site. On Safari's top menu bar, go to Safari -> Preferences -> Notifications and remove your site's entry. Then visit your site again and subscribe to notifications. The moment you see the permission prompt, the new icons will be downloaded to your system and you should see them right away on the permission prompt.

Because I've ask my colleagues to do the same steps its appear the updated icon now
refer this screenshot: https://www.screencast.com/t/IQkZv3fr58
reference : https://documentation.onesignal.com/docs/troubleshooting-web-push#section-my-safari-notification-icons-aren-t-showing-up
·
Monday, 16 January 2017 16:03
·
0 Likes
·
0 Votes
·
0 Comments
·
Thank you!! It's working fine now. Much appreciated!
·
Monday, 16 January 2017 23:54
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating, glad that your issues are resolved now Jeromy
·
Monday, 16 January 2017 23:55
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post