Correct path to upgrade to Drupal 10

Thanks, Gabriele for following up on the subject

Working on #3391543: Plan: Release Varbase 9.0.16 →

For sure you can start the testing upgrade process

Drupal 9 support will end in November 2023 →

November 1, 2023 (UTC) Drupal 9 reaches end-of-life due to its dependency on Symfony 4.
Reference: Symfony 4.4 release checker.
What to do about Drupal 9's end of life in November 2023

Drush 11 support will end in November 2023

We are ready to upgrade any Varbase 9.0.x site to Drupal ~10.1.0
No need to wait on #3391543: Plan: Release Varbase 9.0.16 →

Hello Rajab, thank you for your quick reply!

I'm trying to follow your instructions but first time I run "composer update" I get the following error:

...
 88/97 [=========================>--]  90%  - Installing drupal/varbase_landing (dev-9.0.x 73524c5): Cloning 73524c5be2 from cache
  - Installing drupal/varbase_heroslider_media (dev-9.0.x 1b82cdf): Cloning 1b82cdf85b from cache
  - Installing drupal/varbase_email (dev-9.0.x d12d01d): Cloning d12d01d7d7 from cache
  - Installing drupal/varbase_core (dev-9.1.x ae189d8): Cloning ae189d8e7c from cache
  - Installing drupal/varbase_carousels (dev-9.0.x 053b9de): Cloning 053b9de21d from cache
  - Installing drupal/varbase_blog (dev-9.0.x bad40cc): Cloning bad40ccc11 from cache
  - Installing drupal/varbase_auth (dev-9.0.x f8fa06c): Cloning f8fa06c0a6 from cache
  - Installing drupal/varbase_api (dev-9.0.x 74c6cad): Cloning 74c6cad928 from cache
 97/97 [============================] 100%
In FilesystemRepository.php line 163:
                                                                                                                                                               
  file_get_contents(/var/www/d10/vendor/composer/composer/src/Composer/Repository/../InstalledVersions.php): Failed to open stream: No such file or directory   

Running "composer update" again doesn't help:

golem@t140:/var/www/d10$ composer update
PHP Warning:  require(/var/www/d10/vendor/composer/../longwave/laminas-diactoros/src/functions/create_uploaded_file.php): Failed to open stream: No such file or directory in /var/www/d10/vendor/composer/autoload_real.php on line 82
PHP Fatal error:  Uncaught Error: Failed opening required '/var/www/d10/vendor/composer/../longwave/laminas-diactoros/src/functions/create_uploaded_file.php' (include_path='/var/www/d10/vendor/pear/archive_tar:/var/www/d10/vendor/pear/console_getopt:/var/www/d10/vendor/pear/pear-core-minimal/src:/var/www/d10/vendor/pear/pear_exception:.:/usr/share/php') in /var/www/d10/vendor/composer/autoload_real.php:82
Stack trace:
#0 /var/www/d10/vendor/composer/autoload_real.php(65): composerRequirea04b5b931443125d9f9e6084e5fef0b5()
#1 /var/www/d10/vendor/autoload.php(7): ComposerAutoloaderInita04b5b931443125d9f9e6084e5fef0b5::getLoader()
#2 /var/www/d10/vendor/composer/composer/src/bootstrap.php(17): include('...')
#3 /var/www/d10/vendor/composer/composer/src/bootstrap.php(20): includeIfExists()
#4 /var/www/d10/vendor/composer/composer/bin/composer(19): require('...')
#5 /var/www/d10/vendor/bin/composer(120): include('...')
#6 {main}
  thrown in /var/www/d10/vendor/composer/autoload_real.php on line 82

I deleted my original composer.json file, downloaded https://github.com/Vardot/varbase-project/blob/9.0.x/composer.json, added under "require" section the modules that I need and corrected any "docroot" instance (webroot here is "public_html") .

Any suggestion? Thanks a lot in advance

Sorry, my fault: I had "export PATH="./vendor/bin:$PATH"" in .bashrc (to easily run drush), so I was using version 2.2.2 of composer (from ./vendor/bin) instead of the updated one (2.6.5)

