Closed (outdated)
Project:
Migrate
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Feb 2012 at 20:47 UTC
Updated:
21 Feb 2018 at 13:48 UTC
Jump to comment: Most recent
Comments
Comment #1
mikeryanCan you explain a little more clearly what you mean by "node permissions"? If you mean the permissions associated with a role, we do have a role destination class (MigrateDestinationRole) but it pretty much just migrate the role name - not a bad thought to bring across the permissions as well.
Comment #2
mgiffordI think in this case it is mostly the role, but there are of course other means to control node permissions. Would be great to be able to provide more flexibility on that front.
I will try to come back with a more detailed requirements list.
Comment #3
StuartDH commented+1 in the interim I was going to use features for permissions, but this would be a good addition to migrate
Comment #4
mikeryanStill don't know what "node permissions" means, but importing the permissions associated with roles makes sense...
Comment #5
SamH commentedWe could either insert into {role_permission} directly, or use user_role_grant_permissions($rid, array $permissions = array()). Which way makes more sense? The choice will determine what fields we have for the permission destination.
Comment #6
randallknutson commentedFor anyone still interested in this, I wrote a quick MigrationDestination class for role_permissions. You will need to include this in a custom module but it does work.
Comment #7
pifagor commented