Problem/Motivation

The informational texts displayed when viewing an empty list of items is inconsistent.

For example:

Path Text when empty
/admin/content No content available.
/admin/content/block-content There are no custom blocks available.Add a custom block.*
/admin/content/comment No comments available.
/admin/content/files No files available.
/admin/structure/views (no text at all)
/admin/structure/block No blocks in this region
/admin/config/search/path No URL aliases available. Add URL alias.*
/admin/config/development/configuration The staged configuration is identical to the active configuration.
/admin/config/media/responsive-image-style There is no Responsive image styles yet.
/admin/structure/display-modes/form (no text at all)
/admin/structure/comment There is no Comment types yet
/admin/structure/types No content types available. Add content type.*
admin/config/media/image-styles There are currently no styles. Add a new one.*

* hyperlink to add a new entry.

Proposed resolution

Decide on a consistent form for such messages, whether to use the plural or singular case, start message with "There is/are..." or just "No..." and whether to end with a link to add new items or not.

Remaining tasks

Choose standardisation.
Identify all lists.
Implement standardisation for all lists.

User interface changes

Text changes only, unless it is decided to remove inline links to create new items, eg as for /admin/config/search/path.

API changes

None.

CommentFileSizeAuthor
#36 inconsistent_messages-2219749-5.patch9.25 KBAbhishek_Singh
#4 inconsistent_messages-2219749-4.patch8.94 KBjoyceg
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Bojhan’s picture

Bojhan CreditAttribution: Bojhan commented

https://www.drupal.org/node/1146122

"There are no [things] available. Add [a thing]"

We already decided on a standard, it is plural and we always and with a link singular.

Bojhan’s picture

Bojhan CreditAttribution: Bojhan commented
Issue tags: -Needs usability review
joyceg’s picture

joyceg CreditAttribution: joyceg commented
Assigned: Unassigned » joyceg
joyceg’s picture

joyceg CreditAttribution: joyceg commented
FileSize
inconsistent_messages-2219749-4.patch8.94 KB

Adding the patch here.

joyceg’s picture

joyceg CreditAttribution: joyceg commented
Status: Active » Needs review
Eli-T’s picture

Eli-T
he/him
Primary language English
Location Manchester
CreditAttribution: Eli-T commented
Status: Needs review » Needs work

There are no contents available.Add a new content.

The word content can't be used like this. It would be more appropriate to say "There is no content available. Add new content."

All periods should be followed by a space.

There is no point adding the Add a new
strings without them being links.

There are no Custom blocks yet.Add a new Custom block.

Custom should not be capitalised.

'There are no disabled views.Add an enabled view.'

That's confusing.

The last submitted patch, 4: inconsistent_messages-2219749-4.patch, failed testing.

The last submitted patch, 4: inconsistent_messages-2219749-4.patch, failed testing.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Issue tags: +Barcelona2015
danharper’s picture

danharper CreditAttribution: danharper as a volunteer and at Curve Agency commented

Working on this one

danharper’s picture

danharper CreditAttribution: danharper as a volunteer and at Curve Agency commented
Issue summary: View changes
danharper’s picture

danharper CreditAttribution: danharper as a volunteer and at Curve Agency commented
Issue summary: View changes
danharper’s picture

danharper CreditAttribution: danharper as a volunteer and at Curve Agency commented

After looking through this I have a question regarding generating markup inside the t function, currently the markup is like this

'#empty' => $this->t('There are no comments available. Add a comment.')

Where I want

Add a comment

to be a link.

How should I use the t() function to include a link/markup?

t('There are no comments available. <a href="%link">Add a comment.</a>', array('link' => '/block/add')),

Cheers Dan

Eli-T’s picture

Eli-T
he/him
Primary language English
Location Manchester
CreditAttribution: Eli-T commented

I've found the patch on #2513402: Any time a user creates a thing and saves, display a link to the thing created in the status. at https://www.drupal.org/files/issues/any_time_a_user_creates-2513402-36.p... has loads of examples of generating links in t().

danharper’s picture

danharper CreditAttribution: danharper as a volunteer and at Curve Agency commented
Issue summary: View changes

Added another path to be checked.

danharper’s picture

danharper CreditAttribution: danharper as a volunteer and at Curve Agency commented
Issue summary: View changes
danharper’s picture

danharper CreditAttribution: danharper as a volunteer and commented
Issue summary: View changes

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Issue tags: +Dublin2016
ifrik’s picture

ifrik
she/her
CreditAttribution: ifrik commented
Issue tags: +Usability, +ui text, +sprint
philipnorton42’s picture

philipnorton42 CreditAttribution: philipnorton42 as a volunteer commented
Assigned: joyceg » philipnorton42
philipnorton42’s picture

philipnorton42 CreditAttribution: philipnorton42 as a volunteer commented
Assigned: philipnorton42 » Unassigned
yoroy’s picture

yoroy CreditAttribution: yoroy commented

Lets see if we can work on this some more this friday :) https://groups.drupal.org/node/515590

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone CreditAttribution: quietone at PreviousNext commented
Issue summary: View changes
Status: Needs work » Active
Issue tags: +Bug Smash Initiative

There is still inconsistencies in these messages. I have updated the IS for the strings in 10.1.x

The next step is to get agreement on the strings.

Abhishek_Singh’s picture

Abhishek_Singh CreditAttribution: Abhishek_Singh at OpenSense Labs commented
FileSize
inconsistent_messages-2219749-5.patch9.25 KB

Added another for the issue.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.