If a content type has automatic path aliases, imported content gets an alias even if it was saved as no alias

Created on 25 August 2023, 10 months ago
Updated 10 May 2024, about 2 months ago

Problem/Motivation

Due to the interaction with Redirect module's redirect to canonical path, we want our front page, which is regularly imported by Single Content Sync, to not have a path alias.

Steps to reproduce

Configure a content type to have automatic aliases.

Save a node without an alias and with "Generate automatic URL alias" off.

Export the node.

Import itβ€” it will get an alias, even though it shouldn't.

Proposed resolution

Include the 'generate automatic URL alias' setting in the node export and honor it on import.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Needs review

Version

1.4

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States mlncn Minneapolis, MN, USA

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

Comments & Activities

Production build 0.69.0 2024