MailEclipse - Laravel Mailable Editor!

Overview

Laravel Mail Editor (Aka MailEclipse)



MailEclipse is a mailable editor package for your Laravel applications to create and manage mailables using a web UI. You can use this package to develop mailables without using the command line, and edit templates associated with mailables using a WYSIWYG editor, among other features.

WORK IN PROGRESS

Please note that this package is still under active development. We encourage everyone to try it and give feedback.

Features

  • Create mailables without using command line.
  • Preview/Edit all your mailables at a single place.
  • Templates (more than 20+ ready to use email templates).
  • WYSIWYG Email HTML/Markdown editor.
  • Suitable for laravel beginners.
  • Send Test mails
  • Testing mails with fake data
  • and many more... (promise).

Requirements

  • Laravel 8.

For Laravel 5.6 to 7 support please see version v2.2 branch

Installation

Via Composer

$ composer require qoraiche/laravel-mail-editor

The package will automatically register itself.

Publish configuration file and public assets:

php artisan laravel-mail-editor:install

Documentation

!!NOTE!! Maileclipse website is currently down, please check this youtube video (from author) for usage:

https://www.youtube.com/watch?v=QFgEGNBY3FI&t=135s

Documentation for Maileclipse can be found on the Official website.

Community

You can reach us at:

Change log

Please see the changelog for more information on what has changed recently.

Security

If you discover any security related issues, please email author email [email protected] instead of using the issue tracker.

License

MIT license. Please see the license file for more information.

Screenshots

maileclipse-new-mailable

maileclipse-templates

maileclipse-templates-create

TODO

Contributions are welcome

  • Frontend enhancement (jquery to vue.js).
  • Add more email templates (HTML/Markdown).
  • Expand documentation pages.

Credits

Donate ❤️

If you benefit from and/or like using MailEclipse then please help drive the future development of the project by

Donors list:

  1. conschneider.de - (20,00 $) - Thank You! - 3 November 2020
  2. Emprovise - (20,00 $) - You did a great job on MailEclipse! Thank you for providing this to everyone for free. I look forward to watching your project grow! Thanks Again, James S. - 19 December 2019
  3. Idearia Web Agency - (40,00 €) - Keep up the good work! - 19 June 2019
  4. Snapt Systems Ltd - (100,00 $ USD) - Being used by one of our teams at Snapt! - 11 April 2019
  5. Corr Ex - (2,00 $ USD) - 28 March 2019
  6. WebArt Design - (10,00 $ USD) - Donation made with love by BuiltByPanda. com from Australia who support developers and their excellent work - 28 March 2019
  7. Flavius Borlovan (6,99 $ USD) - #teamcookie says HELLOO 🥳😉 Thanks for this really helpful Package (MailEclipse) bro. 😉💪🏽 - 12 March 2019
  8. Maik Kasper - (6,99 $ USD) - We {teamcookie:github. com/flavius-constantin} 💥 love to support good developers and their awesome work! 🌪🔥 - 13 March 2019

Sponsors

