deploying nodes creates new a user on the destination?
| Project: | Deployment |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I'm a bit confused about how deployment of nodes works with users, hoping to get a bit of clarification.
With admin users (uid 1 on both sites), everything works fine, but switching to regular users seems to get a bit odd.
I have two sites: call then master and slave.
On each one I've created a non-admin user: on master, there is the editor user; on slave there is the sync user (which I created purely as a services users).
I log in as an editor user on master, create a node.
I then go to sync it.
I give the username and password for user 'sync'.
The batch reports a success.
I then go to the slave site, and I find the node exists there now -- except its author is not 'sync', but 'editor'!
Is this the expected behaviour? If so, what's the point of logging in as 'sync'?
#1
When nodes are deployed they retain the same author they had on master. At deployment time, if that user does not exist on slave, then the user is deployed before the node, then the node is deployed as that author. I know that, at least for my client I built this for, this is desired behavior, and I feel like changing the authorship of a node on deployment is not a good thing. Ideally, the node data should be identical between master and slave, this is the whole point of the module.
The point of logging in as sync is to provide credentials that have the authority to create nodes and taxonomy and users and etc on slave.
On another topic you got some nodes to deploy which is awesome :D