Souptik Datta

<p><a href="https://github.com/Souptik2001/all-path-messaging" rel="nofollow ugc">Check out the Github Repository ♥</a></p>
<p><strong>Limitless Communication:</strong> All-in-one, super scalable, messaging Solution for WordPress.</p>
<p>Ok hold on! ✋. So, many words in one line.<br />
Let’s understand each one-by-one.</p>
<ul>
<li><strong>All-in-one:</strong> What do you want? – Email, SMS, push-notification? Get all-in-one.
<ul>
<li>But I don’t want to use <code>xyz</code> provider for SMS, I want to use <code>pqr</code>, can I have that? Yes it provides you with lot of pre implemented providers for all email, sms and push-notification.</li>
</ul>
</li>
<li><strong>Super Scalable:</strong> But I want to use an email provider named <code>yxr</code> you haven’t heard the name of. Now what? 🧐
<ul>
<li>No worries! Are you a developer? If yes, just write your own plugin and implement your own adapter and see it nicely hooked-up with “WordPress messaging”. Please refer to <a href="https://github.com/Souptik2001/wp-messaging/wiki/Create-your-own-Adapter-%F0%9F%9B%A0%EF%B8%8F" rel="nofollow ugc">this</a> section for implementing adapters.</li>
</ul>
</li>
</ul>
<p>And that’s how it provides <strong>Limitless communication</strong>! 🚀</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/80hWdK8kREM?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h3>Quick Links</h3>
<p><a href="https://github.com/Souptik2001/wp-messaging/wiki/Setup-%E2%9A%99%EF%B8%8F" rel="nofollow ugc">Setup ⚙️</a> | <a href="https://github.com/Souptik2001/wp-messaging/issues" rel="nofollow ugc">Issues</a> | <a href="https://github.com/Souptik2001/wp-messaging/wiki/Services-and-functions-%F0%9F%A7%A9" rel="nofollow ugc">Services and functions 🧩</a> | <a href="https://github.com/Souptik2001/wp-messaging/wiki/Create-your-own-Adapter-%F0%9F%9B%A0%EF%B8%8F" rel="nofollow ugc">Create your own Adapter 🛠️</a></p>
<h3>Coming soon ⏳</h3>
<ul>
<li>Push notifications</li>
<li>Email Testing page</li>
<li>SMS Testing page</li>
<li>Push notifications Testing page</li>
</ul>
<h3>Examples</h3>
<h4>Email 📧📨</h4>
<p>Send an email through a particular adapter (with headers 😉) –</p>
<pre><code>\Souptik\AllPathMessaging\Email\send(
  [ 'dev2@souptik.dev' ],
  'Yay its working!',
  'This is some long mail body.',
  'Souptik',
  'dev1@souptik.dev',
  [
   'cc' => [
    [
     'name'  => 'CC Test',
     'email' => 'cc@souptik.dev',
    ],
   ],
   'attachments' => [
    trailingslashit( WP_CONTENT_DIR ) . '/mu-plugins/test-all-path-messaging.php',
     'SameFileDifferentName.php' => trailingslashit( WP_CONTENT_DIR ) . '/mu-plugins/test-all-path-messaging.php',
   ],
  ],
  'mailgun'
 );
</code></pre>
<p>Just remove the last parameter! And now it uses the default selected adapter –</p>
<pre><code>\Souptik\AllPathMessaging\Email\send(
  [ 'dev2@souptik.dev' ],
  'Yay its working!',
  'This is some long mail body.',
  'Souptik',
  'dev1@souptik.dev',
  [
   'cc' => [
    [
     'name'  => 'CC Test',
     'email' => 'cc@souptik.dev',
    ],
   ],
   'attachments' => [
    trailingslashit( WP_CONTENT_DIR ) . '/mu-plugins/test-all-path-messaging.php',
     'SameFileDifferentName.php' => trailingslashit( WP_CONTENT_DIR ) . '/mu-plugins/test-all-path-messaging.php',
   ],
  ],
 );
</code></pre>
<p>Checked the override <code>wp_mail</code> checkbox? Try a simple <code>wp_mail</code>! –</p>
<pre><code>wp_mail(
  [ 'dev2@souptik.dev' ],
  'Yay its working!',
  'This is some long mail body - from <strong>wp_mail</strong>.',
  [],
  []
 );
