commerce_kickstart.profile currently has code (from the 1.x days) that modifies the behavior of the update manager.

That code does the following:
1) Hide all modules that ship with Kickstart (unless they have already been manually updated), so that the user doesn't get the idea he should update them one by one (which breaks the install).
2) Show the update status of Kickstart itself in the list.

Current problems that I see:
1) Not all of our modules are hidden. Perhaps the code doesn't deal with -dev releases properly?
2) Not every module has a matching package (I think Backoffice modules were some of the problematic ones), which causes them to appear oddly in the list, and might be connected to #1.
3) Despite showing Kickstart in the list of modules that can be updated, Kickstart can't actually be updated through the update manager :)
So we either:
- Try to make it work (if possible, but I'm not holding my breath)
- Continue showing it in the list but remove the ability to actually try and update it (preferred, maybe with a custom message with an explanation)
- Remove it from the list completely

Comments

jsacksick’s picture

Tagging

bojanz’s picture

The fix will also need to be backported to Kickstart v1 to prevent confusion such as #1637402: commerce_kickstart-7.x-1.8-core.tar.gz does not contain any .info files.

vasike’s picture

Status: Active » Needs review

It seems there's an issue with dev versions.
"Recently", drupal.org changed the naming of the dev versions (ex. 7.x-1.0+17-dev instead of 7.x-1.x-dev)

here is a gerrit commit, that adds an OR condition to see if it's the dev version.
https://code.drupalcommerce.org/#/c/502/
with this all kickstart built-in modules should be removed from update manager.

what about drupal core update notice? anyway it's not available for update, but a notice for a new version could make people try to upgrade core and there are some core patches needed.

jsacksick’s picture

bojanz’s picture

Status: Needs review » Fixed

Improved the comments on #515 and merged it

This fixes #1 and #2. We need a new issue for #3.

Status: Fixed » Closed (fixed)

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

Balbo’s picture

Version: 7.x-2.x-dev » 7.x-2.0
Status: Closed (fixed) » Active

I think this should be the right thread...

(I'm not new to drupal, I'm new to "profiles" "distributions")

I just downloaded latest version of kickstart (7.x-2.0). As I read here, I

Move modules into sites/all/modules or sites/all/modules/contrib: Although installation profiles build with the modules in the profiles directory, many developers want them in sites/all/modules. Before running the installation process, just move the modules from profiles/commerce_kickstart/modules into sites/all/modules with any tool you like. For example, mv profiles/commerce_kickstart/modules/* sites/all/modules/.

and correctly got a running ecommerce.

Now, if I go to /admin/reports/updates I just see the core and the "Commerce Kickstart 7.x-2.0 module" (that "Includes: Commerce Kickstart, Commerce Kickstart Block, Commerce Kickstart Blog, Commerce Kickstart Comment, Commerce Kickstart Help, Commerce Kickstart Inline Help, Commerce Kickstart Lite Product, Commerce Kickstart Menus, Commerce Kickstart Merchandising, Commerce Kickstart Migrate, Commerce Kickstart Order, Commerce Kickstart Payment Example, Commerce Kickstart Product UI, Commerce Kickstart Reset, Commerce Kickstart Search, Commerce Kickstart Service Provider, Commerce Kickstart Slideshow, Commerce Kickstart Social, Commerce Kickstart Taxonomy, Commerce Kickstart User, Toolbar Megamenu"). Both updated.

But I do not see all others contrib, like Views.

Is this supposed to be the correct behavior? Don't think so.
What should I do? Thanks

bojanz’s picture

Status: Active » Closed (fixed)

No, modules are not supposed to be moved.
I'll have that page fixed.
Btw, the correct page is listed on the project page.

Balbo’s picture

Sorry, I don't think I got it.
What page are you about to fix?
The /admin/reports/updates not showing contrib or the one saying to move modules?

If i didn't move the modules before installation, would I see the available contrib updates? Should restart without moving folders, or it doesn't matter?
Sorry for being so tedious, but I need to understand it right.

When you say "the correct page is listed on the project page" you mean "the correct page that shows available updates"? I cannot find any hint about "correct page" in the project page.

Thanks a lot. I thinks this answers will help several people.

I now did see the notice here. Got it.
I will restart with a vanilla commerce kickstart, and I guess I will now see the available contrib update at /admin/reports/updates.

bojanz’s picture

I am referring to http://www.drupalcommerce.org/commerce-kickstart-2/install linked from http://drupal.org/project/commerce_kickstart

Contrib modules included in Kickstart are not shown in the update manager, because they are updated together with the distribution. That is intentional.