#ProjectUpdateBotD11

Applied updates from the bot. Have not tried this on D11 yet, so will leave this open, but can confirm that upgrade status only reported that D11 compatibility only needed the version requirement added.

Automated updates appear to work as-is. Merged this in and tagged a release.

The 3.x-dev branch now has the 4.6 code in place for anyone wanting to give that a try.

Hello. I have added a new commit doing what was requested in comment #6. The pipelines have passed. I await review. Thank you.

Hello! Is there released date set for this?

Automatically closed - issue fixed for 2 weeks with no activity.

Automatically closed - issue fixed for 2 weeks with no activity.

Automatically closed - issue fixed for 2 weeks with no activity.

Automatically closed - issue fixed for 2 weeks with no activity.

Automatically closed - issue fixed for 2 weeks with no activity.

Hi!
is it possible that this will be committed in the development branch?

@pminf for now, you can use the development (2.0.x-dev) version if you need to use Seven on Drupal 11, until a new release for d11 comes out

First step toward this is 📌 Fix head tests or fix related functionality if necessary Active

@joseph.olstad

Any update on a D11 compatible version?

Patch for 2.0.2 since there's no D11 version yet

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

Could you please release a Drupal 11 compatible version including this fix?

Automatically closed - issue fixed for 2 weeks with no activity.

Thank you maxilein I will get it released next week.

trackleft2 → changed the visibility of the branch 3431824-2-0-x to hidden.

trackleft2 → closed merge request !18

Thank you for your interest in contributing to this module, however, your merge request targets an unsupported branch, for this reason I am closing your merge request as won't fix.
Also, this issue is meant for the project update bot to use.

Merging, thanks bot!

I have merged the code changes that provide compatibility with Drupal 10, 11, and future releases. Thanks.

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

Can you please make a Drupal 11 version.

Patch #7 wouldn't apply

Automatically closed - issue fixed for 2 weeks with no activity.

Thanks plopesc

smustgrave → closed merge request !13

smustgrave → closed merge request !14

The last patch made the module pass D11 testing but it actually broke the adding of any new fields to any content type due to a D11 different expectation on field declaration.

This fixes that, and now fields can be added.

As for the module's functionality in D11 itself, this is working for me (with this patch) except that tabledragging the references breaks due to some malformed markup (as expected by a stricter tabledrag.js in D11) created by this module. This isn't an issue for me (you can use the order field) so I'm running with it.

I just wanted to share this in case others need it.

Automatically closed - issue fixed for 2 weeks with no activity.

earlyburg → closed merge request !2

astonvictor → closed merge request !15

This was already fixed in version >2.2.0

saidatom → changed the visibility of the branch project-update-bot-only to hidden.

any chance for update?

Added tests and fixed the super obvious issues called out by the testbot. Mainly by running phpcbf and fixing a few obvious spellings. All this so we can be sure the quality of the D11 port is actually there.

This is broken in the SettingsForm constructor.

The upstream dependency is no longer blocking.

I think the gitlab ci file was not according to standards in the merge request, so I put in the correct one.

Also it is time to switch to the semver version, especially as we change the drupal core requirement to 10 and 11, then usually we would create a new branch anyways.

This is now fixed on the 2.0.x branch.

dieterholvoet → credited klaas → .

Static patch of MR4

The changes with dependency injection have already been included and are ready to be reviewed by the community:

• Merge request: !38
• Patch: https://git.drupalcode.org/project/prevnext/-/merge_requests/38.patch

Ready to check!

Add compatibility with video embed field beta

I've fixed the composer.json too. Waiting for tests to move to RTBC.

Can we not delete all comments that explain what's going on in the code?
Also I see interface method docs are replaced by @inheritdoc. Since it's an interface that defines those methods, what is it that we inherit from?

realityloop → changed the visibility of the branch drupal11 to hidden.

Very minimal code here. Nothing raises red flags and the project update bot did not raise anything else either.

This looks RTBC to me.

MR!7 has been merged. This contains the || ^11 from #2.

MR!10 contains the patch at #6. This is code for the Tests, but the CI is not configured for to run them. One of the maintainers should have the access to do that though.

Looking at MR!10 it's a standard pattern for D11 upgrades on tests.

Practical testing shows this is working on 10.4.8 and Rector raised no other red flags for D11.

This would get my RTBC.

Automatically closed - issue fixed for 2 weeks with no activity.

You're welcome.
Please leave this issue open.

Automatically closed - issue fixed for 2 weeks with no activity.

@sanduhrs, thank you:)

I'm changing the issue's status as fixed.

@kopeboy you can do that by using the issue's fork, see https://blog.riff.org/2025_01_03_how_to_use_modules_or_themes_not_yet_av... for doc.
I have some modules in production, using this approach --- and I will use it as well for this one, as now, I need this module.

done :)

any chance for merge?

Do you mean a new release?

Any chance of a D11, Commerce 3 release for this module?

Merged to branch 8.x-1.x

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

Automatically closed - issue fixed for 2 weeks with no activity.

Automatically closed - issue fixed for 2 weeks with no activity.

works as expected. please promote a release!

Automatically closed - issue fixed for 2 weeks with no activity.

Automatically closed - issue fixed for 2 weeks with no activity.

Committed to branch 2.0.x

jayelless → changed the visibility of the branch 3527591-automated-drupal-11 to hidden.

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