Nifty

Hi @murali-indiacitys

Thanks for sending out the plugin update.

We’ve done some testing, and have noticed that for deleted users tokens to actually be removed, the “Schedule automatic delete tokens without userid (userid=0)” option has to be off. That is, if both “Schedule automatic delete tokens with userid no longer exist” and “Schedule automatic delete tokens without userid (userid=0)” options are on, the tokens for deleted users do not get removed. Is this how it’s supposed to work?

We also noticed that when the cron job schedule is changed, “Save changes” sometimes needs to be clicked twice, before it appears to be updated.

We’re using the WP Crontrol plugin to check the schedule.

Thanks.

Thanks Murali, that sounds great. We really appreciate you adding this option. We’ll look forward to the update. ??

That all sounds great! Good to see you’ve got lots of exciting things coming. ??

Hi Murali,

Thank you for the update. So far, everything looks to be working great!

Is there any way we could donate towards your efforts? ??

Thanks again.

Thanks, Murali! We’ll look forward to hearing back from you. ??

Hi Murali,

Thank you very much for your explanation and the prompt update. The problem looks to be fixed. We will let you know if we encounter any more issues ??.

We have one more question, but could be seen as a feature suggestion, also. How could we disable the notifications (notifications prompt with Allow/Block options) in the browser? We will be encouraging users to download and use the app, thus we are looking to have a website that will essentially be closed off and promote downloading of the app only (while still running BuddyPress and your plugin, but only using the REST API components of the plugins).

For example, in the “API to integrate mobile app” tab, there could be an option to disable the service worker (if that’s the correct reference) for browsers, for those using the PNFPB REST API only. Put simply, notifications will only work through the PNFPB REST API and the user won’t be asked about notifications on the website.

Thanks again and thank you for your ongoing support!

Hi Murali,

Thank you for taking our suggestions onboard, and for the new update. We appreciate the work that you have put in to provide this plugin.

We’re coming across an issue which we’re hoping you can help us diagnose. After applying the update, we are now receiving 2 notifications on our devices that are running our apps, whereas before we only used to receive 1 notification (as expected). Tapping on the first notification works correctly (i.e. our app opens as expected) while tapping on the second notification does nothing. We suspect the first notification does not contain the “click_action” parameter (hence our app opens correctly), however the second contains this “click_action” and tapping on it does not invoke the app.

Our app is written using Xamarin and interfaces with our BuddyPress website via the REST API, and it uses your plugin’s REST endpoint to register Firebase tokens.

Is there a configuration change that we need to make so that we don’t receive the second notification? Or is there an issue somewhere else? We have cleared existing tokens and resubscribed as you had instructed.

Thank you.

Hi Murali,

Thank you for your reply and looking into it.

You are correct, copying and pasting the emoji will work. For sending out push notifications from the admin side, this is fine. However, the challenge is when users who are conversing between each other, type out a message on a phone app (such as a private message), they will use the phone’s keyboard emojis and not the copy and paste method. Having the ability to send a generic message instead of the message’s content in the push notification is the only workaround we can think of at the moment. What are your thoughts?

Thanks.

Hi Murali,

That sounds great; we’ll look forward to the next update. ??

Thanks again.

Hi Murali,

Thank you for your reply, and sorry for our late reply. After further investigation, we realised that our configuration in the Firebase dashboard was incorrect. We had separate app projects for our app and website, when in fact they should have been configured in the same project. We are able to receive notifications successfully now after adding a new web app to our existing project.

We have a few other questions/ideas, please see below:

1. Emojis do not display in the notification that is received (they display as Unicode). We are not sure what can be done about this, but maybe we could have an option to disable the message content being sent in the notification? Instead, maybe an editable setting can be created where you can configure a generic message such as “You have a new message waiting.”, or similar.

2. Since we are only using the REST API to send private message notifications through a native app, would it be possible to add in an option to disable notifications on the website (which are opted into through the web browser)? This would disable the “<domain> wants to Show notifications” prompt on the website.

3. When a private message notification is received on the device, we would like it to open the app when the notification is tapped. We have found that tapping the notification does not do anything, unless ‘click_action’ => $messageurl (line 1805 in pnfpb_push_notification.php) is commented out or removed. As the notification contains a link to the private message and an instruction to open our app, there is a conflict. Removing the ‘click_action’ => $messageurl line fixes this for us. Would it be possible to add in an option to disable the click action being sent with the notification? This would allow more flexibility for when the notification is tapped.

Thank you and looking forward to hearing from you.

Hello,

Thank you, the code works well.

Hi,

Thanks for looking into that.

The direct URL for the activation page works fine [/activate/], but when a new user visits the URL (containing the activation key from the Activation Email) when activating their account [/activate/123/ for example], then “Page not found” is seen in the title.

Thanks.

Hi Andrew,

Thank you for looking into this. We’ve conducted a few tests and while it seems to fix the issues with the Wordfence emails, the BuddyPress emails revert back to being sent in text.

Thanks.

We’re having the same issue on our “Activate” page.
We’re using BuddyPress.

After some further testing, this appears to be an issue with version 1.0.74 of the Rank Math plugin; the issue was resolved when we rolled back to version 1.0.73.

Hi Andrew,

Thanks for your reply. We’ve tried the code and it works to some extent.

It would seem it changes some of the line breaks in Wordfence emails. We’ve noticed the Wordfence emails have gone from HTML to Plain Text format. They display OK, but the format change would probably explain why some line breaks are removed. This may be impacting other emails, but we are not aware of any more yet.

Thanks.