61

Product support

Get help in the plugin support forum.

Categories

Send branded newsletter e-mails to subscribers. Easy to use and fully GDPR compliant this clever plugin gives you a number of options to offer prospective subscribers.

  1. Simple checkbox management for opting in subscribers to all or selected lists.
  2. Automatic email verification to confirm opt in.
  3. Visitor managed message categories if required.
  4. Admin choice for sending to all or selected lists.
  5. Messages can be created and saved for future broadcast.
  6. Unsubscribe link in every message sent.
Sign up to the newsletter.

Usage

  1. Create page for managing newsletter options by subscribers so that it has :email and :token variables (for example manage-newsletter with /manage-newsletter/:email/:token URL). Of course, those variables can be changed.
  2. Embed component NewsletterConfirm on exact one CMS page (Newsletter plugin will automatically look for a page that has the component and cache it for 10 minutes)
  3. Go to backend Newsletter -> Checkboxes and add checkboxes as your business requires
  4. Embed component NewsletterForm on the page you want to have form rendered on (landing page or just footer partial)

Do not forget to configure e-mail sending in your backend settings

Translations

The plugin supports translations for all elements (there are no hardcoded frontend contents) including AJAX responses and displayed errors.

Out of the box, there are only two languages:

  • pl - Polski
  • en - English

But of course, you can prepare your own translations.

E-mail templates

Out of the box, there are two e-mail templates you can to customize:

  • inibiz.newsletter::mail.subscription which is sent to those who want to become a subscriber
  • initbiz.newsletter::mail.message which is sent to subscribers

In subscription e-mail template you can use {{activationLink}} variable.

In message e-mail template you can use:

  • {{title}} - Title of message
  • {{content}} - Content of message
  • {{ newsletterLink }} - link for subscribers to sign out from newsletter

If you want, you can create your own e-mail template. While sending you just have to choose which one you want to use. The message e-mail template is just a default one.

1.1.4

Update tests for newest RainLab plugins

Oct 17, 2024

1.1.3

October 3.6 registerMailTemplates bugfix

Jun 04, 2024

1.1.2

Fix additional data and fillable

May 22, 2024

1.1.1

Hot fix, typo in lang

May 15, 2024

1.1.0

Add tags, extra fields to subscriber, indexes and more

May 15, 2024

1.0.15

Disable queues by default to keep legacy working

Apr 07, 2020

1.0.14

Add queue support, sending test e-mails and little cleanup

Apr 07, 2020

1.0.13

TinyInt fix

Sep 25, 2019

1.0.12

Nullable fix

Sep 24, 2019

1.0.11

DB engine added

Sep 11, 2018

1.0.10

Small type fix

Sep 11, 2018

1.0.9

Primary key name shortened

Sep 11, 2018

1.0.8

Creating and updating subscriber form backend

Aug 10, 2018

1.0.7

Minor fixes

Aug 09, 2018

1.0.6

Updated table initbiz_newsletter_checkboxes

Aug 09, 2018

1.0.5

Updated table initbiz_newsletter_checkboxes

Aug 09, 2018

1.0.4

Adding and removing checkboxes introduced

Aug 09, 2018

1.0.3

!!! Big changes in newsletter plugin. See upgrade guide before upgrading.

Aug 09, 2018

1.0.2

Error reponses using AJAX and some small fixes

Jul 05, 2016

1.0.1

First version of newsletter

Jan 25, 2016

1.0.2 -> 1.0.3

There were big changes introduced to newsletter here. Sorry it took so long to update.

The bad news is that while upgrading to version above 1.0.2 you have to be aware that agreements to optional checkbox all text in your previous checkboxes will be lost. So if you want to restore those agreements you have to make backup of data on your own, and than insert related models in initbiz_newsletter_checkbox_subscriber table using their ids.

The good news is that now the plugin is much more powerful than before and from now we are going to keep versions updating fully supported, so there will not be such bad news anymore :)

PostgreSQL

If you are using PostgreSQL than rename column sendTo to sendto before running update.