Could there be a design flaw in the way files are stored ? about laravel-mail-editor HOT 16 CLOSED

Hi @salhdev,
Thanks for reporting this I will take this into consideration in the next updates,

Also, PRs are welcome 👍

Thanks again.

from laravel-mail-editor.

Its because of where the files are being stored. sorry about that. @keatwei Once we get my PR merged that would be fixed

from laravel-mail-editor.

@griffins ya.. if possible can put in resources/views/emails would be great
thx for your effort and package

from laravel-mail-editor.

For the second task there is PR #13 which should fix known issues preventing the package from being used in production

from laravel-mail-editor.

@griffins thanks for your PRs I will take a look at it tomorrow when I come back home.

Thanks again.

from laravel-mail-editor.

Exactly what i was wondering

from laravel-mail-editor.

Just found out about this package today from laravel news. I love it.
My only problem is the need to modify my database schema. I would love if the package could maintain its meta data in a json file instead of the db. Am willing to make a pr for the same

from laravel-mail-editor.

Am doing a PR for this issue, what do you think about the views existed in the default namespace instead of the maileclipse one?

from laravel-mail-editor.

Hi i did a PR for the first task. #11

from laravel-mail-editor.

after i do composer update, my existing template is not accessible

from laravel-mail-editor.

Also if you drop your database you will lose them

from laravel-mail-editor.

I already did that. Actually you can customize the folder you want

There is a new config for it.

like here

    'view' => [
        'dir' => resource_path('views/mail/'),
        'namespace' => 'mail'
    ],

from laravel-mail-editor.

Any word on a plan to make this easy to migrate into production?

from laravel-mail-editor.

Hello @dbfx, @salhdev, @keatwei

Please update to the latest version (currently 1.1.7), now you can override templates views using the following publish command:

php artisan vendor:publish --tag=maileclipse.templates

Also, there is no need for database migration, all templates metadata will be stored in a JSON file.

hope this helps,
Thanks

from laravel-mail-editor.

Great thank you! Sent a contribution to the project from Snapt!

from laravel-mail-editor.

@dbfx thank you so much, I appreciate it!

from laravel-mail-editor.