🇨🇷Costa Rica @mcortes19

I added the masquerade cache context to the main region footer menu

+1

I confirm this is working as expected.

Merged to dev branch

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

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

@almunnings yes, I will explore option 3 to expose it as MetaTagScript

@almunnings Since we are using graphql-request for batching request, is not easy to replicate this issue outside the app.

After a thoroughly debugging, we noticed at some point the`EntityOwner` FieldType wasn't returning the `entity_owner` data-producer when we requested data using batch-request. So we ended up by removing that approach and just request all information we need in a single GraphQL query.

mcortes19 → created an issue.

@almunnings I confirm #8 works for me as well

@almunnings We are migrating a site from D7 with a lot of Paragraphs and when we enabled some fields the error appeared, but was hard to identify which field or fields are the cause because was most a random behavior.

Definitely I'll debug thoroughly and posted here my finding. For now this MR fixes the issue!

@abhishek_gupta1 I added a MR based on your solution

mcortes19 → created an issue.

I tested on the D10.8 site and it returned the following error: For error #0: Error: Call to protected method Drupal\menu_link_content\Plugin\Menu\MenuLinkContent::getEntity() from scope Drupal\graphql_compose_menus\Plugin\GraphQL\DataProducer\MenuTreeLinkEntity in Drupal\graphql_compose_menus\Plugin\GraphQL\DataProducer\MenuTreeLinkEntity->resolve() (line 45 of /app/web/modules/contrib/graphql_compose/modules/graphql_compose_menus/src/Plugin/GraphQL/DataProducer/MenuTreeLinkEntity.php)

Seems like the `getEntity()` method is public until D10.2 → and many sites are not ready to move to D10.2

Thanks @CedricL, I'll definitely use it as inspiration and hopefully as a basis for contributing.

mcortes19 → created an issue.

mcortes19 → created an issue.

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

In group v3 the group_content was changed to → group_relationship, also it requires the plugin_id field, so your migration could look like this:

source:
  plugin: d7_node
  node_type: oportunity
process:
  type:
    plugin: default_value
    default_value: program-group_node-opportunity
  plugin_id:
    plugin: default_value
    default_value: group_node:opportunity
  gid:
    plugin: migration_lookup
    migration: groups_audience
    no_stub: true
    source: groups_audience
  entity_id:
    plugin: migration_lookup
    migration: program_node_migration
    no_stub: true
    source: nid
destination:
  plugin: 'entity:group_relationship'

Reviewing the code seems roles are first sorted by scope and then by their weight. not sure if this should change in the future to only use the weight sort