Moving to a Modern Development Workflow for Craft CMS

Updating Craft CMS & Plugins

We update the project to latest Craft CMS and plugins and run any required migrations.

I like to do updates to Craft and plu­g­ins using Com­pos­er. You can use Craft’s updater but I sug­gest you don’t mix the two.

ddev exec composer update

Once the update is com­plete, we need to run all pend­ing migra­tions so our data­base is up-to-date with the lat­est from Craft and any plu­g­ins requir­ing migrations.

ddev exec php craft migrate/all
Checking for pending migrations ...
Total 16 new Craft migrations to be applied:
    - m201116_190500_asset_title_translation_method
    - m201124_003555_plugin_trials
    - m210209_135503_soft_delete_field_groups
    - m210212_223539_delete_invalid_drafts
    - m210214_202731_track_saved_drafts
    - m210223_150900_add_new_element_gql_schema_components
    - m210302_212318_canonical_elements
    - m210326_132000_invalidate_projectconfig_cache
    - m210329_214847_field_column_suffixes
    - m210331_220322_null_author
    - m210405_231315_provisional_drafts
    - m210602_111300_project_config_names_in_config
    - m210611_233510_default_placement_settings
    - m210613_145522_sortable_global_sets
    - m210613_184103_announcements
    - m210829_000000_element_index_tweak

Total 1 new Feed Me migration to be applied:
    - m210317_000000_search_indexes

Apply the above migrations? (yes|no) [no]: yes
17 migrations were applied.

Migrated up successfully.

Now when we vis­it the site in the web brows­er, every­thing should be work­ing properly!

Now, we can add and com­mit the changes from the update to the Git repository. 

git commit -am "updated to latest Craft and plugins"

Moving to a Modern Development Workflow for Craft CMS is made up of the following videos: