πŸ‡ΊπŸ‡¦Ukraine @solariel

Account created on 25 February 2015, about 10 years ago
#

Recent comments

πŸ‡ΊπŸ‡¦Ukraine solariel

Updated patch #23 to apply on latest core version

πŸ‡ΊπŸ‡¦Ukraine solariel

Nope, it isn't related.
In πŸ› ResourceTypeRepository wrongly assumes that all entity reference fields have the setting "target_type" Fixed they have added the \Drupal\Core\Field\Plugin\Field\FieldType\EntityReferenceItemInterface that has a static getReferenceableBundles() method.

\Drupal\Core\Field\Plugin\Field\FieldType\EntityReferenceItem implements that method with using 'target_type' option.

Your class DynamicEntityReferenceItem inherits that method but it won't work for dynamic reference since it doesn't have a 'target_type' option.

The issue you've linked is another core issue related to dynamic entity reference support.

This one is about your module having to adapt to solution provided in #3057545

πŸ‡ΊπŸ‡¦Ukraine solariel

Unfortunately, this is tied to how drupal.org automatically injects composer requirements by checking the .info.yml of the module. Until maintainers update the info file noone will be able to do anything. For now the only way to install h5p on D10 is manually with applying patches from https://www.drupal.org/project/h5p/issues/3329297 πŸ“Œ Automated Drupal 10 compatibility fixes Needs review

Production build 0.71.5 2024