Updated: Comment #0
Problem/Motivation
The Custom Block entity type's description (info) field is still handled through custom code in entity forms and entity views
Proposed resolution
Move to widgets and formatters.
Remaining tasks
Fix test failures.
User interface changes
None.
API changes
None. The custom_block.info base field is rendered using widgets and formatters, and is no longer exposed as an "extra field".
| Comment | File | Size | Author |
|---|---|---|---|
| #19 | 2225371-19-custom-block-base-fields.patch | 15.02 KB | mr.baileys |
| #15 | 2225371-15-custom-block-base-fields.patch | 15.06 KB | mr.baileys |
| #13 | Welcome_to_Site-Install___Site-Install.png | 9.15 KB | galooph |
| #11 | 2225371-7-10-interdiff.txt | 840 bytes | mr.baileys |
| #11 | 2225371-10-custom-block-base-fields.patch | 15 KB | mr.baileys |
Comments
Comment #1
wim leersNote: this patch was split off from Berdir's patch in #2010930: [META] Apply formatters and widgets to rendered entity base fields (all besides node.title).
Comment #2
wim leersComment #4
mr.baileysWorking on this during the Szeged sprint.
Comment #5
wim leersNote: this is still missing a
setRequired()call, like I added over at #2225399-2: Apply formatters and widgets to Feed base fields. You may want to add that too, mr.baileys.Comment #6
mr.baileysTest failures fixed.
Since the property keys returned by CustomBlockTranslationUITest::getNewEntityValues() are used to build the edit-array for form posts (getEditValues()) as well as for entity creation (ContentTranslationTestBase::createEntity()), and since the property name to use in both cases differs ('info' for entity creation, 'info[0][value]' for form posting), I had to hack-by-overriding getEditValues() to ensure the correct property name is used.
Comment #7
mr.baileysAdded the setRequired-call mentioned in #5.
Comment #8
yanniboi commentedI have had a look at this.
Installing with minimal and standard profiles works, creating a custom block works and editing works.
Compared the form display settings before and after patch.
Also configuring the block description works fine.
Looks like this is RTBC
Comment #9
wim leersUpdating issue summary as per yched's instructions at #2225431-4: Apply formatters and widgets to Taxonomy Term base fields.
Thanks for the review, yanniboi!
Comment #10
wim leersI manually tested the patch also, and I found one big problem: it causes block descriptions to be rendered:

This should be removed. Then the block description won't be rendered.
Comment #11
mr.baileysRemoved view display options from description as per #10
Comment #12
k.dani commentedI have applied the patch against the *current* HEAD of 8.x branch without any problems. The Block description isn't rendered and the configuration works fine for me. The only problem I noticed is the following:
If I place a custom block into a region, I will get the following warning: "Theme hook custom_block not found.". I couldn't find the implementation of "custom_block" theme. May it be missing?
Anyway, it seems to me that this problem is not related to the issue and the patch, so I change the status of it to RTBC.
Comment #13
galooph commentedJust tested this manually and it works as expected. The block description is no longer rendered.
Comment #14
alexpott2225371-10-custom-block-base-fields_1.patch no longer applies.
Comment #15
mr.baileysStraight re-roll to keep up with HEAD.
Comment #16
galooph commentedPatch from #15 applied cleanly and worked fine. The block description was not rendered.
Comment #17
mr.baileysOk, since this was a straight re-roll and the tests came back green, back to RTBC.
Comment #18
alexpott2225371-15-custom-block-base-fields.patch no longer applies.
Comment #19
mr.baileysStraight re-roll. (Wim Leers told me to add "Avoid commit conflicts").
Comment #20
pfrenssenComment #21
pfrenssenLooking good! Back to RTBC.
Comment #22
catchCommitted/pushed to 8.x, thanks!
Comment #24
wim leers