sailthru / sailthru-magento2-extension

sailthru/sailthru-magento2-extension

Sailthru Module for Magento

magento2-module 2.4.6-2.4.9 Compatible Based on composer requirements only QA: failed

MageSail

Sailthru Magento 2 Extension

Installation Instructions

  1. Get the module via composer composer require sailthru/sailthru-magento2-extension
  2. Enable the module bin/magento module:enable Sailthru_MageSail
  3. Upgrade the database bin/magento setup:upgrade (Depending on Magento mode, you may need to run magento setup:di:compile)
  4. Go to Magento Admin > Stores > Configuration > Sailthru to configure. Visit the Sailthru Documentation Site for setup documentation.

Note: If sync'ing variant products with no visible individual URL, you should enable "Preserve Fragments" in Sailthru here.

Javascript Setup

The Sailthru MageSail module comes ready to use Sailthru's new PersonalizeJs javascript. To add page-tracking and gather onsite data like pageviews and clicks:

  1. Add your Customer ID (found here) to vendor/sailthru/sailthru-magento2-extension/view/frontend/web/spm.js

Please contact Sailthru to learn more about and enable Site Personalization Manager.

To define transactional template to be overriden by Sailthru

Declare new transactional email template in ./etc/template_config.xml file that can be created within any module.
Each template definition in ./etc/template_config.xml has four required parameters that are defined in ./etc/template_list.xsd file.
Required parameters are:

  1. id - transactional email template identifier in Magento 2
  2. name - template title which will be displayed in Admin Panel -> Stores -> Configuration -> Sailthru -> Transactionals -> General Transactionals dropdown list
  3. custom_template_source - Core Config Path to native Magento 2 transactional email template ID value. Is utilized when custom email template overrides default Magento 2 email template
  4. sort_order - template sort order

After updating the ./etc/template_config.xml file run php bin/magento cache:clean config to clean Config cache.
To extend or change structure of a transactional email templates override config file use ./etc/template_list.xsd file.

Use Magento Email Queue

Sailthru Magento 2 extension utilizes standard Magento queueing functionality.

  1. Go to Admin > Stores > Configuration > Sailthru > Messaging > Advanced
  2. Set flag "Use Magento Email Queue" to Yes and save configuration
  3. Make sure Magento cron is setup and running
  4. To test Sailthru messages queue consumer execute:
$ php bin/magento queue:consumers:start sailthru.email.send.consumer.db
OR
$ php bin/magento queue:consumers:start sailthru.email.send.consumer.amqp

RabbitMQ integration

Instead of standard database based queue broker RabbitMQ can be used

Refer to Magento Guide: RabittMQ Setup

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Released
2.5.8 stable Fail 2026-03-16 12:16:44
2.5.4 stable Not tested 2024-11-15 10:24:59
2.5.3 stable Not tested 2024-09-19 14:18:09
2.5.2 stable Not tested 2024-09-13 15:42:57
2.5.1 stable Not tested 2024-08-16 13:26:26
2.5.0 stable Not tested 2024-08-14 12:00:41
2.4.4 stable Not tested 2024-08-05 08:30:42
2.4.2 stable Not tested 2024-05-06 09:46:06
2.4.1 stable Not tested 2023-10-25 10:41:21
2.4.0 stable Not tested 2023-01-12 21:06:08
2.3.1 stable Not tested 2022-03-24 05:52:36
2.3.0 stable Not tested 2022-03-11 17:31:38
2.2.4 stable Not tested 2022-03-02 04:37:47
2.2.3 stable Not tested 2022-02-18 00:26:01
2.2.2 stable Not tested 2022-02-16 01:28:31
2.2.1 stable Not tested 2021-10-12 20:23:47
2.2.0 stable Not tested 2021-03-30 21:22:53
2.1.0 stable Not tested 2021-03-30 20:49:14
2.0.4 stable Not tested 2020-12-17 20:02:49
2.0.3 stable Not tested 2020-07-13 22:16:42
2.0.2 stable Not tested 2020-06-29 21:34:32
2.0.1 stable Not tested 2020-06-08 15:59:18
2.0.0 stable Not tested 2020-01-31 22:30:35
1.5.2 stable Not tested 2019-11-19 19:44:21
1.5.1 stable Not tested 2019-10-14 18:06:36
1.5.0 stable Not tested 2019-10-10 21:10:48
1.4.1 stable Not tested 2019-06-17 14:38:39
1.4.0 stable Not tested 2019-05-01 20:58:26
1.3.0 stable Not tested 2019-04-01 15:45:39
1.2.0 stable Not tested 2019-03-26 15:42:48
1.1.0 stable Not tested 2018-09-25 16:47:04
1.0.4 stable Not tested 2017-03-31 03:09:27
1.0.3 stable Not tested 2017-03-20 02:00:03
1.0.2 stable Not tested 2016-09-26 20:20:35
1.0.1 stable Not tested 2016-09-12 20:05:42
1.0.0 stable Not tested 2016-08-22 16:44:07

Requires 3

Package Constraint
magento/framework ^102.0 || ^103.0
php ~5.6.0|~7.0.0|~7.1.3|~7.2.0|~7.3.0|~7.4.0|~8.0
sailthru/sailthru-php5-client 1.2.4

Suggests 3

Package Reason
magento/module-catalog ^101.*
magento/module-customer ^100.1.*
magento/module-newsletter ^101.*
QA results
Tool Status Findings Summary
PHPCS Fail 29 29 errors (gating threshold: error-severity=10, ruleset: Magento2)
PHPStan Fail 130 130 errors (level 4, ruleset: phpstan + bitexpert/phpstan-magento)
Cpd Pass 0
Security Pass 0

No license declared

This package's composer.json doesn't declare a license, homepage, or authors. Check the source repository for terms of use.

Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.