- Issue created by @SirClickALot
- First commit to issue fork.
-
sanduhrs →
committed 3f83df95 on 1.0.x
Issue #3411993 by sanduhrs: Missing drupal/webfinger after module update...
-
sanduhrs →
committed 3f83df95 on 1.0.x
- Status changed to Fixed
over 1 year ago 6:41pm 4 January 2024 - 🇩🇪Germany sanduhrs 🇪🇺 Heidelberg, Germany, Europe
Committed to -dev, fixed in next release.
Thanks for reporting. -
sanduhrs →
committed 4718c9c1 on 1.0.x
Issue #3411993 by sanduhrs: Missing drupal/webfinger after module update...
-
sanduhrs →
committed 4718c9c1 on 1.0.x
- Status changed to Needs work
about 1 year ago 11:05pm 9 January 2024 - 🇨🇦Canada noah
I was still seeing the error with 1.0.11, because although
drupal/webfinger
was being downloaded (thanks to the dependency added in this issue), the module was not enabled so none of the referenced methods were available. I was able to get the site working again by following @SirClickalot's instructions re: commenting out the service inattribution.services.yml
, manually enabling the Webfinger module, and then re-enabling the service.Unless I've missed something about how this should work, I think the Webfinger module should be listed as a dependency in
attribution.info.yml
, no? And I think there should be anattribution.install
file with a hook to ensure that the Webfinger module is enabled. I'd be up for making these updates, however I'm not even sure that will do it since the error here is preventing database updates from running (so the "enable Webfinger" hook won't run because of the error caused by Webfinger not being enabled)—I'm not sure how to work around that. -
sanduhrs →
committed 24928aa4 on 1.0.x
Revert "Issue #3411993 by sanduhrs: Missing drupal/webfinger after...
-
sanduhrs →
committed 24928aa4 on 1.0.x
- Status changed to Fixed
about 1 year ago 5:24pm 11 January 2024 - 🇩🇪Germany sanduhrs 🇪🇺 Heidelberg, Germany, Europe
The webfinger support has been reverted FTTB.
Thanks for reporting! Automatically closed - issue fixed for 2 weeks with no activity.