🇺🇸United States @droath

droath → created an issue.

@Vacilando

Could you please provide more details on when you encounter that error? I am unable to replicate it. The patch that has been merged appears to be functioning correctly for me on a fresh Drupal installation.

droath → created an issue.

droath → created an issue.

droath → created an issue.

Thank you for the patch; it has been merged into the development release.

This looks to be a duplicated issue, that is related to https://www.drupal.org/project/entity_extra_field/issues/3385923 🐛 Extra field is rendered outside field_goup details field group Fixed .

It makes sense that it doesn't work with Paragraphs entities, as they have their own solution different from what Drupal core offers out of the box. I can look into what it might take to get this to work with paragraphs on the edit screen, but it's going to be lower on the priority list as we're trying to get a stable release in the coming months.

I believe this is a duplicated issue: https://www.drupal.org/project/entity_extra_field/issues/3334147 🐛 Empty content view Fixed

Thank you, it has been patched in the dev release and will be pushed to the RC shortly

Thank you, it has been patched in the dev release and will be pushed to the RC shortly

@jnettik

I have made the changes as outlined so that any entity extra field plugin type can utilize the data attached to the extra field object. I am concerned that this patch might cause issues for existing sites that rely on the block ID instead of using the entity field name. Are you willing to test this patch to ensure it works for your problem?

I encountered an issue where I received an error message like the following:

Warning: Undefined array key 0 in Drupal\views_argument_token\Plugin\views\argument_default\TokenArgument->processToken() (line 426 of modules/contrib/views_argument_token/src/Plugin/views/argument_default/TokenArgument.php).

It was an easy change in the patch to address to ensure we don't process any empty arrays. The updated patch has been attached.

droath → created an issue.

@jnettik

I had a similar issue, and I was able to use this patch to address those issues.

https://www.drupal.org/project/mercury_editor/issues/3401444 🐛 Entity Browsers within paragraphs don't reliably select entities Active

I was able to resolve this bug when using the following patch for the domain module:

https://www.drupal.org/project/domain/issues/3226427#comment-15104156 🐛 Arbitrary null value from DomainNegotiator::getActiveDomain() Needs review

droath → created an issue.

droath → created an issue.

Here is a reroll of the patch for the latest release.

droath → created an issue.

@mauzilla

This seems to be a typical problem in Drupal. I suggest checking out this Stack Exchange for guidance on fixing a mismatched entity and/or field definitions error in your configuration. Personally, I have used the Devel Entity Updates → module to successfully resolve similar issues.

droath → created an issue.

The patch didn't work to resolve the error. I ended up trying a different approach, which seems to have resolved the issue.

I've created and deployed another tagged release.

After conducting some research, it appears that this issue is not specific to ME but rather stems from improper configuration settings.

droath → created an issue.

droath → created an issue.

Thanks for reporting. I modify the code to utilize NULL, which appears to be functioning correctly and should remain functional even if the referenced patch is implemented.

droath → created an issue. See original summary → .

Yes @irinaz , I have just completed the creation of an alpha 3 release that incorporates all the changes for Drupal 10, including this particular commit as well!

droath → created an issue.

While dealing with a related issue, I realized the importance of conducting an access check. Personally, I believe it would be more logical to perform this check early in the process. Surprisingly, as I worked on resolving this matter, it also ended up indirectly addressing the problem discussed in this thread.

https://www.drupal.org/project/flag/issues/3383006 🐛 Missing Access Control Check Prior to Rendering Link Active

droath → created an issue.

droath → created an issue.

droath → created an issue.

Thanks for the patch, it's been committed to the dev branch. I'll do a tagged release soon after.

Thanks for the patch, it's been committed to the dev branch. I'll do a tagged release soon after.

Thanks for the patch, it's been committed to the dev branch. I'll do a tagged release soon after.

I was able to resolve this bug using the following code, my particular use case was related to ctools:

/**
 * Implements hook_condition_info_alter().
 */
function HOOK_condition_info_alter(array &$definitions) {
  if (!isset($definitions['node_type'])) {
    $definitions['node_type']['class'] = EntityBundle::class;
  }
}

droath → created an issue.

Thanks for the patch, this has been merged into the 2.x dev branch.

Thanks for the work on this, I was able to review and made minor changes/additions to this feature. It's now apart of the 2.x dev branch and will be merge in the coming days if no issues have been reported.

Thanks @asherry! It's been merged and released in the 2.x branch.

droath → created an issue.

droath → created an issue.

I've added token support for props/slots in the module. Let me know if there is anything else that should be accounted for.

droath → created an issue.

I was able to resolve this issue, it was related to lando configs.

droath → created an issue.