(v 3.3) update + D10 update error

Did you solve your issue with the upgrade?

We can see in your screenshot that the conflict was caused by the Devel module at version 4.x which is not supported in D10.

You should use version 5.x :

composer require 'drupal/devel:^5.0'

And then try again...

Maybe you already know but you can also use the Upgrade status → module to better plan your upgrade.

@LeDucDuBleuet

Maybe you already know but you can also use the Upgrade status module to better plan your upgrade.

The upgrade status module report says the following
Droopler Profile (droopler)-
Contributed profile Uninstalled 3.1.0 Incompatible N/A 3.3.0-rc1 Incompatible Issues N/A

Why is that?

It is weird because if you followed the update.md instructions, you should have version 3.2.0-rc1 instead of version 3.1.0 in your upgrade status messages and it should say it is installed...

Thank you very much,
I came to the conclusion that the requirements of Droopler 3.3 are lower than those of Drupal 10.
After the corrections, the update went well. Now it works almost fine with Drupal 10.2.-beta2.
There are a few more minor warnings, but they are more related to module errors than Droopler.
Regards

It is weird because if you followed the update.md instructions, you should have version 3.2.0-rc1 instead of version 3.1.0 in your upgrade status messages and it should say it is installed...

@LeDucDuBleuet Thanks. This makes sense. So if I understand correctly, if I follow all the steps mentioned in points 1-6 of updating to 3.2.0 instructions and then run composer update command I should be upgraded to 3.2.0-rc1. Don't we need to make any 3.2.0 related changes to the composer.json before running update command. I mean the update instructions is not very clear. If composer.json needs to be updated/changed before running composer update command then what exactly are the charges that we would need to make to composer.json.

I was of the view that quite a few thing would need to be updated in composer.json including the version of droptica/droopler to 8.3.2.0 and drupal/** to relevant versions.

Same for upgrade from 3.2.0 to 3.3.0 - If composer.json needs to be updated/changed before running composer update command then what exactly are the charges that we would need to make to composer.json.

I can see @pingwin_cracow has made some changes to composer.json in his original post are these all the changes.

Finally at what stage does Drupal Core gets upgraded to version 10. Is it upon running composer update command in version 3.2.0 or 3.3.0.

Simply speaking what are the sequential steps to upgrade droopler and drupal to the latest versions.

You are very right @Aanjaneyam, the update instructions are not very clear. I had to fiddle a bit. In short, I did this.
Drupal 9 - I checked modules that are incompatible with D10 and uninstalled them, or introduced a patch for a given module to avoid a fatal error.
Then I compared the Droopler 3.3 requirements in Droopler's composer.jons and updated the modules version to the versions required by D10.
Next in composer.jons I changed the requirement to "droptica/droopler": "^8.3.3.0", and started the installation on D9. Having Droopler version 3.3 and D9, I changed the requirements to D10 and restarted the installation. It worked. Just in case, after each update I ran update.php to avoid database errors.
If an error occurs during installation, pay attention to which module causes it.
And finally, an important thing - uninstall the Droopler subtheme (if you use it) before installations. After installing Drooplerr 3.3, customize your subtheme to version 3.3 based on Droopler 3.3 Theme. Otherwise, you will initially have an incompatibility conflict between Theme Profile and Droopler's Subtheme.
Good luck and let me know how it goes.
Regards.

@pingwin_cracow many thanks for the reply. I was wondering if you could share the final updated version of your composer.json.

Also, how did you update from droopler 3.1.0 to 3.2.0-rc1. The update instructions says uninstall modules lazy and rdf. However, they appear to to be uninstallable because so many droopler and other modules depend upon these two modules. Could lazy and rdf be forcefully uninstalled and if they can be would this un-installation break something else making the upgrade more difficult.

{
"name": "droptica/droopler-project",
"description": "Project template for Droopler with Composer",
"type": "project",
"license": "GPL-2.0-or-later",
"homepage": "https://www.droopler.com",
"support": {
"docs": "https://www.droopler.com/developers",
"issues": " https://www.drupal.org/project/issues/droopler?categories=All → "
},
"repositories": {
"drupal": {
"type": "composer",
"url": "https://packages.drupal.org/8"
},
"asset": {
"type": "composer",
"url": "https://asset-packagist.org"
}
},
"require": {
"composer/installers": "^2.0",
"cweagans/composer-patches": "^1.6",
"dompdf/dompdf": "^1.0.2",
"droptica/droopler": "^8.3.3.0",
"drupal/core-composer-scaffold": "^10.2",
"drupal/core-recommended": "^10.2",
"drupal/csv_serialization": "^4.0",
"drupal/eca": "^1.1",
"drupal/inline_entity_form": "^1.0@RC",
"drush/drush": "^12.0",
"oomphinc/composer-installers-extender": "^2.0",
"phpmailer/phpmailer": "~6.1",
"phpoffice/phpword": "v0.18.*",
"zaporylie/composer-drupal-optimizations": "^1.1"
},
"require-dev": {
"drupal/core-dev": "^10.2"
},
"conflict": {
"drupal/drupal": "*"
},
"minimum-stability": "dev",
"prefer-stable": true,
"config": {
"sort-packages": true,
"allow-plugins": {
"dealerdirect/phpcodesniffer-composer-installer": true,
"composer/installers": true,
"cweagans/composer-patches": true,
"drupal/console-extend-plugin": true,
"drupal/core-composer-scaffold": true,
"oomphinc/composer-installers-extender": true,
"zaporylie/composer-drupal-optimizations": true,
"drupal/core-project-message": true,
"drupal/core-vendor-hardening": true,
"phpstan/extension-installer": true,
"php-http/discovery": true
},
"preferred-install": {
"droptica/droopler": "source",
"*": "dist"
}
},
"extra": {
"enable-patching": true,
"drupal-scaffold": {
"locations": {
"web-root": "web/"
}
},
"installer-types": ["bower-asset", "npm-asset"],
"installer-paths": {
"web/core": ["type:drupal-core"],
"web/libraries/{$name}": ["type:drupal-library", "type:git", "type:bower-asset", "type:npm-asset"],
"web/modules/contrib/{$name}": ["type:drupal-module"],
"web/profiles/contrib/{$name}": ["type:drupal-profile"],
"web/themes/contrib/{$name}": ["type:drupal-theme"],
"drush/Commands/contrib/{$name}": ["type:drupal-drush"],
"web/modules/custom/{$name}": ["type:drupal-custom-module"],
"web/themes/custom/{$name}": ["type:drupal-custom-theme"]
}
}
}

this is my composer.json file.
I don't remember exactly in what order I uninstalled lazy and rdf.
You definitely need to check the editor's text format settings and turn off lazy in each profile.
.../admin/config/content/formats
Try to install Droopler 3.2 and only after Droopler updates the requirements will you be able to uninstall lazy.
Rdf is in core D9, it is removed automatically by D10 during update. It does not need to be removed manually with Droopler 3.2 - it is not necessary.

@pingwin_cracow many thanks. Much appreciated.