Wednesday, October 26, 2011 4:12 PM
We are using a publishing portal with content deployment setup between two site collections in same web application. One site collection is authoring site with URL /department/author and other site collection is a read-only production site with URL /department. If we have a page a.aspx with summary links webpart and page is in checked-in state and we do content deployment, the page moves to production site but URL's for links in summary links webpart remain /department/author, which is fine since the content is in checked-in state, now we publish the content in authoring. Content is in published state, then do a content deployment to production the links in the summary links webpart on the page in production is still /department/author which result in access denied error, infact the page cannot be opened anymore. Can some one tell us if this is a known behaviour(BUGGG) in Summary Linka webpart and any work arounds to fix the same?
Monday, October 31, 2011 10:45 AM
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Monday, November 14, 2011 9:05 PM
We attempted to repro this but was not able to. Do you have any further details on how you configured your content deployment and how the web application was configured?
You may get better traction on your issue if you spoke with a support engineer directly, if you are not finding what you are looking for via the forums.
Please visit the below link to see the various paid support options that are available to better meet your needs. http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone
Regards, Savoeurn Va Microsoft Online Community Support