Problem/Motivation

The Namespace for assets is under component_library. If that is the intended place, why are we asking for the theme when creating the assets? Either remove the question for the theme or make the assets part of the theme namespace. And add visual queues how to use the created assets. Flagging this as a bug because it results in a what is happening situation. It also could lead to BC issues if we need to move everything into the theme if that was the intended result.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

heddn created an issue. See original summary.

heddn’s picture

Issue summary: View changes
StatusFileSize
new17.59 KB
new32.96 KB
tim bozeman’s picture

Status: Active » Needs review
StatusFileSize
new3.38 KB

Yes, you're right. Asset's don't need a theme field at all! I also moved Component Library to the top of the list when you are attaching libraries. That was a lot of scrolling before.

  • Tim Bozeman committed 157f82a on 1.0.x
    Issue #3281241 by Tim Bozeman, heddn: Namespace for assets is under...
tim bozeman’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.