Updating

We attempt to document every possible breaking change. Since some of these breaking changes are in obscure parts of the CMS, only a portion of these changes may actually affect your website.

Updating To 5.13

Estimated Update Time: 1 Hour

Note: your upgrade may crash during the "Updating Database" step, with an error in the 'Blueprint.php' file. If this occurs, you should be able to run the upgrade process again immediately, and can proceed as normal. If you are still encountering errors, please contact an application developer for further help.

The recent 5.13 release of Fusion has seen a number of changes, fixes and additions. This will be the last major update to the v5 line of FusionCMS, with all future resources going into the development of v6. Critical bug patches and security updates will still be pushed out as needed.

Redirects now include a notes field

When creating a redirect entry in the SEO module, an informational note can be added to that entry, hopefully to help reference it in the future

Removed "glide()" helper function

The glide() helper function, while not really ever used, was causing problems on some browser (IE11) because of the URL that it was returning. According to a previous poll, this shouldn't affect any current sites.

New field type: Button

We have included a new field type that can be used immediately on any updated theme: Button. This simple field is actually three fields in one- each button fieldtype will include an input for the button link, the text of the button, and an option for the target attribute. On the front end, the field will also include an isComplete boolean value, returning true if both the link and text fields are filled in. These properties should be referenced as an array, similar to replicator or address field types: $entry->banner_button['text'].

Dropdowns for "Group" entry

When creating or editing a field, the "Group" setting will now be a <select> field, rather than a simple input. On page load, the dropdown will contain all of the current groups entered for this type, so groups can easily be selected based on what currently exists. This also includes a 'Create new group' option to generate an input field for a new group.

Addition of Google reCAPTCHA

Fusion now includes native support for Google's reCAPTCHA v2 service. When this is enabled on a form, all submissions for this form will be required to include captcha verification. More information on setup of this for older themes, as well as a breakdown of the submission process, can be found here.

Access Token Expiration Dates

In mid 2018, a change was made to increase the default expiration of the API keys/tokens from the default 1 year to the new 100 years. This did not actually work, but any 5.13.0+ site will now correctly generate keys with this longer expiration.

Fix for active states in menus

For a while, the isActive() function was behaving incorrectly, and not properly returning menu active states. This should now work correctly, both for development and production environments.

Add Google Analytics graph to Fusion dashboard

A graph with analytics about visitors, page views, form contacts and devices can now be found on the dashboard of the CMS when the proper credentials are uploaded. These credentials can be entered in the system settings, under Google -> Insights.

Asset selection window

No longer will the asset modal be stuck at the top of the page! Now, the modal will size to fit the screen, and stay fixed in this position until closed, whether the user was at the top of the page or the very bottom. This will also mitigate page height problems we see occasionally when uploading assets or creating new categories in this modal.

Upgrade to Laravel 5.7

This update is kind of a lot, but one of the biggest things of note is that we can no longer use the one-line @php(something()) shortcut in our blade templates. Any places that this occurs in a theme will need to be changed to:

@php
  something();
@endphp

Glide improvements

A simple change, but in past versions, calling an image file without Glide transformations (like /asset/54fda349) would actually still run the image file through the Glide processor. In some cases, it can actually cause images to return on the front end with larger file sizes than they were uploaded with. Now, if no transformations are specified, the image is returned wholesale without calling Glide at all.

Category sorting

Much like entries, categories can now be sorted manually in the CMS. Each category group has its own settings for automatic and manual sort, as well as the sort term and order. Like entries, the manual sort can be used to sort them in to parent/child relationships

Disabling pagespeed module in development

We've observed that there are numerous problems that can pop up when the Pagespeed module is run- what necessitated this change is that the default debug/error screen in the dev environment can show up incorrectly, or lose its interactive functionality because of the way this plugin is printing JS on the page. We've now disabled the pagespeed module entirely for any sites running in the dev enviroment.

Updating To 5.10

Estimated Update Time: 5 Minutes - 1 Hour

Navigation Module

Any assigned fieldtypes to navigation menus were not originally resolving their values through the proper channels. v5.10 fixes this issue, so any fieldtypes you had previously set must be updated to use the expected fieldtype casting as is expected anywhere else in your view files.

Example of code that used to work:

@if (isset($item->fields['background'][0]))
    @php($image = get_asset($item->fields['background'][0]))
    <div class="menu__bg lazy" style="background-image: url('{{ url('asset/'. $image->slug) }}');"></div>
@endif

Example of a way to pull this data now:

Note, you don't need to call get_asset any longer as images are automatically resolved for you.

@if (isset($item->fields['background']->slug))
    {{-- Just reassigning for convenience --}}
    @php($image = $item->fields['background'])

    <div class="menu__bg lazy" style="background-image: url('{{ url('asset/'. $image->slug) }}');"></div>
@endif

Updating to 5.6

Estimated Update Time: 10 Minutes - 1 Hour

During the upgrade process you may encounter a directory error: mkdir(): File exists. To resolve, check for and delete the storage/temp folder. This is related to a reported bug that does not recursively apply the same permissions to folders inside of the storage folder, thus denying permission to delete the temp directory and create a new one during the upgrade process.

• Create a manual backup, a proceed with the standard upgrade process.
• Once upgraded, bring your site back down for maintenance: php artisan down
• Re-import your database from the backup
• Run the following console commands in order:
  1. php artisan module:migrate
  2. php artisan upkeep
  3. php artisan up

You should now be fully upgrade.

Updating to 5.5

Estimated Update Time: 5 Minutes

You will likely get an error during upgrade indicating “foreign id key” migration. To circumnavigate this issue, please add the following entry to the “migrations” table, incrementing the ID and Batch as needed:

• 2018_07_19_185316_make_parent_id_foreign_key_null_on_delete

Updating to 5.4

Estimated Update Time: 5 Minutes

v5.4 introduces an update to the way we are pulling in our required Composer dependencies. We ran into an issue where one of the dependencies we had pushed a breaking change to a patch release, effectively breaking any new and existing sites attempting to upgrade.

To update to v5.4, please follow the following steps:

1. Open your composer.json file, and change the version dependency for teamtnt/laravel-scout-tntsearch-driver to 3.0.6. Save the file.
2. Delete your storage/temp directory if it exists.
3. Run composer update
4. Run php artisan fusion:upgrade

Updating to 5.3

Estimated Update Time: 10 Minutes

1. Attempt an upgrade, it's going to fail, don't panic.
2. Run php artisan module:migrate matrix
3. Re-run the upgrade

Updating To 5.1

Estimated Update Time: 2 Hours

Categories Module

Repositories have been ripped out of the categories module

Please ensure that you are not referencing any of the repository-specific methods and properties when using the category helpers.

category_entries() helper method has been removed

In line with removing the repository interface within categories, we've updated the way category entries need to be queried.

When piggybacking off of the matrix_entries() helper method, you now have access to a new underCategory() method. This will query the results of your entries down to the category and category group handle's specified:

// Get all entries under the category with a handle of "space-sloth" regardless of the category group
$entries = matrix_entries('blog')->underCategory('space-sloth')->get();

// Get all entries under the category with a handle of "nuclear-rabbits" under the category group "pets"
$entries = matrix_entries('blog')->underCategory('nuclear-rabbits', 'pets')->get();

Users Module

The "Your Account" URL has been changed

The URL has changed from /settings to /account.

Furthermore, each section of the account management interface have been extracted to their own endpoints with their own templates:

Themes Module

The underlying theming framework has been updated.

Reference to Theme Namespace

You are no longer required to reference your theme's namespace when referencing view files.

Performing a find and replace on your theme's namespace to remove should suffice in this update (e.g. search for example:: in your view templates where example is the namespace of your theme).

Renamed theme_layout() helper method

The theme_layout() method has been renamed to be simply layout(). Please ensure that your @extends blade directive calls have been updated.

Furthermore, if you are still using the Theme::getLayout() method or $theme_layout variable, please update this to reference layout() as well.

Matrix Module

Repositories have been ripped out of the matrix module

Please ensure that you are not referencing any of the repository-specific methods and properties when using the matrix helpers.

Deprecated Repository Methods

For further documentation on the methods available to you with this update, please refer to the Laravel documentation here: https://laravel.com/5.4/eloquent