Portal Engine Questions on portal engine and web parts.
Version 7.x > Portal Engine > Isolate staging tasks to their respective sites View modes: 
User avatar
Member
Member
Jerreck - 1/13/2014 8:54:42 AM
   
Isolate staging tasks to their respective sites
How would I need to configure my settings to prevent the staging tasks of one site from appearing on another?

For example, when I edit a document from Site A, I want that synchronization task to show up only in the log for Site A - not Site B.

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 1/14/2014 6:34:34 AM
   
RE:Isolate staging tasks to their respective sites
Documents/Pages are site specific when it comes to content, so what you're explaining is or should already be happening. When it comes to templates, web parts, layouts, etc, those are global objects that each site is given permission to use. So if Site A and Site B have access to Page Template 1 and Site A makes a change to that template, Site B will also see the change.

User avatar
Member
Member
Jerreck - 1/14/2014 2:04:33 PM
   
RE:Isolate staging tasks to their respective sites
That makes sense, but why would I be seeing changes to documents from one site appear in the staging log for another site? Is there a setting that we may have accidentally changed that would cause this?

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 1/14/2014 2:58:38 PM
   
RE:Isolate staging tasks to their respective sites
Check and see where the content is managed. If it is specifically in the document then, no it shouldn't sync across. If it is set in the web part or layout or template then yes it will affect all pages using that template on all sites.

User avatar
Member
Member
Jerreck - 1/15/2014 8:20:50 AM
   
RE:Isolate staging tasks to their respective sites
We don't appear to have that key anywhere. That would be added to appSettings in the web.config, correct?

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 1/15/2014 9:52:04 AM
   
RE:Isolate staging tasks to their respective sites
Yes, that is correct. I see the post below saying that everything is OK and just the same names confused you. The computer machines are making fun of us sometimes :-)

Best regards,
Juraj Ondrus

User avatar
Member
Member
Jerreck - 1/15/2014 8:22:22 AM
   
RE:Isolate staging tasks to their respective sites
^ That was a reply to kentico_jurajo's post

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 1/15/2014 1:20:39 AM
   
RE:Isolate staging tasks to their respective sites
Hi,

Have you tried using this web.config key:

<add key="CMSStagingLogGlobalObjectsOnlyForAssignedSites" value="true" />

If true, tasks for global objects are logged only for the sites to which the respective objects are assigned. The default value is false.

However, when I am in CMS Desk of site A, make some document change, I see the task only in the Site A staging tasks area. If I log into site B CMS Desk, the task list does not contains this document staging task.

Best regards,
Juraj Ondrus

User avatar
Member
Member
Jerreck - 1/15/2014 8:33:25 AM
   
RE:Isolate staging tasks to their respective sites
My mistake. I've triple checked our staging logs, and confirmed that I am not seeing any document changes from one site appearing in another. I was misreading a section of tasks as document updates when they were document types (in my defense the types shared the names of the documents :D ).