Use Crumbs 7.x-2.x [#2409091]

Every once in a while I get requests on Crumbs that refer to the 7.x-1.x version, and are already fixed in 7.x-2.x.
E.g. #2408879: Commerce Kickstart Checkout Use Case
People then tell me that Kickstart does not want them to upgrade any of the included modules.

I have not studied Kickstart myself, and don't know if this true, or some kind of misunderstanding.

If there is a safe way for people to upgrade, maybe this should be done first (adding it to the docs, with an "at your own risk"), and then after a while, Kickstart can officially switch to the crumbs-7.x-2.x.
Of course I will be happy for any testing and feedback from the Kickstart side.
Especially the upgrade path needs a special look, I think.

Comments

Comment #1

suntower CreditAttribution: suntower commented 22 January 2015 at 21:02

I guess I'm the guinea pig.

I updated to 7.x-2 and I am -more- confused than ever. I basically need -5- minutes of your time to understand the UI. I (literally) cannot figure out how to enable various plug-ins or change their weights or... basically -anything-. I cannot be the only one who feels the same.

In return, I will HAPPILY write a proper user guide. I've written professional online help for 25 years.

I contacted you via IRC a few weeks ago on this. I will follow up w an e-mail.

TIA.

Comment #2

donquixote CreditAttribution: donquixote commented 22 January 2015 at 22:17

Ok, catch me on IRC.

Comment #3

donquixote CreditAttribution: donquixote commented 23 January 2015 at 04:06

@ Kickstart maintainers:
I don't know if you share the concerns raised by suntower. The admin UI has always been a controversial subject, and I have yet not found a "perfect" UI for the plugin management.
Either way, users that want to upgrade should not be stopped by Kickstart.

Maybe the explanation is that you are not supposed to modify the code within the kickstart folders, but you can download alternate module versions and place them in sites/all/modules/contrib, which (I assume) has priority over the modules in the Kickstart folders. So you would have crumbs-7.x-1.x in the kickstart folders, but crumbs-7.x-2.x in the sites/all/modules/contrib folder.

Is this correct?
@suntower: Is this the way you installed crumbs-7.x-2.x?

Comment #4

suntower CreditAttribution: suntower commented 23 January 2015 at 04:41

@donquixote

I replaced the existing crumbs folder which is inside the kickstart profile.

/profiles/commerce_kickstart/modules/contrib/crumbs

I did -not- install it in sites/all/modules

I think -one- issue is that the 7.1 v included with kickstart contains a class in crumbs.taxonomy.inc. for commerce products.

I'm sending you an e-mail.

Comment #5

donquixote CreditAttribution: donquixote commented 23 January 2015 at 05:58

I think -one- issue is that the 7.1 v included with kickstart contains a class in crumbs.taxonomy.inc. for commerce products.

I had a look at the module included in Kickstart, and I found that it is all unmodified native code from Crumbs 7.x-1.x.
And the product-specific code in there only applies on sites where product/% is a path to a commerce product. This is the case if you use the commerce_product_page module, but not with native Commerce only. In native Commerce, product entities do not have a relevant user-facing url where you would care about the breadcrumb. (Users visit the "product display" node url, not the product url).

The 7.x-2.x branch still supports term references from commerce products. But it does so in a generic way, by supporting term reference fields on all entity paths that are known to Crumbs. E.g. if the bean module would register a bean/% route for bean entities, and tell Crumbs about this route, then the term reference, entityreference and other entity-related Crumbs plugins would all work for bean/% magically.