</code></pre>
<h4>SMS 📲</h4>
<p>Send a SMS through a particular adapter –</p>
<pre><code>\Souptik\AllPathMessaging\SMS\send( [ '+xxxxxxxxxxxx' ], 'Yay its working!', 'twilio' );
</code></pre>
<p>Just remove the last parameter! And now it uses the default selected adapter –</p>
<pre><code>\Souptik\AllPathMessaging\SMS\send( [ '+xxxxxxxxxxxx' ], 'Yay its working!' );
</code></pre>
<h3>Creating your own adapter 🛠️</h3>
<p>Here comes the cool part fellow developers! 💻</p>
<p><strong>Tip:</strong> I have provided a dummy adapter for each service at <code>inc/<service>/adapters/dummy/</code>.</p>
<p>Consider that as the starting point and let’s understand what each file does.</p>
<ul>
<li>Let’s start with <code>namespace.php</code>. It is the entry point of your adapter.
<ul>
<li>In that you will see a simple <code>bootstrap</code> function.</li>
<li>In that function we are hooking into <code>EMAIL_SLUG . '_adapters'</code> and registering our adapter.</li>
<li>We pass the following data –</li>
<li><code>slug</code></li>
<li><code>name</code></li>
<li><code>adapter</code> class object.</li>
<li><code>options</code> – An array defining the settings required for this adapter, which will be used to automatically display the options on the settings page.</li>
</ul>
</li>
<li>Next is <code>class-adapter.php</code>, which is the Adapter class, which we initialized in the above file and passed it to <code>adapter</code>. It contains three simple functions –
<ul>
<li><code>get_settings_fields</code> – This is the function which returns the array of options, which we used in the above file for <code>options</code>. Each option, will have –</li>
<li>The key as the name of the option.</li>
<li>And three values –
<ul>
<li><code>label</code> – Label to display in the settings page beside the input.</li>
<li><code>type</code> – Type of the field.</li>
<li><code>sanitize_callback</code></li>
</ul>
</li>
<li><code>get_settings</code> – This function returns an associative array, whose keys are the name of the options and the value as the value of the options.</li>
<li><code>get_adapter</code> – This function will just return the core provider class, which is responsible for processing the message.</li>
<li>First check if <code>Utopia Messaging</code> already provides the provider or not <a href="https://github.com/utopia-php/messaging?tab=readme-ov-file#adapters" rel="nofollow ugc">here</a>, for example <code>Utopia\Messaging\Adapter\Email\Mailgun</code>.</li>
<li>If it is present just use it. Easy peasy! ✨</li>
<li>But if not, let’s code it ourself, because <code>Utopia Messaging</code> makes it so easy to create a new adapter!</li>
</ul>
</li>
<li><code>class-dummy.php</code> is for that purpose, assuming you don’t get a provider already present in <code>Utopia Messaging</code>.
<ul>
<li>It’s basically a child class of <code>EmailAdapter</code> or <code>SMSAdapter</code>, which abstract a lot of stuff for us!</li>
<li>Let me explain two main functions, <code>_construct</code> and <code>process</code>. <em>Rest of the functions and properties are self-explanatory!</em> 😉</li>
<li>In the <code>_construct</code> function just put the arguments which you want to accept. That’s it! And now they will be available everywhere else as <code>$this->param_name</code>!</li>
<li>The <code>process</code> function is the place where you have to write the main logic of calling your providers API to send the message.
<ul>
<li>As said above all the credentials/data you accepted through constructor are available as <code>$this->param_name</code>.</li>
<li>Build the <code>body</code> and the <code>headers</code>.</li>
<li>And then you can use the <code>$this->request</code> function as demonstrated in the dummy!</li>
<li>Create a response using Utopia’s <code>Response</code> class.</li>
<li>Handle the errors, populate the response, return! Done! 🚀</li>
</ul>
</li>
</ul>
</li>
</ul>
<h3>External services</h3>
<h4>Brevo</h4>
<p>This plugin connect’s to Brevo’s API to send emails through Brevo. This is the <a href="https://api.brevo.com/v3/smtp/email" rel="nofollow ugc">API</a> it sends the request to.<br />
The request is send everytime a mail is sent, and Brevo is selected as the default adapter from the plugin settings (or the function to send email through Brevo is directly invoked in the code).<br />
Here is the <a href="https://www.brevo.com/legal/termsofuse/" rel="nofollow ugc">Terms of Use</a> and <a href="https://www.brevo.com/legal/privacypolicy/" rel="nofollow ugc">Privacy Policy</a> of the service.</p>
<h4>AWS SES</h4>
<p>This plugin connect’s to AWS SES’s API to send emails through AWS SES.<br />
The request is send everytime a mail is sent, and AWS SES is selected as the default adapter from the plugin settings (or the function to send email through AWS SES is directly invoked in the code).<br />
Here is the <a href="https://aws.amazon.com/service-terms/" rel="nofollow ugc">Terms of Use</a> and <a href="https://docs.aws.amazon.com/ses/latest/dg/data-protection.html" rel="nofollow ugc">Privacy Policy</a> of the service.</p>
<h4>Mailgun</h4>
<p>This plugin connect’s to Mailgun’s API to send emails through Mailgun.<br />
The request is send everytime a mail is sent, and Mailgun is selected as the default adapter from the plugin settings (or the function to send email through Mailgun is directly invoked in the code).<br />
Here is the <a href="https://www.mailgun.com/legal/terms/" rel="nofollow ugc">Terms of Use</a> and <a href="https://www.mailgun.com/legal/privacy-policy/" rel="nofollow ugc">Privacy Policy</a> of the service.</p>
<h4>Telesign</h4>
<p>This plugin connect’s to Telesign’s API to send SMS through Telesign.<br />
The request is send everytime the function to send SMS is invoked with the Adapter as Telesign or the default adapter is set as Telesign.<br />
Here is the <a href="//www.telesign.com/telesign-terms-of-service" rel="nofollow ugc">Terms of Use</a> and <a href="https://www.telesign.com/privacy-policy" rel="nofollow ugc">Privacy Policy</a> of the service.</p>
<h4>Twilio</h4>
<p>This plugin connect’s to Twilio’s API to send SMS through Twilio.<br />
The request is send everytime the function to send SMS is invoked with the Adapter as Twilio or the default adapter is set as Twilio.<br />
Here is the <a href="https://www.twilio.com/en-us/legal/tos" rel="nofollow ugc">Terms of Use</a> and <a href="https://www.twilio.com/en-us/legal/privacy" rel="nofollow ugc">Privacy Policy</a> of the service.</p>


