Cannot upgrade Drupal to 10

Hello. Any tips to upgrade Drupal Core after applying this patch ? Trying a mass "composer update" without effect.

As this change is touching the dependency composer.json file, it cannot be applied as a patch. Find out why https://github.com/cweagans/composer-patches/tree/1.x#patches-containing.... Temporary, you should use directly the branch from the MR

As blocks upgrading to the recommended stable Drupal core, I think it’s critical

Drupal 9.4 is still an active version, even if it isn't the latest and greatest. I've been working with Opigno for 4 years, and they always wait until the last possible minute to release a new version with a Drupal upgrade.

If you're feeling really antsy, you can use Composer aliases to upgrade past the Opigno requirements.

This need to be updated to either 9.5 or 10 as the active support is already ended and security support if about to end in June 21.

https://endoflife.date/drupal

I think the best solution is to remove the constraint from composer.json and rely on .info.yml file

I subscribe to this issue and also think it's critical due to 9.5.8 is a security update: https://www.drupal.org/project/drupal/releases/9.5.8 →

There's no 3.x-dev package so we cannot set the correct issue version. Moved to 3.1.0 and changing the title as the latest version allows Drupal 9.5.

I have this rebased to be able to merge, it will also download with composer for me

I have made some more work done with this but there are still a number of modules that are dependent which aren't upgraded to Drupal 10 yst, and Did get it installed in Drupal 9 and tested enough to know that this isn't really going to do what we need, it seems to have many features that we don't need and is just to feature heavy for what we want.

If you really want to upgrade to d10, think again. Because the private message module(3.x) is a complete disaster. The last messages you sent do not appear in the stream. You must refresh the page after each message. You cannot tell this to your members. Load previous message button is not working. You cannot list previous messages.
If the private message is important to you, I suggest you think again.

5 days to Drupal 9 end of life. Any updates?

My client is asking for advice on the timings for Opigno's move to Drupal 10. Any updates on this?
Thanks.

Sorry, this is still a bug

Hi @axelm that's great to hear, thanks for the update

Hey @axelm and everyone, any update on the upgrade and can someone help with any workaround. I tried with the pulling the patch from the PR. Its not working.

Is the Drupal 10 release still on schedule for release by year-end? It's the holidays and need to schedule time and resource, or not.

Is Drupal 10 still a go for the end of the year? We want to decide between Drupal + Moodle or Drupal + Opigno but we don't want to use the EOL version 9 of Drupal.

Hi everyone,
Unfortunately we still couldn’t find time to push a stable d10 release on Drupal.org.
It will be done in January.
Happy holidays !

Do we have any date on which it will be done on January? It is stopping us to move to Drupal 10.

Yes, a date would be great. Also, does someone monitor the contact forms? We are interested in a support contract.

Hi @nikolaimanek
Unfortunately we are not able to provide a precise date at the moment.
We commit to precise dates with your customers, and we will do the deployment on Drupal.org when we will have time.
One of our representatives will contact you early next year.
Best wishes,

Any update for the Drupal 10 compatible release?

12/23: “Unfortunately we still couldn’t find time to push a stable d10 release on Drupal.org. It will be done in January, for sure !”
So, by wednesday?

Can you please give us a realistic date as to when this will happen?

Any updates on this?
Thanks.

I sympathize with the struggles you all must be having, especially with the way the Groups module has changed.

Our client's security policy requires us to make the update to Drupal 10, which will require an update to Groups module because of other systems on the site .

From other projects, we know that the Groups module version being used in Opigno on the 3.1 version is no longer the recommended version to use going forward and that users should move to Groups version 2 if they are using Groups already, and using Groups 3 if there is a fresh install.

Can you please let us know what version of the Groups module the next version of Opigno will ship with?

Hi @sascher
It will be Group 1.6.
Update to 2.2 is theoretically possible, but the name of content types were changed.
This would consequently require some additional work (to some already complex port from Drupal 9 to Drupal 10) and extensive testing, so Opigno 3.2 (Drupal 10) will start with Group 1.6 (that is still supported with Drupal 10).
Then we will work on upgrade to Group 2.2.

That makes sense, thank you for answering my question. @axelm

The upgrade to Groups can be a tough one for sure. We had to upgrade the groups module to version 2 on another project because we kept getting errors when upgrading to Drupal Core 10.2.2.

Could you please let us know what version of Drupal core you all plan to have Opigno 3.2 ship with?

Hi @sascher
It should be 10.2.x (10.2.2 or more recent)

Hi @axelm - great to see you here again. Any chance of a best case/worst case timeline?

Hi @jackradford
We don't want to announce some precise timeline since many different factors are involved, and not being able to meet the announced timeline would then generate some frustration, which I can understand.
What I can say for sure is that we are actively working on it and getting closer, and we are trying our best to make it happen as soon as possible.

Hi @axelm

Can you provide an update as this is really not moving forward.

Nevuary.

@jive01

There is a fork : https://www.drupal.org/project/lms →

But it's in early development.

That LMS is not a fork, but a whole new project.

Drupal 10 compatible 3.2.7 has been released. With this release, setting to Needs Review to get community feedback to ensure Drupal 9 sites are now able to upgrade to Drupal 10 to close out this issue.

Congrats, will be reviewing over the next couple of weeks