Note:tries to provide an actionable first step for this issue.
From override the block form and prevent the user from creating a Views block instance title different from the View display title. This results in this UX fail:. Right now, Views goes out of its way to
It basically prevents the UX improvement offrom taking effect, regresses from D7 in that you can no longer set a block instance title different from the View title, and confuses users by being different from every other block.
Filing as major because this is considered a blocker for all Views block conversions.
Allow users to override the View title on the block configuration form.
We need to find a happy medium between letting content authors configure their block instances, and communicating to users that Views controls the block title dynamically. @yoroy proposed this interaction to resolve the issue:
There is also a concern that site builders will no longer be able to control the titles for these blocks once the block is allowed to override it. In #3 (and related issue ), @dawehner suggested that we might want to allow Views admins to restrict when these settings can be overridden on a per-block level.
Finally, we need to find a way to describe what the view title is for the user, since Views sets it dynamically based on conditions like whether the view has no results or what arguments are supplied to it.also is exploring this issue within the Views UI itself.
|#87||Screen Shot 2013-12-05 at 7.02.05 PM.png||70.19 KB||webchick|
|#87||Screen Shot 2013-12-05 at 6.55.39 PM.png||59.35 KB||webchick|
|#87||Screen Shot 2013-12-05 at 6.45.13 PM.png||57.1 KB||webchick|
|#87||Screen Shot 2013-12-05 at 6.43.59 PM.png||56.57 KB||webchick|
|#87||Screen Shot 2013-12-05 at 6.42.37 PM.png||59.28 KB||webchick|