Hi,

Should this project in my 'requires' list be removed using Composer?
"drupalcommerce/commerce_base": "dev-8.x-1.x",

The Upgrade Status module reports that "Commerce Base" is in the files structure but not installed and suggests removing it.

Upgrade Status Module Report

My original Drupal 8 install was with Composer using:
composer create-project drupalcommerce/project-base XXXXXX --stability dev

I presently have Commerce 8.x-2.26 installed.

I'd like to upgrade to from Drupal 8.9.x to 9.2.x.

My current composer.json attached.

Thank you!

Issue fork commerce-3229867

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

mlecha created an issue. See original summary.

jsacksick’s picture

Status: Active » Closed (won't fix)

With the abundance of support available in Drupal Answers, the Drupal focused Stack Exchange site, we are no longer answering support requests in the issue queue.

Support requests opened here will be closed (won't fix), so please search for existing answers or post new questions at:

https://drupal.stackexchange.com (using the drupal-commerce tag)

firfin made their first commit to this issue’s fork.

firfin’s picture

The question in stack exchange is here:
https://drupal.stackexchange.com/questions/305842/should-i-remove-commer...

Unfortunately there are no answers there either. And the answer is not clear from documentation either. Some help would be greatly appreciated.

firfin’s picture

Status: Closed (won't fix) » Active

I think this deserves some attention. Many commerce sites were created using the 'project-base' on D8 and now need to be updated to D9.
Some best practice advice would be a great start.
The docs just state some info about updating Drupal Core, nothing about updating project-base itself or it's commerce_base requirement.

To me (and others apparently) it is unclear on how to proceed with updating.

jsacksick’s picture

Status: Active » Fixed

drupalcommerce/project-baseis a composer template, it isn't a module... It shouldn't be required in your composer.json.

firfin’s picture

So drupalcommerce/commerce_base is a requirement in project composer.json files which are based of the drupalcommerce/project-base template.

As far as I understand it, commerce_base is installed as an installation profile, not as a module. That is why it shows up in the 'Upgrade status' as not installed, I presume. It is probably just best to ignore this?

Also messages about swiftmailer (required by commerce_base) are generated, but this will sort itself out magically at some point in the future I suppose? With some future version of commerce_base.

firfin’s picture

profiles were not treated correctly by the upgrade_status module. This is fixed in #3230266: Custom install profile is reported as an extension that should be uninstalled due to core bugs

So you can try the patch from that issue, or wait for a new release which includes the patch.

Status: Fixed » Closed (fixed)

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

seorusus’s picture

StatusFileSize
new1.52 KB

This patch fixes the deprecated constant USER_REGISTER_VISITORS_ADMINISTRATIVE_APPROVAL
and adds Drupal 9 compatibility to the commerce_base profile.