Problem/Motivation
In core/modules/block_content/block_content.module, the documentation block for block_content_query_entity_reference_alter()
includes the line,
Block_content entities that are reusable should by default not be selectable
It should be "not reusable" rather than "reusable". Compare with the change record Added the ability to set Custom Block entities as non-reusable: it says, in part,
Since a Custom Block with the reusable field set to FALSE should not be reused in other parts of the site the queries of
EntityReferenceSelection
plugins will now automatically be altered to add:$query->condition("$data_table.reusable", TRUE);
Unless the query satisfies one of these two conditions:
...
The API documentation for block_content_query_entity_reference_alter() is generated from this documentation block, so I am adding the "API Documentation" tag.
Proposed resolution
Insert the word "not" and rewrap the affected line and the next to 80 characters.
Remaining tasks
User interface changes
None, except in the API documentation.
API changes
None
Data model changes
None
Comment | File | Size | Author |
---|---|---|---|
#11 | 3098922-7.patch | 1 KB | benjifisher |
#10 | 3098922-9.txt | 1020 bytes | AkashKumar07 |
#9 | 3098922-9.patch | 1020 bytes | AkashKumar07 |
#7 | 3098922-7.patch | 1 KB | shubham.prakash |
#3 | 3098922-1.patch | 1.01 KB | reinchek |
Comments
Comment #2
rajdeep0826 CreditAttribution: rajdeep0826 as a volunteer commentedComment #3
reinchekHi! I applied this correction.
Thanks for segnalation,
Nino.
Comment #4
benjifisher@rajdeep0826:
When you assign an issue to yourself, please also leave a comment explaining what you plan to do. Since there is already a patch on this issue, you can contribute by reviewing it. From your profile, I see that this could be your first core issue. Thanks for your interest in helping!
@reinchek:
When you add a patch to an issue, you should also set the status to Needs Review (NR). This will trigger the testbot. I will do that for this issue.
Comment #5
reinchek@benjifisher:
Next time I'll be more careful! Thanks,
Nino.
Comment #6
benjifisherI guess that @rajdeep0826 has moved on to other things, so I am unassigning this issue.
Nino:
The patch looks correct, but when I try to apply it, I get this:
Trailing whitespace should almost always be avoided. See Indenting and Whitespace in the Drupal coding standards. I am setting the issue status to NW. Please attach an updated patch and (for practice) an interdiff: Creating an interdiff.
I was reminded of the practical importance of following standards for indentation just last week. One of my coworkers fixed the indentation in
composer.json
and I had to resolve some merge conflicts. We should never have let the incorrect indentation get committed in the first place!I am also updating the issue description with a reference to the relevant change record.
Comment #7
shubham.prakash CreditAttribution: shubham.prakash at OpenSense Labs commentedAdded a patch as asked in #6
Comment #8
benjifisher@shubham.prakash:
Thanks for updating the patch. It looks correct.
This issue is tagged for novices, and your profile shows that you have already contributed to many issues, including several core issues.
Since this is a novice issue, I would still like to see an interdiff: not because I need it in this case but because this is a novice issue and I want to give novices some practice in the usual process. Back to NW.
Comment #9
AkashKumar07 CreditAttribution: AkashKumar07 at OpenSense Labs commentedAdded interdiff as per asked. Thanks
Comment #10
AkashKumar07 CreditAttribution: AkashKumar07 at OpenSense Labs commentedChanged the extension .patch to .txt. Thanks.
Comment #11
benjifisher@AkashkumarOSL:
From your profile, I see that you have credit for several issues, but so far none for Drupal core. I hope you continue to contribute!
Since you accidentally uploaded a file with the
.patch
extension in #9, I am re-uploading the patch from #7. This helps avoid confusion for both humans and the testbot.Your interdiff looks correct, but you did not follow the naming convention (see the link I gave in #6). The old standard was simply
interdiff.txt
but the current recommendation is to include the comment numbers of the patches being compared:interdiff_[old_comment_number]-[new_comment_number].txt
. In this case, that would beinterdiff_3-7.txt
. (The patch attached to Comment #3 was misnamed.)Actually, the documentation page is not entirely consistent on the naming convention. I will update it.
Comment #12
alexpottCommitted and pushed dfcf19dad1 to 9.0.x and 0f4bc1f190 to 8.9.x and 8df66ec621 to 8.8.x. Thanks!
Backported to 8.8.x as this is a docs fix.