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.

Mobile Builder

App Cheap

<p>Support push notification for mobile and the web app.</p>
<p><a href="https://codecanyon.net/item/cirilla-multipurpose-flutter-wordpress-app/31940668" rel="nofollow ugc">Demo app</a></p>
<h3>Push services support</h3>
<ul>
<li>Firebase HTTP V1</li>
<li>Firebase HTTP legacy</li>
<li>OneSignal</li>
<li>Debug</li>
</ul>
<h3>How does it work</h3>
<p>The Push Notification plugin is built with five part:</p>
<ul>
<li>Trigger: When WordPress action execution (Post saved, Order status changed …)</li>
<li>Recipients: One/ More recipients get the notification ( topic, registration ID, role, user, merge tag …)</li>
<li>Conditionals: Determine whether notification send</li>
<li>Action: The action when the user click to notification on device</li>
<li>Merge Tag: That is dynamic information in that context</li>
<li>String translation: Replace part of string on title and message</li>
</ul>
<h3>Plugin Features</h3>
<ul>
<li>Comment Post: Fires immediately after a comment is inserted into the database.</li>
<li>Post Type: Fires when a post is transitioned from one status to another.</li>
<li>Save Post: Fires once a post has been saved.</li>
<li>Order Status Changed: Fires when an order is transitioned from one status to another.</li>
<li>Product Status Changed: Fires when a product is transitioned from one status to another.</li>
<li>WCFM – Direct Messaging: Fires when vendor receive a message.</li>
<li>BuddyPress: Fires Messages message sent, Activity Posted Update, Friends Friendship Accepted, Friends Friendship Requested, Groups Posted Update, Groups Send Invites</li>
</ul>


Push notification for Mobile and Web app

Push notification for Android, iOS and the Web

All Path Messaging vs Push notification for Mobile and Web app