Currently it is not possible to move nodes from one space to another when using Spaces Taxonomy. The reason for this is seemingly due to business requirements for Open Atrium, as outlined in the readme:

2. If you want to move foo/node/5 to bar/node/5, how do you handle any associations that may/may not be relevant in the new space? For example, imagine moving a casetracker case from a client group to a private group -- what should happen to its parent project and any email subscriptions for users that aren't in the target space?

I suggest removing this limitation from Spaces Taxonomy, so that developers can choose whether to allow to move nodes between Spaces or not, as per the specific business requirements of their projects.

CommentFileSizeAuthor
#6 spaces-Move-nodes-between-spaces-1860226-6.patch1.94 KBeuk
#5 1860226-5-spaces-move_nodes_between_spaces.patch1.96 KBiSoLate
#3 1860226-1-spaces-move_nodes_between_spaces.patch3.83 KBpfrenssen
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pfrenssen’s picture

pfrenssen
Location Sofia
CreditAttribution: pfrenssen commented

Here's a patch that removes this limitation.

pfrenssen’s picture

pfrenssen
Location Sofia
CreditAttribution: pfrenssen commented
Status: Active » Needs review
pfrenssen’s picture

pfrenssen
Location Sofia
CreditAttribution: pfrenssen commented
FileSize
1860226-1-spaces-move_nodes_between_spaces.patch3.83 KB

Here it is at last :D

pfrenssen’s picture

pfrenssen
Location Sofia
CreditAttribution: pfrenssen commented
Status: Needs review » Needs work

This should really be configurable, so it will not affect current implementations.

iSoLate’s picture

iSoLate CreditAttribution: iSoLate commented
FileSize
1860226-5-spaces-move_nodes_between_spaces.patch1.96 KB

Here is a patch to make it configurable for each space.

euk’s picture

euk CreditAttribution: euk commented
Issue summary: View changes
FileSize
spaces-Move-nodes-between-spaces-1860226-6.patch1.94 KB

Patch works.

However, it doesn't comply with naming convention for patches.
Also paths used in the patch are not standard.
Corrected both discrepancies.

PS. I wonder how come this module is marked as "Actively maintained"? The last commit was made almost an year ago...

euk’s picture

euk CreditAttribution: euk commented
Status: Needs work » Needs review
brunorios1’s picture

brunorios1 CreditAttribution: brunorios1 commented

@pfrenssen, @iSoLate,
I applied the patch but i didnt't found the admin configs.
Where this configurable option (checkbox) should appear?
thanks!

pfrenssen’s picture

pfrenssen
Location Sofia
CreditAttribution: pfrenssen commented
Status: Needs review » Needs work

@brunorios1, it's years ago since I worked on this, unfortunately I don't remember. Looking at the patch it is the "Spaces features form" which you can access at the path /features.

Anyway this patch needs work, I was too quick in marking it RTBC.

  1. It needs to be rerolled with correct paths starting from the root of the Spaces module, not from the Drupal root.
  2. Typo: "wether" should be "whether"
  3. Spaces Taxonomy is an optional submodule, so this configuration option should only be shown if this is actually enabled.
kristiaanvandeneynde’s picture

kristiaanvandeneynde
Primary language Dutch
Location Antwerp, Belgium
CreditAttribution: kristiaanvandeneynde as a volunteer commented

The patch in #828416-25: Enable multiple spaces per item--spaces_taxonomy implementation removes the space changing limitation and adds functionality to assign a node to multiple spaces. Perhaps all effort should be combined into that issue?