Once disabled a few modules that were crashing "drush updatedb" (namely "Simple entity merge" and "Snowball stemmer") everything worked like a charm!

I have another two sites to update, and they are more complex but I'm now confident that it can be done without too much effort.

Thanks a lot again!

I forgot to report the only warning I got during the update process:

[notice] The role Site Admin has had the following non-existent permission(s) removed: userprotect.protected_site_admin.bypass.
[notice] The role Site Admin has had non-existent permissions removed. Check the logs for details.

I don't know what it means, but might be of your interest.

Permissions must exist →

Invalid permissions will trigger runtime exceptions in Drupal 10 → . Permissions should be defined in a permissions.yml file or a permission callback.

The skip_missing_permission_deprecation flag that was added in Drupal 9 to the Role entity in #2571235: [regression] Roles should depend on objects that are building the granted permissions → .

Modules cannot be in a disabled state anymore, only installed and uninstalled →
#1199946: Disabled modules are broken beyond repair so the "disable" functionality needs to be removed →

  # A special flag so we can migrate permissions that do not exist yet.
  # @todo Remove in https://www.drupal.org/project/drupal/issues/2953111.
  skip_missing_permission_deprecation:
    plugin: default_value
    default_value: true

It was removed from the 10.0.x and 10.1.x branch.

#2953111: Only migrate role permissions that exist on the destination →

• Issue #3344805 → : Added Permissions for user roles to Varbase Core from scanned config/permissions directory
• Issue #3344813 → : Added Permissions for user roles to Varbase Media from scanned config/permissions directory
• Issue #3344807 → : Added Permissions for user roles to Varbase Editor from scanned config/permissions directory
• Issue #3344811 → : Added Permissions for user roles to Varbase Layout Builder from scanned config/permissions directory
• Issue #3344791 → : Added Permissions for user roles to Varbase API from scanned config/permissions directory
• Issue #3344818 → : Added Permissions for user roles to Varbase Social Single Sign-On from scanned config/permissions directory
• Issue #3344801 → : Added Permissions for user roles to Varbase Carousels from scanned config/permissions directory
• Issue #3344808 → : Added Permissions for user roles to Varbase Email from scanned config/permissions directory
• Issue #3344810 → : Added Permissions for user roles to Varbase Landing Page (Paragraphs) from scanned config/permissions directory
• Issue #3344800 → : Added Permissions for user roles to Varbase Bootstrap Paragraphs from scanned config/permissions directory
• Issue #3344821 → : Added Permissions for user roles to Varbase Workflow from scanned config/permissions directory
• Issue #3393952 → : Added Permissions for user roles to Varbase Total Control Dashboard from scanned config/permissions directory
• Issue #3341637 → : Added permissions to the SEO Admin user role for Varbase Dashboards default dashboard

Hi Rajab,

I've now successfully upgraded all my Vardot based Drupal 9 sites to Drupal 10, using https://github.com/Vardot/varbase-project/blob/9.0.x/composer.json as a model. But now updating again fails:

- drupal/varbase_workflow dev-2.0.x requires drupal/core ~9 -> found drupal/core[9.0.0-alpha1, ..., 9.5.x-dev] but it conflicts with your root composer.json require (~10.1.0).
- vardot/varbase 9.0.x-dev requires drupal/varbase_workflow 2.0.x-dev -> satisfiable by drupal/varbase_workflow[2.0.x-dev (alias of dev-2.0.x)].
- drupal/varbase_workflow 2.0.x-dev is an alias of drupal/varbase_workflow dev-2.0.x and thus requires it to be installed too.
- Root composer.json requires vardot/varbase 9.0.x-dev -> satisfiable by vardot/varbase[9.0.x-dev].

I guess I need to update varbase_workflow, but to which version?

Not to use the 9.0.x-dev version of Varbase
the right one is ~9.0 as in

https://github.com/Vardot/varbase-project/blob/9.0.16/composer.json

Updated the docuentation for that

#3401786: Plan: Release Varbase 9.0.17 →

In some cases modules have custom config, code, logic for Drupal ~10, which differ from Drupal ~9

