🇭🇺Hungary @zserno

I faced the same error using version 3.0.0
However, this was fixed in 827a8f4a so simply updating to 3.0.5 fixed the errors for me.

zserno → made their first commit to this issue’s fork.

I faced the same issue as #7. In my case I had custom DS block fields that were holding views blocks. These views all had contextual filters.

In D9, such DS fields were created with @ds.ds_block_field_entity_context:[entity] in their context mapping. As per #4, this context was removed from DS, so a manual resave was necessary on these DS fields' Configure block form (located at /admin/structure/ds/fields/manage_block/[ds_field_name]/block_config).

To summarize, the following steps fixed the exception for me:

1. Search for the string "ds_block_field_entity_context" among the site's config files: grep -nri ds_block_field_entity_context ./config/
2. For each ds.field.[ds_field_name].yml in the grep result, submit the settings form at /admin/structure/ds/fields/manage_block/[ds_field_name]/block_config

Diff after executing above steps and a fresh config export:

 context_mapping:
-      nid: '@ds.ds_block_field_entity_context:node'
+      nid: '@node.node_route_context:node'

Just ran into this problem. Attached patch fixes it, rolled against branch 2.0.x

Patch to fix the Php error.

zserno → created an issue.

I ran into this error after upgrading a Drupal 9 site to 10.

I agree with #16: originally this site started out as an early Drupal 8 site. Somehow, one of the views had its pager's offset configuration unset. Setting the offset value to '0' fixed the issue for me.

zserno → created an issue.

Re-rolled against HEAD.

Attached patch adds the aria-label attribute to inline

zserno → created an issue.