This is breaking tests on HEAD (because 8.7 was just branched).

#2976334: Allow Custom blocks to be set as non-reusable adding access restriction based on where it was used. added a new base field to the block content type. For now, this is in 8.7 and up. It may be back ported.

We should conditionally add this to the expected document in 8.7 and up.

CommentFileSizeAuthor
#4 Screen Shot 2018-07-17 at 11.48.14.png120.02 KBgabesullice
#2 2986383-3.patch866 bytesgabesullice

Comments

gabesullice created an issue. See original summary.

gabesullice’s picture

gabesullice
Primary language English
commented
Status: Active » Needs review
StatusFileSize
new 2986383-3.patch866 bytes

Should fix it.

  • gabesullice committed c525d20 on 8.x-2.x 
    Issue #2986383 by gabesullice: Drupal core compatibility: Block content...
gabesullice’s picture

gabesullice
Primary language English
commented
Status: Needs review » Fixed
StatusFileSize
new Screen Shot 2018-07-17 at 11.48.14.png120.02 KB

This indeed fixes things. Committed! :)

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

👍

gabesullice’s picture

gabesullice
Primary language English
commented
Assigned: gabesullice » Unassigned

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

drupalninja99’s picture

drupalninja99 commented

Why does JSON:API only render reusable blocks? Paragraphs endpoints render all paragraphs, I don't understand why JSON:API wouldn't render inline blocks at each block entity endpoint.