Comments
  • Trying to get property X of non-object each mailable, even though these work when running in the app

    Trying to get property X of non-object each mailable, even though these work when running in the app

    I have just installed the package in the hope we can use this, but looks like we can't.

    Every mailable that as something on it, (shown below) doesn't work

    Screenshot 2020-12-10 at 15 28 27 Screenshot 2020-12-10 at 15 28 36

    When having a constructor and passing info down even if it's queued or not the mailable doesn't render, I've found this with a few of my mailables, however these work as normal when sending and queueing up.

    Laravel Application: 7

    Maileclipse package version: 2.2

    Screenshots If applicable, add screenshots to help explain your problem.

    bug V2 
    opened by lstables 46
  • [Constructor error] Fatal error when using package

    [Constructor error] Fatal error when using package

    First off; looks pretty awesome. I wanted to give it a run in my application (which has a lot of mailables), but straight away I get an error when I visit /maileclipse:

    Too few arguments to function App\Mail\MailClass::__construct(), 0 passed in /Users/****/Workspace/****/vendor/qoraiche/laravel-mail-editor/src/mailEclipse.php on line 548 and at least 2 expected
    

    The constructor of this class has 3 arguments available:

        public function __construct($var1,$var2, $var3 = null)
        {
          
        }
    

    I would debug it myself and PR it if I had the time. Still thanks for such a great package 👍

    bug Good Issue 
    opened by Cannonb4ll 28
  • Trying to get property 'fullname' of non-object

    Trying to get property 'fullname' of non-object

    I have seen that similar issues have been already submitted & resolved, but I was not able to find a clear explanation what I have to do in order to fix this issue. I have MailEclipse version 1.3 installed
    There is a ProductCreated mailable & product-created.blade.php markdown template. In that template file I have the following line:

    New product "{{ $product->title }}" was created by user: {{ $product->user->fullname }}
    

    Mailable class:

    class ProductCreated extends Mailable
    {
        use Queueable, SerializesModels;
        /**
         * @var User
         */
        public $user;
        /**
         * @var Product
         */
        public $product;
    
        /**
         * Create a new message instance.
         *
         * @param User $user
         * @param Product $product
         */
        public function __construct(User $user, Product $product)
        {
            $this->user = $user;
            $this->product = $product;
        }
    
        /**
         * Build the message.
         *
         * @return $this
         */
        public function build()
        {
            return $this->markdown('emails.product-created');
        }
    }
    

    Please assist. Thanks.

    bug Good Issue V2 V3 
    opened by 4unkur 17
  • Could there be a design flaw in the way files are stored ?

    Could there be a design flaw in the way files are stored ?

    Hi again, The templates are stored in : vendor/qoraiche/laravel-mail-editor/resources/views/templates/ where vendor/* is ignored in git => So the result of that is that all your dev and changes in the templates will not be taken in the testing nor production environment ! And also template data is stored in a data table which is also not taken in the git. Why not create a Templates directory within the app/Mail directory and store it there ?

    enhancement 
    opened by salhdev 16
  • Uncaught SyntaxError:

    Uncaught SyntaxError: "" string literal contains an unescaped line break

    Describe the bug

    I have a mailable that uses the User Model, and some other Models. When I try to edit the mailable I have this error in the console: "Uncaught SyntaxError: "" string literal contains an unescaped line break" After I remove the user model from the mailable the error disappears.

    Laravel Version:

    8.73.1

    MailEclipse package version:

    v3.5.0

    Screenshots (if applicable)

    imagen

    bug WIP Reviewed 
    opened by hmreumann 14
  • fix: compatible way to call the method on mailable

    fix: compatible way to call the method on mailable

    Description

    Adds a method exists check to the function of the buildMailable data method to check which method exists on the Mailable.

    Related Issue

    #218

    Motivation and Context

    This is to make the preview functionality work with Laravel 9

    How Has This Been Tested?

    Screenshots (if appropriate):

    Types of changes

    • [x] Bug fix (non-breaking change which fixes an issue)
    • [ ] New feature (non-breaking change which adds functionality)
    • [ ] Breaking change (fix or feature that would cause existing functionality to change)

    Checklist:

    • [x] My code follows the code style of this project.
    • [x] My change requires a change to the documentation.
    • [x] I have updated the documentation accordingly.
    • [x] I have read the CONTRIBUTING document.
    • [x] I have added tests to cover my changes.
    WIP V3 Review Needed v4 
    opened by ReeceM 12
  • Endless User Email Verification

    Endless User Email Verification

    Describe the bug

    After I added the User $user model to the constructor of a Markdown Email, when I refresh the page it starts sending Email Verifications.

    Reproduction steps

    Steps to reproduce the behavior:

    1. Create a Mailable.
    2. Added a User $user to the constructor.
    3. Click Mailables. And it starts sending Verification Emails.

    Laravel Version:

    Laravel Framework 8.57.0

    MailEclipse package version:

    versions : * v3.4.1


    I have 101 users in my DB.

    bug Good Issue V3 Reviewed 
    opened by hmreumann 12
  • Undefined index: string

    Undefined index: string

    Describe the bug I'm getting the follow error after update to 2.0.6 version and PHP to 7.4.7

    To Reproduce I went to http://127.0.0.1:8000/maileclipse/mailables and get the follow error

    Laravel Application: 5.8

    Maileclipse package version: 2.0.6

    Screenshots image

    bug Good Issue 
    opened by mateusgalasso 12
  • Pretember for Hacktoberfest - Please Read First

    Pretember for Hacktoberfest - Please Read First

    Contributors

    It is awesome that you would like to help with the MaileEclipse package, there will be issues tagged as Hacktoberfest. Please read this brief list of things about contributing on the repo

    Please have a read of this, https://github.com/Qoraiche/laravel-mail-editor/blob/master/contributing.md

    • If you would like to work on the issues that are available, please claim them with a comment and also ask for any assistance if you are unsure about something.
    • If you are unable to complete the PR, or would like someone else to handle it, please mention it so in the comments.
    • Please keep community standards in the messages and commits.
    • One feature per PR to keep it in scope, if you have different things, you can open a new PR for that different feature

    Original Message below

    Hi @Qoraiche,

    As Hacktoberfest is around the corner again this year, and with September it is set as a time for preparing the repos for getting ready for it.

    I was wondering if we can start going through some of the issues on the repo and seeing which ones can be marked for those who would like to get involved in Hacktoberfest and like to support the packages development.

    We could have a poll even of some issues that could be tagged and refined to what can be sorted.

    This would be nice as there are some simple issues and some other things that contributors could add, and possibly some of the previous contributors.

    There is the discord channel if there are newcomers to contributing and would like some help from the community https://discord.gg/hacktoberfest

    I think we could have some comments tagged into this issue with links to the issues that some think could be tagged as hacktoberfest

    opened by ReeceM 10
  • Error: Symfony \ Component \ HttpKernel \ Exception \ HttpException No message

    Error: Symfony \ Component \ HttpKernel \ Exception \ HttpException No message

    Going to http://localhost:8000/maileclipse/mailables leads to the following error.

    image

    I have followed all the install instructions, so seems like this is a bug? I am using version 2.2, on Laravel 5.6.40

    bug Review Needed 
    opened by rxng 9
  • PSR Classname compliance

    PSR Classname compliance

    It would be good to get all the classnames and namespaces to make use of PSR standards so that the compose autoload system and classmaps all function correctly and as expected.

    There are a few classes and files that have lowercase first parts of the names.

    This is a good issue for new comers helping on the repo 👍

    enhancement WIP good first issue 
    opened by ReeceM 9
  • No template associated

    No template associated

    Describe the bug

    When trying to open a a Mail template a error comes up with no template found, downgrade to version 4.0.3 and the template loads up fine.

    markdown.template wont load in 4.0.4, also the footer of the application still shows 4.0.3 on 4.0.4

    Reproduction steps

    Steps to reproduce the behavior:

    1. Go to 'Mailables'
    2. Click on 'a user made mailable'
    3. See error

    Laravel Version:

    9.44.0

    MailEclipse package version:

    4.0.4

    Screenshots (if applicable)

    https://i.imgur.com/vvKeixx.jpg


    Additional information Mailables are in `qpp\mail\` Templates are in `resources\views\markdown\`
    bug Review Needed 
    opened by dualznz 3
  • Markdown Button save >

    Markdown Button save >

    Describe the bug

    The markdown save wrong

    Reproduction steps

    Steps to reproduce the behavior:

    1. Edit an mailable
    2. add Button and click update
    3. Click on Preview

    Laravel Version:

    Laravel Framework 8.83.19

    MailEclipse package version:

    versions : * v3.5.3

    Screenshots (if applicable)

    image

    bug 
    opened by mtmSchoenberger 21
  • axios.post is not a function

    axios.post is not a function

    Describe the bug

    Hii, I installed the maileclipse package with laravel 9. I'm not able to create any new mailable class or template. whenever I try to create a mailable class or template and submit the form**, the same error occurred "axios.post is not a function"** can you please help me with this issue?

    only mailables listing & templates listing is working, not able to add any new template or mailable class.

    Laravel Version:

    Laravel 9

    Screenshots (if applicable)

    image

    image

    bug Review Needed 
    opened by RJonwal 2
  • MailEclipse drops Meilisearch/Laravel scout records

    MailEclipse drops Meilisearch/Laravel scout records

    Describe the bug

    Hi all,

    Installed MailEclipse last week now I noticed that is drops my Meilisearch/Laravel scout index files. Only loading MailEclipse drops the indexes to im 100% sure it has something to do with this.

    Any ideas?

    Reproduction steps

    Steps to reproduce the behavior:

    1. Go to /maileclipse
    2. View your Meilisearch/Laravel Scout index files, they are empty

    Laravel Version:

    8.77

    MailEclipse package version:

    v3.5.3

    bug Review Needed 
    opened by vanrijs 6
  • Return value error on template?

    Return value error on template?

    Qoraiche\MailEclipse\MailEclipse::getTemplate(): Return value must be of type ?Illuminate\Support\Collection, none returned

    Reproduction steps

    Steps to reproduce the behavior:

    1. Go to create template.
    2. Go through steps to create template, name/description - get Axios 500 error . . . assuming it didn't create
    3. Click on template that it thinks was created to edit and get error message.

    Laravel Version:

    Laravel 9.17.0

    PHP PHP 8.1.6

    MailEclipse package version:

    source : [git] https://github.com/Qoraiche/laravel-mail-editor.git 085d431c8a31d688f3097dd46c8df523108bc2f7

    Screenshots (if applicable)

    bug Review Needed 
    opened by HeartlandTechie 6
  • Template preview not working?

    Template preview not working?

    Describe the bug

    Maybe I am missing someting, but I think the template preview is not working when you go and use the preview mode when editing a template directly (not going through a mailable). When I click the preview button it just shows a white black page in the text editor.

    url: https://laravel.test/maileclipse/templates/edit/yourtemplate.

    stacktrace:

    [2022-06-21 11:27:37] local.ERROR: Method Qoraiche\MailEclipse\Http\Controllers\TemplatesController::previewTemplateMarkdownView does not exist. {"userId":2,"exception":"[object] (BadMethodCallException(code: 0): Method Qoraiche\\MailEclipse\\Http\\Controllers\\TemplatesController::previewTemplateMarkdownView does not exist. at /Users/jorn/Sites/**/vendor/laravel/framework/src/Illuminate/Routing/Controller.php:68)
    [stacktrace]
    #0 /Users/jorn/Sites/**/vendor/laravel/framework/src/Illuminate/Routing/Controller.php(54): Illuminate\\Routing\\Controller->__call('previewTemplate...', Array)
    #1 /Users/jorn/Sites/**/vendor/laravel/framework/src/Illuminate/Routing/ControllerDispatcher.php(45): Illuminate\\Routing\\Controller->callAction('previewTemplate...', Array)
    #2 /Users/jorn/Sites/**/vendor/laravel/framework/src/Illuminate/Routing/Route.php(261): Illuminate\\Routing\\ControllerDispatcher->dispatch(Object(Illuminate\\Routing\\Route), Object(Qoraiche\\MailEclipse\\Http\\Controllers\\TemplatesController), 'previewTemplate...')
    #3 /Users/jorn/Sites/**/vendor/laravel/framework/src/Illuminate/Routing/Route.php(204): Illuminate\\Routing\\Route->runController()
    #4 /Users/jorn/Sites/**/vendor/laravel/framework/src/Illuminate/Routing/Router.php(725): Illuminate\\Routing\\Route->run()
    #5 /Users/jorn/Sites/**/vendor/laravel/framework/src/Illuminate/Pipeline/Pipeline.php(141): Illuminate\\Routing\\Router->Illuminate\\Routing\\{closure}(Object(Illuminate\\Http\\Request))
    

    Reproduction steps

    Steps to reproduce the behavior:

    1. Go to Templates
    2. Add template
    3. Save template
    4. Click preview template

    Laravel Version:

    v9.17.0

    MailEclipse package version:

    v4.0.3

    Screenshots (if applicable)

    afbeelding

    bug Reviewed v4 
    opened by jornwildenbeest 9
