Problem/Motivation

The word custom is redundant in most cases in a content management system. Everything that the user creates is custom in some way because it didn't exist before the user made it. Here are some examples from the existing block UI (as of 24/6/2013).

Screenshot showing the use of the word custom in multiple labels created by the block module

Proposed resolution

Instead of the button label Add custom block type, the label should simply be Add block type. Instead of the form label Custom block types, the form label should simply be Block types

Remaining tasks

Change the labels

User interface changes

String changes.

API changes

None.

#1875252: [META] Make the block plugin UI shippable



Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tim.plunkett’s picture

Status: Active » Closed (duplicate)

I think this can be marked a duplicate of #1920862: Rename custom_block.module to block_content.module, as "Custom Block" module will become "Block Content" module.

jessebeach’s picture

Noted, thanks!

Antti J. Salminen’s picture

Issue summary: View changes
Status: Closed (duplicate) » Active

#1920862: Rename custom_block.module to block_content.module decided to leave the decisions about rewording to a follow up so this looks to me like it should still be active. "custom block" seems somehow out of place now. I feel having only "Block types" might be confusing though as they are separate from other kinds of blocks and there will be block types not visible on that list. An alternative could be having "Content block types".

albita’s picture

Assigned: Unassigned » albita

working on it...

albita’s picture

Status: Active » Needs review
FileSize
1.18 KB

Switched "Add custom block" to "Add block".

Status: Needs review » Needs work

The last submitted patch, 5: 2027101-5-remove-custom.patch, failed testing.

carletex’s picture

carletex’s picture

Assigned: albita » Unassigned
Status: Needs work » Needs review
FileSize
3.12 KB

Attached a new patch.

Some tests relied on a button text with the word 'custom'.

grisendo’s picture

Works for me

vollepeer’s picture

Path #8 is now broken because of #2291137.
I recreated the patch against the current DEV.

The last submitted patch, 8: 2027101-8-remove-custom.patch, failed testing.

Antti J. Salminen’s picture

To me it seems that if the terms used are identical for both user created block types and all the others, it could be an usability issue. After all the custom blocks will be completely defined by the user but they can't do much about the other ones.

Looks like current patch may also not get rid of the "custom block" terminology everywhere as I think we'd still have the "Custom block library" tab and the category "Custom" for these blocks.

Anonymous’s picture

FileSize
25.37 KB

Hi, i recreate the pacth.
H1 tag have the word custom yet, looks good other.

Anonymous’s picture

Status: Needs review » Needs work

Updated status.

The last submitted patch, 11: drupal-remove-custom-2027101-11.patch, failed testing.

alvar0hurtad0’s picture

Status: Needs work » Needs review
FileSize
3.14 KB

This is #11 patch rerolled (or similar)

zzhao’s picture

Status: Needs review » Needs work
FileSize
116.41 KB

This patch does work for the button "Add custom block type" (see the original picture).

According to the original post, it looks like Drupal core has changed the link text from "Custom block types" to "Custom block library". Is the current link text supposed to replace the word "Custom" as well? I mark this patch as "Needs work" since it's a question needs to be answered first.

From DrupalCon 2015 LA.

yogen.prasad’s picture

Assigned: Unassigned » yogen.prasad
_KurT_’s picture

Status: Needs work » Needs review
FileSize
3.9 KB
33.5 KB

Can't find where to change page title, see 2015-06-18_1253.png

Status: Needs review » Needs work

The last submitted patch, 21: remove_the_word-2027101-21.patch, failed testing.

_KurT_’s picture

Status: Needs work » Needs review
FileSize
3.9 KB
_KurT_’s picture

FileSize
3.9 KB

The last submitted patch, 23: remove_the_word-2027101-21.patch, failed testing.

Status: Needs review » Needs work

The last submitted patch, 24: remove_the_word-2027101-24.patch, failed testing.

deepakaryan1988’s picture

Re-rolling the patch which is in #18 with some modification. Also attaching interdiff

deepakaryan1988’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 27: remove_the_word-2027101-27.patch, failed testing.

_KurT_’s picture

