- 🇺🇸United States Douglas Marsh
What is preventing this fix merged into a new release?
--Doug
- 🇳🇱Netherlands roderik Amsterdam,NL / Budapest,HU
1. Work/personal time intermixed stuff (this module is unpaid/volunteer work from my side vs. free time vs. other volunteer projects that are running out vs. currently the need to concentrate on trying to get some paid work again, hopefully Drupal related)
2. My tingling sense that this is not the last bug remaining but that there's a D10 compatibility issue hidden in an event subscriber (to be more exact: class naming that isn't correct anymore for the new Symfony version) that was never addressed
(Yes, this module should get real test coverage to prevent stuff like this. That would take a lot of effort.)
3. Stubbornness from my side; not wanting to continue a string of rushed releases that I do not personally know are really D10 compatible.
I know it's getting ridiculous because it's been over a year. (Last time I really looked at this module was June 2022 / D9-only v3.5).
Tell me if you can't live with patches. Otherwise: likely ~12-14 days from now.
[ Linking other/duplicate issue ]
- Status changed to Fixed
11 months ago 8:38pm 26 July 2023 - 🇳🇱Netherlands roderik Amsterdam,NL / Budapest,HU
Urgh: this was caused by the confusing D10 upgrade pushed out in v8.x-3.7.
And the other thing "hidden in an event subscriber" which I mentioned, does not need work. (It was already fixed / the changed Symfony class name was already compatible from D9.2+.)
Oh well. I finally have a well working local development environment (which is a must with this module), and I plan to work more on issues soonish. But first, a release that contains this fix.
Automatically closed - issue fixed for 2 weeks with no activity.