Skip to content

[BUG] UX improvements needed for static_alias integration into structure board #8415

@petrklus

Description

@petrklus

I believe work is needed to make the static_alias functionality work inside the structure board, especially when djangocms-versioning is also in place.

Issues at the moment:

  • When a draft is not present, the plugin edit buttons are still there and the error message is not helpful Image

  • It is not possible to create a new draft from the same view

  • The publication controls are also not obvious

  • The plugin add button is visually disabled and clicking it shows/hides the plugins (which is not correct)

Suggestions:

  • Remove the plugin add and edit button when content is published and no draft is present
  • Replace the top level add plugin button with a button to create a new draft when no draft is present
  • Add a publish button when draft is present into the structure board as well (next to the top level add plugin button)

The overall goal is to be able to edit and publish the static_alias contents from the frontend. It is not practical (at least for our use case) to be editing and publishing on another page, especially for in-page elements that do not render right when on their own.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions