Souptik Datta

<a href="https://github.com/Souptik2001/all-path-messaging" rel="nofollow ugc">Check out the Github Repository ♥</a>
Limitless Communication: All-in-one, super scalable, messaging Solution for WordPress.
Ok hold on! ✋. So, many words in one line. 
Let’s understand each one-by-one.
<ul>
<li>All-in-one: 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>Super Scalable: 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>
And that’s how it provides Limitless communication! 🚀
<iframe loading="lazy" title=""All Path Messaging" WordPress plugin Overview" width="750" height="422" src="https://www.youtube.com/embed/80hWdK8kREM?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
<h3>Quick Links</h3>
<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>
<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>
Send an email through a particular adapter (with headers 😉) –
<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>
Just remove the last parameter! And now it uses the default selected adapter –
<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>
Checked the override <code>wp_mail</code> checkbox? Try a simple <code>wp_mail</code>! –
<pre><code>wp_mail(
 [ 'dev2@souptik.dev' ],
 'Yay its working!',
 'This is some long mail body - from wp_mail.',
 [],
 []
 );
</code></pre>
<h4>SMS 📲</h4>
Send a SMS through a particular adapter –
<pre><code>\Souptik\AllPathMessaging\SMS\send( [ '+xxxxxxxxxxxx' ], 'Yay its working!', 'twilio' );
</code></pre>
Just remove the last parameter! And now it uses the default selected adapter –
<pre><code>\Souptik\AllPathMessaging\SMS\send( [ '+xxxxxxxxxxxx' ], 'Yay its working!' );
</code></pre>
<h3>Creating your own adapter 🛠️</h3>
Here comes the cool part fellow developers! 💻
Tip: I have provided a dummy adapter for each service at <code>inc/<service>/adapters/dummy/</code>.
Consider that as the starting point and let’s understand what each file does.
<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>. Rest of the functions and properties are self-explanatory! 😉</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>
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. 
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). 
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.
<h4>AWS SES</h4>
This plugin connect’s to AWS SES’s API to send emails through AWS SES. 
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). 
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.
<h4>Mailgun</h4>
This plugin connect’s to Mailgun’s API to send emails through Mailgun. 
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). 
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.
<h4>Telesign</h4>
This plugin connect’s to Telesign’s API to send SMS through Telesign. 
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. 
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.
<h4>Twilio</h4>
This plugin connect’s to Twilio’s API to send SMS through Twilio. 
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. 
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.

All Path Messaging

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

Ivijan-Stefan Stipic

INFINITUM FORM

This FCM Plugin for WordPress is designed to simplify the integration of push notifications to all Android and iOS devices. With ease of use in mind, here’s what you can achieve:
<ol>
<li>
Easy Integration:
<ul>
<li>Installation: Simply install the plugin.</li>
<li>Configuration: Enter your Firebase Server (API) key, generate a site key, and select the post types for notifications.</li>
<li>Compatibility: Works with both Android and iOS devices and the latest version of WordPress.</li>
</ul>
</li>
<li>
REST API Endpoints for Device Management:
<ul>
<li>Subscribe Device: Register devices when the mobile application is launched.</li>
<li>Unsubscribe Device: Deregister devices when the application is deleted.</li>
<li>Example: Use the provided endpoints with parameters like <code>rest_api_key</code>, <code>device_uuid</code>, <code>device_token</code>, etc., to manage subscriptions.</li>
</ul>
</li>
<li>
Customizable Notifications:
<ul>
<li>Categories: Register devices under specific categories. If a category doesn’t exist, it’ll be created automatically.</li>
<li>Content Types: Select specific post types for triggering notifications.</li>
</ul>
</li>
<li>
Open Source & Free: Modify and use without any cost.
</li>
</ol>
Make sure to have a Firebase project and your Firebase Server (API) key before using the plugin. Don’t miss out on important updates, try our FCM push notification plugin today!
<h3>REST API Endpoints</h3>
<h3>Subscribe Device</h3>
<pre><code>https://example.domain/wp-json/fcm/pn/subscribe
</code></pre>
Parameters: 
– <code>rest_api_key</code> (required): Unique site key from plugin settings. 
– <code>device_uuid</code> (required): Device’s unique ID. 
– <code>device_token</code> (required): Device’s token. 
– <code>subscription</code> (required): Category name for device registration. 
– <code>device_name</code> (optional): Name of the device. 
– <code>os_version</code> (optional): Operating system version.
Returns JSON:
<pre><code>{
 "error": false,
 "message": "Device token registered",
 "subscription_id": 123
}
</code></pre>
Unsubscribe device:
<pre><code>https://example.domain/wp-json/fcm/pn/unsubscribe
</code></pre>
Parameters:
<ul>
<li><code>rest_api_key</code> (required): Unique site key from plugin settings.</li>
<li><code>device_uuid</code> (required): Device’s unique ID.</li>
</ul>
Returns JSON:
<pre><code>{
 "error": false,
 "message": "The device token was successfully removed"
}
</code></pre>
This plugin is available as open-source and free of charge, allowing seamless integration with any WordPress setup and offering the flexibility for customization to meet specific needs.1. Preparation for Use: 
 – Prior to activating the plugin, it’s essential to establish a Firebase project and obtain the corresponding Firebase Server (API) key. This setup links your WordPress site to Firebase, enabling the key functionalities of the plugin.
<ol>
<li>
Unique Site Key Requirement:
<ul>
<li>Upon installing the plugin, you’ll need to access the plugin settings page to generate a unique site key. This key is crucial for the identification and security of your particular WordPress installation.</li>
</ul>
</li>
<li>
Content-Type Selection for Notifications:
<ul>
<li>The plugin grants you the flexibility to choose specific types of posts for sending notifications. This allows for a tailored communication strategy, ensuring that users only receive alerts relevant to their interests.</li>
</ul>
</li>
<li>
Device Management via REST API Endpoints:
<ul>
<li>The plugin utilizes REST API endpoints to manage device registration and deregistration. Your mobile application must be configured to interact with these endpoints, enabling accurate control over the device subscriptions.</li>
</ul>
</li>
<li>
Cross-Platform Compatibility:
<ul>
<li>Designed to work seamlessly with both Android and iOS devices, this plugin ensures that you can reach your audience regardless of their preferred platform.</li>
</ul>
</li>
<li>
Category-Specific Notification Delivery:
<ul>
<li>The plugin facilitates sending push notifications to all registered devices for a particular post category. This targeted approach enhances engagement by delivering content-specific alerts.</li>
</ul>
</li>
<li>
Registration Verification Before Notification:
<ul>
<li>Prior to sending any notifications, the plugin verifies the device’s registration status. This step maintains notification accuracy and avoids sending to inactive or irrelevant devices.</li>
</ul>
</li>
<li>
Compatibility with Latest WordPress Version:
<ul>
<li>While the plugin aligns with the most recent WordPress version, it’s advisable to check for compatibility to ensure a smooth integration within your specific WordPress environment.</li>
</ul>
</li>
<li>
Customizable Open-Source Software:
<ul>
<li>Embracing an open-source model, the plugin’s code can be adapted to meet individual requirements. This encourages not only personalized use but also potential community contributions and collaboration.</li>
</ul>
</li>
</ol>

Push Notification FCM

Introducing a seamless framework plugin for Firebase Cloud Messaging (FCM) for Android and iOS developers, to send push notifications globally.

All Path Messaging vs Push Notification FCM