Masonite 1.3 to 1.4

Introduction
Masonite 1.4 brings several new features and a few new files. This is a very simple upgrade and most of the changes were done in the pip package of Masonite. The upgrade from 1.3 to 1.4 should take less than 10 minutes
Requirements.txt File
This requirement file has the masonite>=1.3,<=1.3.99 requirement. This should be changed to masonite>=1.4,<=1.4.99. You should also run pip install --upgrade -r requirements.txt to upgrade the Masonite pip package.
New Cache Folder
There is now a new cache folder under bootstrap/cache which will be used to store any cached files you use with the caching feature. Simply create a new bootstrap/cache folder and optionally put a .gitignore file in it so your source control will pick it up.
New Cache and Broadcast Configuration
Masonite 1.4 brings a new config/cache.py and config/broadcast.py files. These files can be found on the GitHub page and can be copied and pasted into your project. Take a look at the new config/cache.py file and the config/broadcast.py file. Just copy and paste those configuration files into your project.
3 New Service Providers
Masonite comes with a lot of out of the box functionality and nearly all of it is optional but Masonite 1.4 ships with three new providers. Most Service Providers are not ran on every request and therefore does not add significant overhead to each request. To add these 3 new Service Providers simple add these to the bottom of the list of framework providers:
1
PROVIDERS = [
2
    # Framework Providers
3
    ...
4
    'masonite.providers.HelpersProvider.HelpersProvider',
5
    'masonite.providers.QueueProvider.QueueProvider',
6
​
7
    # 3 New Providers in Masonite 1.4
8
    'masonite.providers.BroadcastProvider.BroadcastProvider',
9
    'masonite.providers.CacheProvider.CacheProvider',
10
    'masonite.providers.CsrfProvider.CsrfProvider',
11
​
12
    # Third Party Providers
13
​
14
    # Application Providers
15
    'app.providers.UserModelProvider.UserModelProvider',
16
    'app.providers.MiddlewareProvider.MiddlewareProvider',
17
]
Copied!
Note however that if you add the CsrfProvider then you will also need the CSRF middleware which is new in Masonite 1.4. Read the section below to add the middleware
CSRF and CSRF Middleware
Masonite 1.4 adds CSRF protection. So anywhere there is any POST form request, you will need to add the {{ csrf_field }} to it. For example:
1
<form action="/dashboard" method="POST">
2
    {{ csrf_field }}
3
    <input type="text" name="first_name">
4
</form>
Copied!
This type of protection prevents cross site forgery. In order to activate this feature, we also need to add the CSRF middleware. Copy and paste the middleware into your project under the app/http/middleware/CsrfMiddleware.py file.
Lastly, put that middleware into the HTTP_MIDDLEWARE list inside config/middleware.py like so:
1
HTTP_MIDDLEWARE = [
2
    'app.http.middleware.LoadUserMiddleware.LoadUserMiddleware',
3
    'app.http.middleware.CsrfMiddleware.CsrfMiddleware',
4
]
Copied!
Changes to Database Configuration
There has been a slight change in the constants used in the config/database.py file. Mainly just for consistency and coding standards. Your file may have some slight changes but this change is optional. If you do make this change, be sure to change any places in your code where you have used the Orator Query Builder. For example any place you may have:
1
from config import database
2
​
3
database.db.table(...)
Copied!
should now be:
1
from config import database
2
​
3
database.DB.table(...)
Copied!
with this change

What's New - Previous

Masonite 3.0

Next - Upgrade Guide

Masonite 1.4 to 1.5

Last modified 3yr ago

Export as PDF

Copy link

Contents

Introduction

Requirements.txt File

New Cache Folder

New Cache and Broadcast Configuration

3 New Service Providers

CSRF and CSRF Middleware

Changes to Database Configuration