Users created via Content Staging are not assigned to destination site

Lance Keay asked on September 14, 2017 10:24

We are using Content Staging and v9.0.45. When Content Staging Users from www back to dev, the User information is transferred, but the User is not assigned to the dev site. Both www and the dev site have the same 'code name', and the dev DB was restored from a www dump, so they match.

It's strange that the User's info does get added in dev, but the site assignment is missing.

content staging

Correct Answer

Trevor Fayas answered on September 15, 2017 15:47

Thanks for Clarifying Lance.

Was there any errors in the event log during the staging? This is definitely odd behavior, i've had no problems doing exactly what you are doing before.

Can you run a test for me? Create a user on the Live site, make sure it's assigned to the site, then check the Staging module on the live site. You should see the staging task, hit the Eyeball icon to investigate it, and can you either try to screen shot the information there and get it to us or just take a look? On the bottom you should see a list of related items that also will 'push' with the user and i want to see if the User Site information is in there.

1 votesVote for this answer Unmark Correct answer

Recent Answers

Prashant Verma answered on September 14, 2017 12:07

Hi Lance,

Its seems your (dev) source site id is differ with destination site id due to which the user and their content get created on destination site but unable to assign because of their site id miss match.

you can check in DB using (select * from cms_site)

Thanks

Happy to help you

1 votesVote for this answer Mark as a Correct answer

Trevor Fayas answered on September 15, 2017 14:18

prashant, ids change between environments but that doesn't matter with the staging module. it translates the id using the code name/guid.

I would check if the guid is the same, if not then I would suspect that at some point after the clone the site was deleted and readded or something. can you check that for us?

1 votesVote for this answer Mark as a Correct answer

Lance Keay answered on September 15, 2017 15:37

SiteID and SiteGIUDs are identical between servers. They both have the SiteId of 1 and are the only site on either installation.

0 votesVote for this answer Mark as a Correct answer

Lance Keay answered on September 20, 2017 10:12

Thanks Trevor - I just performed the test and it's all working properly. I'm not sure why it malfunctioned a few days ago. Thanks again for your help!

0 votesVote for this answer Mark as a Correct answer