Download the PHP package dekalee/mailjet-bundle without Composer

On this page you can find all versions of the php package dekalee/mailjet-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package mailjet-bundle

Mailjet Bundle

Scrutinizer Code Quality Code Coverage Build Status Latest Stable Version Total Downloads License

Usage

This bundle provides a transport element to use SwiftMailer from the Symfony project to send mail using Mailjet.

Configuration

To configure the bundle, you will have to enter the api key, secret and default template id :

You will also have to modify the transport in the mailer configuration :

Extension

In mailjet, you can define your own template for the mail you send. It is possible to use different template for each mail you will send.

To perform this action, you will need to guess the template Id from the message being send.

Create a guesser

You should implement the class : Dekalee\MailjetBundle\Guesser\TemplateIdGuesserInterface

There are two methods inside :

Declare the service

Once your class is created, you should add the tag dekalee_mailjet.guesser.template_id.strategy to your service definition

Campaign management

Affiliate a user to a campaign

To affiliate a contact to a campaign, you should use the ContactListSubscriber class, declared under the dekalee_mailet.subscriber.contact_list key in the container:

The template used for sending personnal emails to the contact from this list would be able to use the variable content_CampaignName and subject_CampaignName.

Unsubscribe a user from a campaign

To affiliate a contact to a campaign, you should use the ContactListUnSubscriber class, declared under the dekalee_mailet.unsubscriber.contact_list key in the container:

Custom template

If you want to use a custom template from mailjet with some custom variables, there is a way to do it in the bundle:

If you send the mail throught mailjet, the template 1 will be used.

In your working environment, you will receive a mail with all the vars json encoded.

Debug

Since version 2.1.0, it is possible to use mailjet debug capabilities.

You can directly configure them in the config file:

The reporting_email parameter will be used to send the error report mail.

The force_deliver parameter will force the mail deliver even if there is a syntax issue.

Limitation

For the moment, the bundle does not supports the inline attachement functionnality from mailjet, but contributions are welcome :).

Warning for symfony4

When used with env parameters, the swiftmailer bundle automatically generates the transport by using a factory. To avoid this workflow, you shall not use env parameters to configure your swiftmailer installation.


All versions of mailjet-bundle with dependencies

PHP Build Version
Package Version
Requires php Version >=5.5
symfony/swiftmailer-bundle Version ^3.2
mailjet/mailjet-apiv3-php Version ~1.2
doctrine/orm Version ^2.3.6
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package dekalee/mailjet-bundle contains the following files

Loading the files please wait ....