Add intelligence to front page configuration migration

Created on 3 November 2015, almost 10 years ago
Updated 23 May 2025, 4 months ago

Problem/Motivation

The legacy site_frontpage variable is migrated as-is (well, with a '/' prepended) to system.site config. If the incoming path doesn't match a valid route in D8, you'll end up with a broken front page. A specific common example is the default D6 and D7 setting of 'node' - in D8, the /node route only exists if you have views enabled - if not, the front page becomes a 404.

Proposed resolution

Ideally, identify whether the incoming front page configuration matches an existing route and if not generate a message.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ“Œ Task
Status

Postponed

Version

11.0 πŸ”₯

Component

migration system

Created by

πŸ‡ΊπŸ‡ΈUnited States mikeryan Murphysboro, IL, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024