CM Document for content types should show alias pattern

Created on 23 February 2023, about 2 years ago

Problem/Motivation

It would be nice if when on the CM Document page you can see the alias patterns that may exist for a content type. It would have to be conditional on path_alias and pathauto being installed.

Should also show title patterns if they exist.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

1.0

Component

Code

Created by

🇺🇸United States swirt Florida

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

Comments & Activities

  • Issue created by @swirt
  • 🇺🇸United States swirt Florida
  • 🇮🇳India nidhi27

    Hi @swirt,

    It would be great if you can tell me the structure to display the data.

    Thanks!

  • 🇺🇸United States swirt Florida

    Great question. I almost forgot what my intention was.

    Example:
    Let's say we have a content model document that is documenting the "article" content type (or vocabulary) When you view the document :

    • If the pathauto module, is installed it would display the Pathauto pattern for articles"Pathauto pattern: article/[node:title]"
    • The location should be below any custom fields on the document, but above the permissions table.
    • If Pathauto is not installed, nothing would be output.
    • If Pathauto is installed but there is no pattern for this content type, it would say "Pathauto pattern: No pattern set."

    You can ignore my note in the issue to also do it for any title patterns. That solution may not be tied to just detecting one module being used..

  • 🇺🇸United States swirt Florida
  • 🇮🇳India nidhi27

    Hi @swirt,

    There may be possibility that one content type can have multiple patterns also. In that case it will be good to show in table. Kindly share your view.
    Thanks!

  • 🇺🇸United States swirt Florida

    That is a good point, @nidhi27. I think I'd prefer a list to a table. I think it is better for accessibility.

Production build 0.71.5 2024