Facing issues like:
🐛 Fix Drupal core content moderation to prevent old revisions from becoming default on re-save Active
🐛 Revision user incorrectly appears as anonymous user when node author is cancelled Needs work
🐛 Content moderation can wrongly set old revisions as default when they're resaved Needs review
📌 Fix editing and viewing paragraphs issues of incorrect revision of its parent when content moderation is involved Needs review
🐛 Paragraph access check using incorrect revision of its parent, leading to issues editing and viewing paragraphs when content moderation is involved. Needs work
Which they needs fixes for Drupal 9 and other fixes in Drupal 10

To follow with that
📌 Start a 9.1.x branch for Varbase Social Single Sign-On to support Drupal ~10 and drop support for Drupal ~9 Fixed

Doing that in all Varbase modules
📌 Revamp the 9.1.x branch for Varbase Media Header to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9 Fixed
📌 Revamp the 9.1.x branch for Varbase Style Guide to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9 Fixed
📌 Revamp the 9.1.x branch for Varbase Landing Page (Paragraphs) to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9 Fixed
📌 Revamp the 9.1.x branch for Varbase Media to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9 Fixed
📌 Revamp the 9.1.x branch for Varbase Media Hero Slider to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9 Needs review
📌 Revamp the 9.1.x branch for Varbase Email to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9 Fixed
📌 Revamp the 9.1.x branch for Varbase Carousels to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9 Fixed
📌 Revamp the 9.1.x branch for Varbase Blog (Corporate Blog) to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9 Fixed
📌 Start a 9.1.x branch for Varbase Total Control Dashboard to support Drupal ~10 and drop support for Drupal ~9 Fixed
📌 Start a 9.1.x branch for Varbase SEO to support Drupal ~10 and drop support for Drupal ~9 Fixed
📌 Start a 9.1.x branch for Varbase Search to support Drupal ~10 and drop support for Drupal ~9 Fixed
📌 Start a 9.1.x branch for Varbase API to support Drupal ~10 and drop support for Drupal ~9 Fixed
📌 Start a 9.1.x branch for Varbase Social Single Sign-On to support Drupal ~10 and drop support for Drupal ~9 Fixed

Doing one more full testing round before releasing Varbase 9.0.17 and Varbase 9.1.0

Thank you Rajab,

I corrected composer.json, ran update script and successfully upgraded to drupal/core ver. 10.1.6 and vardot/varbase 9.0.16. But now I see this error while running drush updb:

[error]   (Currently using Incompatible module The following module is installed, but it is incompatible with Drupal 10.1.6:  
* Entity Browser Generic Embed

Thanks a lot for your patience!

Thanks, Gabriele for reporting the "Currently using Incompatible module The following module is installed, but it is incompatible with Drupal 10.1.6" issue

✅ Released varbase_media-9.0.37 →
✅ Released varbase_media-9.1.1 →

varbase_media-9.1.0, varbase_media-9.1.1

• Issue #3403763 → : Revamped the 9.1.x branch for Varbase Media to work with Drupal ~10 for a smoother upgrade process and drop support for Drupal ~9

varbase_media-9.0.36, varbase_media-9.0.37

• Issue #3403763 → : Changed drupal/core to ~9 in the .info.yml and composer.json files in the 9.0.x branch

#3401786: Plan: Release Varbase 9.0.17 →

By the way, thanks for your follow up and listing of issues!
Updating the documentation and codebase as we go

All old Varbase 9.0.x sites are ready to upgrade to Drupal ~10 with Varbase 9.1.x

To update the documentation too.
After the release of Varbase 9.1.0

Hi, Rajab!
Let me first thank you for your efforts and so nice distribution!

As I see Varbase 10.0.0-rc1 was released yesterday, but it is still stated:
"Only for testing!. Do not use in production or live sites yet!."

Should I wait for another Drupal 10 version, that could be used in production?

almador, Thanks for following up on Varbase 10

Drupal 10.2.0, 10.2.1, and 10.2.2 were released with some changes
Varbase 10.0.0 stable is around
#3413373: Plan: Release Varbase 10.0.0 →

Doing the final full testing rounds and pug fixes before the release
By the way we are doing micro releases for Varbase Modules.