Assigned: yogen.prasad » Unassigned
FileSize
18.25 KB

Still can't find where to change title, see image in my comment #21

_KurT_’s picture

Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 30: remove_the_word-2027101-30.patch, failed testing.

_KurT_’s picture

Status: Needs work » Needs review
FileSize
18.25 KB
manauwarsheikh’s picture

Status: Needs review » Needs work
Issue tags: +SrijanSprintNight
FileSize
71.04 KB
56.94 KB

What: checked for appearance on "custom" word.
Result: Missing title(when block library is selected), custom word is still appearing.
Status: Needs Work!

_KurT_’s picture

Status: Needs work » Needs review
FileSize
19.33 KB

"custom" word deleted, but for disappearing title - can't reproduce, for me title is present and still i can't find a place where to change it (see image in #21)

dawehner’s picture

deepakaryan1988’s picture

Issue tags: -SrijanSprintNight

Removing srijansprintnight tag!! :)

manauwarsheikh’s picture

FileSize
54.47 KB

What: checked for the appearance on "custom" word.
Browser: Chrome on Linux.
Result: Missing title(when block library is selected). Screenshot attached
Status: Needs Review

manauwarsheikh’s picture

Status: Needs review » Needs work
deepakaryan1988’s picture

Issue tags: +Needs reroll

Needs re-roll

hitesh-jain’s picture

Assigned: Unassigned » hitesh-jain
pguillard’s picture

Status: Needs work » Needs review
FileSize
19.35 KB

Patch rerolled
@hitesh-jain : Hope I didn't take your job!

LewisNyman’s picture

Issue tags: -Needs reroll
pguillard’s picture

Assigned: hitesh-jain » Unassigned

drupal a11y’s picture

Issue summary: View changes
FileSize
76.47 KB

The renaming was done for the "add block"-button but not for the "page title".
But maybe this is a caching issue in my dev as it locks o.k. in the module files.

Also the navigation item "custom block types" has been removed meanwhile from the left navigation into a tab "Block Library".

Example image:
Block Admin UI

drupal a11y’s picture

Status: Needs review » Needs work
drupal a11y’s picture

Issue summary: View changes
drupal a11y’s picture

Status: Needs work » Needs review
drupal a11y’s picture

Can anyone else please test it if the remaining issues is maybe a cache problem within my dev.

drupal a11y’s picture

Issue summary: View changes
FileSize
95.91 KB

I have found some other text strings where still "custom block(s)" is mentioned but not the title we want to change.
Also it looks that on this page the code structure is different from the other pages and maybe "breaks" (wrong spelled in the pic) the layout.

Please see:
Wrong title custom blocks library

drupal a11y’s picture

Finally I think the patch is ok, but the issue needs additional work.

drupal a11y’s picture

Issue summary: View changes
MattA’s picture

Component: block.module » block_content.module
Status: Needs review » Postponed

In #2512456: Implement the new block layout design to emphasize the primary interaction of placing a block it was determined that it was more important to remove "library" from the label.

However, this was not helpful either, because it's actually a list of only your custom blocks, *not* a "library" of anything. I think the quote from one participant was something like, "Custom block library listing, now we're talking! ...Wait. I thought you said you had a block library?!"

We cannot remove both "custom" and "library" from the label. I think many users find "custom blocks" to be synonymous to "block content" as well (for example, even the help page for the module is under "Custom block"). Additionally, #2523154: Improve workflow for creating custom blocks also changes the workflow, menu structure, and labels of custom block pages, so that many instances of "custom blocks" become "block content" or "block types".

Therefore this issue should at a minimum be postponed on #2523154 and used to clean up any remaining references to "custom block" if there is a need for that. Otherwise it should be closed.

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.

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.

smustgrave’s picture

Status: Postponed » Closed (outdated)

Closing out as outdated as there hasn't been movement since being postponed 7 years ago. I agree with the comment in #54

We cannot remove both "custom" and "library" from the label. I think many users find "custom blocks" to be synonymous to "block content"

If anyone still feel this is an issue please reopen to justify why.