Releases(v4.0.4)
  • v4.0.4(Nov 21, 2022)

    What's Changed

    • Fix/route errors by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/212
    • fix: compatible way to call the method on mailable by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/219

    Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.3...v4.0.4

    Source code(tar.gz)
    Source code(zip)
  • v4.0.3(Feb 15, 2022)

    What's Changed

    • Fix for issue #199, syntax error by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/200
    • Update versions for latest fix by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/201

    Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.2...v4.0.3

    Thank you to @AliKHODR

    Source code(tar.gz)
    Source code(zip)
  • v3.5.3(Feb 15, 2022)

    What's Changed

    • Update mailables.blade.php by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/202

    Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v3.5.2...v3.5.3

    Source code(tar.gz)
    Source code(zip)
  • v4.0.2(Feb 11, 2022)

    With this addition, please make use of the updated config values in config/maileclipse.php. You need to add the following

        /*
        |--------------------------------------------------------------------------
        | Display Mailable Subject
        |--------------------------------------------------------------------------
        |
        | Set to true this will display the subject of the Mailable instead of Class Name.
        | When the config setting is false the namespace/class name is shown
        | options: true / false
        |
        */
        'display_as_subject' => true,
    

    What's Changed

    • Merge Master into v3.x branch in https://github.com/Qoraiche/laravel-mail-editor/pull/193
    • [3.x] Feature/change table names issue 79 in https://github.com/Qoraiche/laravel-mail-editor/pull/194
    • Merge v3 updates in https://github.com/Qoraiche/laravel-mail-editor/pull/198

    Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.1...v4.0.2

    Source code(tar.gz)
    Source code(zip)
  • v3.5.2(Feb 11, 2022)

    Added

    • Adds the subject of the email client to the table instead of the namespace. See Issue #79, PR #194

    Please add the following to the config/maileclipse.php file to be able to toggle the settings for this added feature.

        /*
        |--------------------------------------------------------------------------
        | Display Mailable Subject
        |--------------------------------------------------------------------------
        |
        | Set to true this will display the subject of the Mailable instead of Class Name.
        | When the config setting is false the namespace/class name is shown
        | options: true / false
        |
        */
        'display_as_subject' => true,
    

    Fix

    • Correct custom Mailable directory usage from config, see PR #190 @Bhagyrajaj

    Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v3.5.1...v3.5.2

    Source code(tar.gz)
    Source code(zip)
  • v4.0.1(Feb 11, 2022)

    This adds improved feedback about the usage of factories when the option is enabled in the config file and none are found for a model.

    What's Changed (Auto-generated)

    • Refac/improve error handling and feedback by @ReeceM in https://github.com/Qoraiche/laravel-mail-editor/pull/196

    Full Changelog: https://github.com/Qoraiche/laravel-mail-editor/compare/v4.0.0...v4.0.1

    Source code(tar.gz)
    Source code(zip)
  • v4.0.0(Feb 8, 2022)

  • v3.5.1(Dec 4, 2021)

  • v3.5.0(Sep 28, 2021)

    Version 3.5.0

    Changes

    • The structure of the config file for the relations section. It will fallback to loading one by default. This is a change that is accounted for and defaults if it uses the old config structure. It is recommended that you update to the new one for this entry in the configuration file.

    New Structure:

    
        /*
        |--------------------------------------------------------------------------
        | Relationship loading.
        |--------------------------------------------------------------------------
        |
        | This configures how deep the package will search an load relations.
        | If you set this to 0, relations will not be loaded.
        |
    +    | relation_depth: off = 0, min = 1, max = 5
    +    | model: this is the model to use to exclude methods when searching.
        |
        | N.B. This does not configure how many many relationship types are loaded.
        */
    -    'relation_depth' => env('MAILECLIPSE_RELATION_DEPTH', 2),
    +    'relations' => [
    +        'relation_depth' => env('MAILECLIPSE_RELATION_DEPTH', 2),
    +        'model' => \Illuminate\Foundation\Auth\User::class,
    +    ],
    
    

    Use this to copy to the new file:

        /*
        |--------------------------------------------------------------------------
        | Relationship loading.
        |--------------------------------------------------------------------------
        |
        | This configures how deep the package will search an load relations.
        | If you set this to 0, relations will not be loaded.
        |
        | relation_depth: off = 0, min = 1, max = 5
        | model: this is the model to use to exclude methods when searching.
        |
        | N.B. This does not configure how many many relationship types are loaded.
        */
        'relations' => [
            'relation_depth' => env('MAILECLIPSE_RELATION_DEPTH', 2),
            'model' => \Illuminate\Foundation\Auth\User::class,
        ],
    

    Fixes

    Source code(tar.gz)
    Source code(zip)
  • v3.4.2(Sep 27, 2021)

  • v3.4.1(Jul 18, 2021)

  • v3.4.0(Jul 16, 2021)

    This release will resolve the issue that has been brought up in issue #63 where relations weren't being loaded and affected the calling of relations inside emails or mailables.

    Fixes

    • Fixes issue #63

    Addition

    • Discovery and loading of relations that have factories
    • New config for depth of searching see below for new addition

    new config value

        /*
        |--------------------------------------------------------------------------
        | Relationship loading depth
        |--------------------------------------------------------------------------
        |
        | This configures how deep the package will search an load relations.
        | If you set this to 0, relations will not be loaded.
        |
        | off = 0, min = 1, max = 5
        |
        | N.B. This does not configure how many many relationship types are loaded.
        */
    
        'relation_depth' => env('MAILECLIPSE_RELATION_DEPTH', 2),
    
    Source code(tar.gz)
    Source code(zip)
  • v2.3.0(Jul 16, 2021)

    This release will resolve the issue that has been brought up in issue #63 where relations weren't being loaded and affected the calling of relations inside emails or mailables.

    Fixes

    • Fixes issue #63

    Addition

    • Discovery and loading of relations that have factories
    • New config for depth of searching see below for new addition

    new config value

        /*
        |--------------------------------------------------------------------------
        | Relationship loading depth
        |--------------------------------------------------------------------------
        |
        | This configures how deep the package will search an load relations.
        | If you set this to 0, relations will not be loaded.
        |
        | off = 0, min = 1, max = 5
        |
        | N.B. This does not configure how many many relationship types are loaded.
        */
    
        'relation_depth' => env('MAILECLIPSE_RELATION_DEPTH', 2),
    
    Source code(tar.gz)
    Source code(zip)
  • v2.2.5(May 10, 2021)

    Small patch release to add some feedback.

    Fixes

    • This adds a error message to the check for allowed environments from the Maileclispe config #152

    Chore

    • Made the return type described in the docblock correct. see 8b21ed764f7653e6c5dd1f5a9f82d19160bb4728 (#152)
    Source code(tar.gz)
    Source code(zip)
  • v2.2.4(Dec 10, 2020)

  • v2.2.3(Dec 10, 2020)

  • v3.2.3(Dec 1, 2020)

    This is a patch release to fix an issue with the viewDataInspect method on the MailEclipse class

    Fixes

    • Return value of MailEclipse::viewDataInspect() was not returning the correct values. see #137 PR #138.
    Source code(tar.gz)
    Source code(zip)
  • v3.2.2(Nov 17, 2020)

  • v3.2.1(Oct 23, 2020)

    Feature

    • Add the ability to send test mail with fake factory model data.

    Fixes

    • Fix model factories builder not loaded in laravel 8
    • Formatting
    Source code(tar.gz)
    Source code(zip)
  • v3.1.0(Oct 5, 2020)

  • v3.0.1(Oct 5, 2020)

  • v2.2.2(Oct 2, 2020)

    Version 2.2.2

    This is a patch release of the package for a PSR-4 warning

    Fix

    • The namespace and the file structure of the console command were corrected to PSR-4 standards thanks @ivebe, see #115
    Source code(tar.gz)
    Source code(zip)
  • v2.2.1(Sep 30, 2020)

    Patch Release.

    Fixes

    • Fixes the string error that happens when the constructor params have a string type hint, issue #103
      • see https://github.com/Qoraiche/laravel-mail-editor/pull/113
    Source code(tar.gz)
    Source code(zip)
  • v3.0.0(Sep 22, 2020)

    Laravel 8 Support release

    Addition

    • The package now has an install command php artisan laravel-mail-editor:install see #111

    Changes

    • Supports only Laravel v8
    • PSR Classnames #112, thank you @yogendra-revanna

    Potential Breaking Change

    The name spaces of the package now use PSR classname standards, if you were referencing them before in an application, please update them to reflect everything correctly.

    Source code(tar.gz)
    Source code(zip)
  • v2.2.0(Sep 22, 2020)

    Version 2.2.0

    IMPORTANT: Version 2.2.0 will only support Laravel versions 5, 6 and 7 for future releases.

    Addition

    • Revert Laravel 8 support
    • Console command for installing assets see PR #111, credit: @yogendra-revanna
    Source code(tar.gz)
    Source code(zip)
  • v2.1.0(Sep 14, 2020)

  • v2.1.0-beta(Sep 10, 2020)

  • v2.0.6(May 28, 2020)

  • v2.0.4(May 25, 2020)

  • v2.0.3(May 6, 2020)

Owner
Yassine Qoraiche
Se7enUp
Yassine Qoraiche
Laravel IMAP is an easy way to integrate both the native php-imap module and an extended custom imap protocol into your Laravel app.

Laravel IMAP is an easy way to integrate both the native php-imap module and an extended custom imap protocol into your Laravel app. This enables your app to not only respond to new emails but also allows it to read and parse existing mails and much more.

null 530 Jan 6, 2023
Laravel Mail Catcher Driver

Laravel Mail Catcher Driver This package include a new mailbase driver which will catch all the sent emails and save it to the database. It then expos

Tauqeer Liaqat 94 Aug 30, 2022
Offer an online version of your Laravel emails to users.

This is was a collaborative project with Ryan Chandler. Please consider supporting him for the hard work he put into this package! Help support the ma

Sam Carré 251 Dec 25, 2022
An AngularJS / Laravel app - Keyword Based Email forwarder | read/write emails through IMAP

@MailTree Simple mail forwarder. Based on the specific email body/subject keywords forward mails to the list of predefined users. Install Imap Install

Dren Kajmakchi 4 Aug 21, 2018
Store outgoing emails in Laravel

Record and view all sent emails Watch a video walkthrough https://www.youtube.com/watch?v=Oj_OF5n4l4k&feature=youtu.be Documentation and install instr

David Carr 203 Dec 15, 2022
Mail Web is a Laravel package which catches emails locally for debugging

Mail Web is a Laravel package which catches emails locally for debugging Installation Use the package manager composer to install Mail Web. composer r

Appoly 64 Dec 24, 2022
Disposable email address validator for Laravel

Laravel Disposable Email Adds a validator to Laravel for checking whether a given email address isn't originating from disposable email services such

null 332 Dec 29, 2022
Send beautiful HTML emails with Laravel

Beautymail for Laravel Beautymail makes it super easy to send beautiful responsive HTML emails. It's made for things like: Welcome emails Password rem

null 1.1k Jan 2, 2023
A testing package for intercepting mail sent from Laravel

Laravel Mail Intercept A testing package for intercepting mail sent from Laravel This testing suite intercepts Laravel Mail just before they are sent

Kirschbaum Development Group, LLC 91 Oct 18, 2022
✉️ Laravel Mail Explorer

Mailbook Mailbook is a Laravel package that lets you easily inspect your mails without having to actually trigger it in your application. View demo In

Max Hoogenbosch 88 Dec 29, 2022
A Laravel package to check if you can send e-mail through a given mailserver in name of a given e-mail address

A Laravel package to check if you can send e-mail through a given mailserver in name of a given e-mail address Mail spf checker A Laravel package to c

Dieter Coopman 110 Dec 16, 2022
Laravel mailer which will catch all the sent emails and show them on an application view.

Laravel Web Mailer This package contains a web mailer which will catch all the sent emails. Then, you can view it visiting the route /web-inbox. The e

Creagia 54 Dec 16, 2022
Mandrill mail driver for Laravel for version 6+

Laravel Mandrill Driver This package re-enables Mandrill driver functionality using the Mail facade in Laravel 6+. To install the package in your proj

Eng Hasan Hajjar 2 Sep 30, 2022
Scaffold plugin for creating and managing Blocks, Block Patterns, Block Styles and Block Editor Sidebars in the WordPress Block Editor (aka Gutenberg).

WordPress Block Editor Scaffold This project is a template repo for developing WordPress Blocks, Block Patterns, Block Styles and Block Editor Sidebar

Rareview 6 Aug 2, 2022
A simple mailable trait and interface to export mails to a storage disk once being sent.

Laravel Mail Export This package can export any mail sent with Laravel's Mailable class to any desired filesystem disk and path as a .eml file. This c

Pod Point 80 Nov 6, 2022
Integrates the Trix Editor with Laravel. Inspired by the Action Text gem from Rails.

Integrates the Trix Editor with Laravel. Inspired by the Action Text gem from Rails. Installation You can install the package via composer: composer r

Tony Messias 267 Jan 4, 2023
JSON Editor for Laravel-admin

JSON Editor extension for laravel-admin This is a laravel-admin extension that integrates JSON Editor into laravel-admin. DEMO Login using admin/admin

Extensions for laravel-admin 27 Nov 5, 2022
Add better visible controls on Beaver Builder editor. Work by Matt Eastwood

Beaver Builder UI Enhancements Community Plugin by Matt Eastwood / Guy Barry / Didou Schol / Marleen Kiral Add extra styling when editing Beaver Build

Didou Schol 14 Feb 1, 2022
ICEcoder is a browser based code editor, which provides a modern approach to building websites

ICEcoder Code editor awesomeness ...in your browser ICEcoder is a browser based code editor, which provides a modern approach to building websites. By

ICEcoder 1.4k Dec 18, 2022
A web based file manager,web IDE / browser based code editor

KodExplorer Update to kodbox: https://github.com/kalcaddle/kodbox Download | Demo It is recommended to use a new design upgrade product:kodbox 该项目处于维护

warlee 5.8k Jan 3, 2023