- Issue created by @Anybody
- First commit to issue fork.
- 🇩🇪Germany Grevil
I am quite unsure about this...
So first up, the parent "social" module is not a module, but instead an installation profile. And having a dependency on an installation profile isn't possible. Furthermore, the parent module isn't Drupal 10 compatible.
See the Installation Docs → for more informations.
- 🇩🇪Germany Anybody Porta Westfalica
@Grevil: social is treated like a module. The dependency works.
Indeed, social needs to become D10 compatible, but it will be and is their job. We need this module D10 compatible.
- Open on Drupal.org →Core: 10.1.4 + Environment: PHP 8.1 & MySQL 8last update
about 1 year ago Waiting for branch to pass - @anybody opened merge request.
- last update
about 1 year ago Build Successful - @grevil opened merge request.
- Status changed to Needs review
about 1 year ago 12:44pm 4 October 2023 - 🇩🇪Germany Grevil
Ok, all done! Please review the issue fork's 1.x branch!
- Issue was unassigned.
- 🇩🇪Germany Anybody Porta Westfalica
@Grevil: Thank you, so no other required changes by our tools? Just the .info.yml change?
-
Anybody →
committed 7c96cb99 on 1.x authored by
Grevil →
Issue #3389147: Drupal 10 compatibility
-
Anybody →
committed 7c96cb99 on 1.x authored by
Grevil →
- Status changed to Fixed
about 1 year ago 1:13pm 4 October 2023 - 🇩🇪Germany Anybody Porta Westfalica
Thanks, perfect! Let's merge it!
- 🇩🇪Germany Grevil
social is treated like a module. The dependency works.
But how? It is definitely not defined as one.
Automatically closed - issue fixed for 2 weeks with no activity.