Feature requests: User ID search and addition of thread ID

[Nifty]

Hi Murali,

Hope you’re going well.

We are using the plugin “BuddyPress Moderation Tools” to suspend users that violate our Terms and Conditions. While we understand that not every other plugin can incorporate this plugin to automatically delete the tokens of the suspended user, would it be possible to add a User ID search to the “Device tokens” page? This way we can manually lookup the tokens of the suspended user via their User ID and then select and bulk delete them. The reason we need to do this is because they are still able to receive on demand push notifications.

We were also wondering if it was possible to add the thread ID of a private message into the data section as a key/value pair when the Firebase notification is sent through the PNFPB REST API? This would enable us to open the appropriate message thread in our app when the user taps the notification. (Ref. https://firebase.google.com/docs/cloud-messaging/js/send-with-console)

Thank you!

[Murali]

I will look into it and I will add these 2 requirements in this week release.

[Nifty]

That sounds amazing, Murali! Thank you, very much. We’ll look forward to it.

[Murali]

Hi

1.50 released today with following changes, (along with your requirements), thread id will be under push notification data (for both website and for webview mobile app).

1. Action scheduler to process more than 1000 subscribers in more than one queue with 1000 subscribers each in background mode. Since Firebase accepts 1000 deviceids per send, action scheduler will be included in upcoming release to schedule in queue (1000 device ids each queue). It will process in asynchronous way to reduce server load.
2. Private message Thread id for mobile app in notification under data to open private message thread directly in mobile app using deep link
3. Activity comment link update in notification
4. Search button in Device tokens list admin panel to search user id and tokens
5. Clearing of stale/invalid tokens for webview mobile apps. For websites, this logic is already present.
6. On demand push notification panel changes to include image link and click action link
7. Removed character limit in on demand push notification
8. DB table changes to include web_auth and web_256 fields in database for future use incase if users wants to migrate tokens from other push service providers
9. Fixed problems related to post title while scheduling notifications for POST
10. Javascript routine to receive tokens from android java app using webview javascript interface
11. New admin tab for scheduled actions in background

• This reply was modified 2 years, 2 months ago by Murali.

[Nifty]

Hi Murali,

Thanks for such a comprehensive update! So far, everything seems to be working really well. The only minor thing we’ve noticed is that when a Device Token search is done, the number of items (i.e. “_ items” label on the top and bottom right of the table) does not reflect the search results. E.g. if you have 20 tokens total and search for a specific user ID, the total number of items will still display “20 items” regardless of how many results are returned.

Thanks again. ??

[Murali]

I will fix this in next release. Total items needs to be updated based on search results like below , I will update it in next release along with some more enhancements in pnfpb_icfcm_device_tokens_list.php after line 220. I will fix this in next release.

		if ( isset($_POST['s']) ) {
			$this->items = self::get_devicetokens( $per_page, $current_page, $_POST['s'] );
		}
		else 
		{
			$this->items = self::get_devicetokens( $per_page, $current_page, '' );
		}
		$total_items  = count($this->items);
		
		$this->set_pagination_args( [
			'total_items' => $total_items, //WE have to calculate the total number of items
			'per_page'    => $per_page //WE have to determine how many items to show on a page
		] );

[Nifty]

Thanks, Murali; that sounds great. ??

[Nifty]

Hi Murali,

Thanks for the updates to the plugin; this seems to have fixed this issue. ??