🇪🇸Spain @bletch

jjchinquist → credited bletch → .

jjchinquist → credited bletch → .

dan2k3k4 → credited bletch → .

Correct patch for 10.0.4

Patch for 10.0.4

Here is a patch for 10.3.5

dan2k3k4 → credited bletch → .

dan2k3k4 → credited bletch → .

dan2k3k4 → credited bletch → .

dan2k3k4 → credited bletch → .

Make sure you have the actual correct code from alpha2. If you have a previous version that has been patched it is best to remove and re-require the module (with the patch deleted from composer.json if you no longer need it).

Please ignore my merge request. I realised pretty quickly that the code on my local did not match what was actually in alpha2. When I got the correct code this issue resolved.

bletch → made their first commit to this issue’s fork.

dan2k3k4 → credited bletch → .

dan2k3k4 → credited bletch → .

bletch → made their first commit to this issue’s fork.

Entity usage already does this and we will be transitioning this module to minimal maintenance mode soon in favour of that module. Please look at it.

See 3.0.x-dev branch

merged

D10 branch released

dan2k3k4 → credited bletch → .

I have opened a merge request with the D10 upgrades from rector, along with the following additional fixes:

1. The app.root service has been converted to a container param ( https://www.drupal.org/node/3080612 → )
2. In Symfony 4.0+ you must specif icy your service visibility, otherwise it will be private.

Patch against 2.0-alpha

Thank you!

bletch → made their first commit to this issue’s fork.

bletch → made their first commit to this issue’s fork.

bletch → made their first commit to this issue’s fork.

There has not been any movement on the offer to maintain from mighty_webber. If they no longer want to maintain this module, or if they do not have permissions to opt-in to security coverage then I am happy to take it over as our project uses. I have permissions to opt-in to security coverage.

bletch → made their first commit to this issue’s fork.

bletch → created an issue.

bletch → made their first commit to this issue’s fork.

bletch → created an issue.

bletch → made their first commit to this issue’s fork.

bletch → made their first commit to this issue’s fork.

bletch → made their first commit to this issue’s fork.

bletch → made their first commit to this issue’s fork.

bletch → created an issue.

bletch → created an issue.

Thank you!

Thank you, this is applied.

Thank you, this is applied in 3.0.1

Thank you, this is applied.

Fixed in 3.0.1

Sorry, I forgot to re-open.

Thank you! I don't yet have maintainer access, do I need to do anything else?

Duplicate of https://www.drupal.org/project/projectownership/issues/3237976 →

bletch → created an issue.

I've updated to denote Context v5, would be good to get a Drupal 10 compliant release out. Please let me know if I can do anything else to help.

bletch → made their first commit to this issue’s fork.

Our project uses this module so I am happy to take over maintenance. I have received security coverage opt-in permission.

Please ignore MR 10 & 11 - they went weird. 12 is correct.

bletch → created an issue.

Here is patch for 2.1.0alpha, for people who need it.

I am happy to maintain this as our project wants to continue using it. I have security coverage opt-in permission.

Thx!

Tried to do a quick fork and merge request but my creds are acting up, so here is patch for d10 compatibility.

I am happy to maintain this as our project and org are the main funders. I have security coverage opt-in.

I am happy to take over maintenance of this as we appear to be the only org using it. I have security coverage opt-in.