All Path Messaging

Limitless Communication: All-in-one, super scalable, messaging Solution for WordPress.

Murali

<p><strong>Push Notification for Post and BuddyPress (PNFPB)</strong> delivers free web push notifications to desktop browsers, Android, and iOS devices using Firebase Cloud Messaging (FCM) HTTP v1, self-hosted WebPush (VAPID), OneSignal, or Progressier as the push provider. Notifications fire automatically when posts, custom post types, or BuddyPress events are published. The plugin also generates a full Progressive Web App (PWA) with offline cache support.</p>
<h4>Push Notification Providers</h4>
<p>Choose one or more providers to match your infrastructure:</p>
<ul>
<li><strong>Firebase HTTP v1 (FCM)</strong> – recommended; supports browser, Android, and iOS. Free via Google Firebase.</li>
<li><strong>WebPush (self-hosted VAPID)</strong> – open standard; no Google account required; browser-only.</li>
<li><strong>OneSignal</strong> – hosted service; supports browser and mobile app push. Free tier available.</li>
<li><strong>Progressier</strong> – hosted PWA push provider.</li>
<li><strong>webtoapp.design</strong> – push for mobile apps generated by webtoapp.design. Can run alongside Firebase or OneSignal to reach both browser and app audiences simultaneously.</li>
</ul>
<h4>Notification Triggers</h4>
<p><strong>WordPress content</strong></p>
<ul>
<li>New post or custom post type published (including bbPress topics).</li>
<li>New WooCommerce product published.</li>
<li>New comment on a post.</li>
</ul>
<p><strong>BuddyPress / BuddyBoss</strong></p>
<ul>
<li>New activity update (supports <code>[member name]</code> dynamic tag).</li>
<li>New group activity (delivered only to group members; supports <code>[group name]</code> tag).</li>
<li>Activity comment posted.</li>
<li>Private message sent — delivered only to the recipient (compatible with BP Better Messages).</li>
<li>Friendship request sent — delivered only to the recipient.</li>
<li>Friendship request accepted — delivered only to the requester.</li>
<li>New member joined.</li>
<li>Member avatar changed.</li>
<li>Member cover image changed.</li>
<li>Group details updated — delivered to group members.</li>
<li>Group invitation sent — delivered only to the invited user.</li>
<li>Activity marked as favourite / liked — delivered to the activity author.</li>
<li>BuddyPress follow (requires BuddyPress Followers plugin).</li>
</ul>
<p><strong>Admin-only notifications</strong></p>
<ul>
<li>Contact Form 7 submission received.</li>
<li>New user registration.</li>
</ul>
<p>Full documentation is available at <a href="https://wiki.pnfpb.com/" rel="nofollow ugc">wiki.pnfpb.com</a>.</p>
<h4>Scheduling</h4>
<p>Every notification type can be sent immediately or scheduled using WordPress Cron (hourly, twice-daily, daily, weekly). For high-volume sites, enable <strong>background scheduling via Action Scheduler</strong> to process 200,000+ subscribers without hitting PHP execution limits.</p>
<h4>On-Demand Push</h4>
<p>Send a push notification to all subscribers at any time from the admin panel — with a custom title, message body, image, and click URL. One-time and recurring schedules (daily, weekly, monthly) are supported.</p>
<h4>AI Assistant</h4>
<p>PNFPB includes an optional AI assistant for two workflows:</p>
<ul>
<li><strong>On-demand push</strong> – generate a notification draft from the current form data before sending.</li>
<li><strong>Post notification</strong> – generate suggested title, content, and send time from the post editor.</li>
</ul>
<p>The AI layer uses a provider contract so the backend can be swapped later without changing the notification workflow. You can also control privacy settings so only the required content is shared with the AI provider.</p>
<h4>Frontend Subscription Controls</h4>
<ul>
<li><strong>Custom popup prompt</strong> — configurable subscription dialog that appears automatically in the browser. Users can select which notification types they want (posts, activities, comments, friendships, etc.) at subscribe time or later.</li>
<li><strong>Bell icon prompt</strong> — persistent bell widget for subscribe/unsubscribe without a full page reload.</li>
<li><strong>BuddyPress profile tab</strong> — a Push Notifications tab is added to each member’s profile settings for managing subscriptions.</li>
<li><strong>Group subscribe button</strong> — subscribe/unsubscribe button added to BuddyPress group headers.</li>
</ul>
<h4>Shortcodes</h4>
<ul>
<li><code>[subscribe_PNFPB_push_notification]</code> — renders an inline subscribe/unsubscribe button with a notification-type preference panel. All button labels and colors are configurable under PNFPB <span aria-hidden="true" class="wp-exclude-emoji">→</span> Customize Buttons.</li>
<li><code>[PNFPB_PWA_PROMPT]</code> — renders the PWA install prompt. Use this when the automatic footer prompt is disabled and you want a specific page or sidebar widget to trigger the install flow.</li>
</ul>
<h4>Progressive Web App (PWA)</h4>
<p>PNFPB generates a web app manifest (<code>pnfpbmanifest.json</code>) and service worker (<code>pnfpb_icpush_pwa_sw.js</code>) so visitors can install your site as a home-screen PWA on any device.</p>
<ul>
<li>Configure app name, short name, start URL, display mode, theme color, background color, and icons (192×192 and 512×512 PNG required).</li>
<li>Define a list of page URLs to cache for offline viewing. Uncached pages fall back to a built-in offline page.</li>
<li>Customisable PWA install prompt (banner or dialog style) with separate iOS guidance (Safari <span aria-hidden="true" class="wp-exclude-emoji">→</span> Share <span aria-hidden="true" class="wp-exclude-emoji">→</span> Add to Home Screen).</li>
<li>iOS 17.0+ required for full PWA install support.</li>
<li><strong>NGINX servers:</strong> if dynamic file serving is unavailable, enable the static file option in PNFPB <span aria-hidden="true" class="wp-exclude-emoji">→</span> NGINX settings to write the service worker and manifest as static files to the site root.</li>
</ul>
<h4>Mobile App Integration</h4>
<ul>
<li><strong>REST API</strong> — register FCM/APNs device tokens from native Android or iOS apps via <code>POST /wp-json/pnfpb/v1/subscribe</code>. Allows push notifications to reach both web subscribers and native app users from the same WordPress event.</li>
<li><strong>webtoapp.design</strong> — dedicated integration for WebView-based apps generated by webtoapp.design.</li>
<li>Sample Android and iOS client code is available on GitHub (linked in the installation instructions below).</li>
</ul>
<h4>Multisite</h4>
<p>The plugin is multisite-compatible. On network activation it creates the required database tables for every existing site, and automatically provisions tables for new sites added to the network.</p>
<h4>Firebase Analytics</h4>
<p>When Google Analytics is linked to your Firebase project the plugin sends <code>notification_open</code>, <code>notification_read</code>, and <code>page_view</code> events to the Firebase Analytics console for open-rate reporting.</p>
<h4>Developer Extensibility</h4>
<ul>
<li><strong>Action hooks</strong> to trigger post or BuddyPress activity notifications programmatically from your own code.</li>
<li><strong>Filter hook</strong> <code>pnfpb_service_worker_extension</code> to inject custom JavaScript into the generated service worker — the standard integration point for combining PNFPB with other service-worker-based plugins.</li>
<li>Full hook, filter, REST API, and database schema reference: <a href="https://wiki.pnfpb.com/developer-reference/" rel="nofollow ugc">wiki.pnfpb.com/developer-reference/</a></li>
</ul>
<h4>Demo</h4>
<p><a href="https://www.pnfpb.com/" rel="nofollow ugc">Test PNFPB on the demo site</a></p>
<h4>Knowledgebase</h4>
<p><a href="https://wiki.pnfpb.com/" rel="nofollow ugc">Documentation on PNFPB plugin available at wiki.pnfpb.com</a></p>


Push Notification for Post and BuddyPress

Push notifications for WordPress post, BuddyPress, WooCommerce with PWA support, mobile app integration, and AI Notification drafts.

All Path Messaging vs Push Notification for Post and BuddyPress