We're actively developing using cod, porting our own (not features based) event profile to cod in order to bring our work into the scope of the community.

We use taxonomies. While porting one of our features we realized that adding taxonomy terms to a feature via uuid was broken.

After drush installing to the instance, it worked. We have not found out at this point which patch to uuid caused the problem.

Comments

blueprint’s picture

blueprint commented

I should add that using the original uuid modules if installed to overide the cod profile (/root/profiles/ or /root/sites/all) will cause new installs of the profile to NOT publish the node intended to be the default start page with instructions, etc. This is not so tragic since it's the only content we could identify being deployed with uuid (one node) and since we had many more elements to deploy (repeatedly) it seemed wise to ignore that one node.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Postponed (maintainer needs more info)

Postponed pending clarification of which patch breaks it. Really that should be fixed in whichever uuid issue the patch is associated with. I could see marking this as a duplicate of that issue except that this issue should track updating the patch in COD.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

The issue that is getting patched in is #968826: Export Menu links with UUID.

I see it needs work, but seems close.