Drupal 9 Compatibility

#3 seems to work. Thanks iamdroid.

Hii,

This patch works for me.

Thanks

I have created this patch for Drupal 9 compatibility on development version 8.x-1.x-dev.
This patch having the consolidated code from the issues Drupal 9 Compatibility and Not working in Drupal 8 - Filter not Visible.

Please review the patch.

#3 worked. Thanks!

The following does not pick up custom blocks.

        $replacement = '';
        if (\Drupal::service('entity_type.manager')->getStorage('block')->load($block_id)) {
         $block = \Drupal::service('entity_type.manager')->getStorage('block')->load($block_id);
          $block_view = \Drupal::service('entity_type.manager')
            ->getViewBuilder('block')
           ->view($block);
          $replacement = \Drupal::service('renderer')->render($block_view);
        }

Add code as follows:

        $replacement = '';
        // Render blocks in code.
        if (\Drupal::service('entity_type.manager')->getStorage('block')->load($block_id)) {
          $block = \Drupal::service('entity_type.manager')->getStorage('block')->load($block_id);
          $block_view = \Drupal::service('entity_type.manager')
            ->getViewBuilder('block')
            ->view($block);
          $replacement = \Drupal::service('renderer')->render($block_view);
        }
        // Render custom blocks.
        if (\Drupal::service('entity_type.manager')->getStorage('block_content')->load($block_id)) {
          $block = \Drupal::service('entity_type.manager')->getStorage('block_content')->load($block_id);
          $block_view = \Drupal::service('entity_type.manager')
            ->getViewBuilder('block_content')
            ->view($block);
          $replacement = \Drupal::service('renderer')->render($block_view);
        }

I am finding the git repo confusing to work with. A patched module with modified README.txt is attached. It seems to be working on D9 for both code and custom blocks.

Note the above relies on using the machine name of a block instance. Therefore a custom block created with a plugin should be placed, and if necessary disabled, and the machine name of the block instance used. To display a block created by a plugin using the block's id in the annotation, something based on https://drupal.stackexchange.com/questions/171686/how-can-i-programmatic... works. This should be documented in README.

Hi,

Patch Comment#7 doesn't work anymore with latest Insert_Bock using Composer
insert_block-d9-compatibility-3151591-7.patch

Last comment changing composer json worked!

Thanks for building!

greetings, Martijn

Hello, in comment #13, for D9, it is explained to add :

"url": "https://packages.drupal.org/9",

But it returns this error :

[Composer\Downloader\TransportException]                                                            
  The "https://www.drupal.org/9/packages.json" file could not be downloaded (HTTP/1.1 404 Not Found) 

Are you sure we can do this ? In other D9 projects, I still see

"repositories": [
        {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
    ],

Sometimes the "file could not be downloaded" error with composer results from using composer version 1 rather than composer 2.

Drupal 9 compatible 8.x-1.0-beta1 is released.

@vinyl_roads -- You are correct, merci. There is no Composer endpoint for Drupal 9 packages, we still use the one for Drupal 8. I made so many of these Issue Forks, and most of them have the correct endpoint, but this one slipped through the cracks. Fixing it now!