La señalización personalizada y el acceso denegados páginas no funcionan en SharePoint 2013

Question

¿Cómo personalizo la sesión y accede a las páginas denegadas en SharePoint 2013?

Después del código de inicio de sesión, corrí el script de Shell Power, pero esto no parece estar funcionando.

¿He perdido algo?

Script de PowerShell:

Set-SPCustomLayoutsPage -Identity "Signout" -RelativePath "/_Layouts/SignOutCustom/SignOut.aspx" -WebApplication url

Answer 1

There is an identified issue with SharePoint 2013 ignoring the values set through the Set-SPCustomLayoutsPage cmdlet.

See: Custom Access Denied Page in SharePoint 2013.

Although the same UpdateMappedPage method and Set-SPCustomLayoutsPage cmdlet exists in 2013, there is an identified bug in the product related to the property. The custom location can be set using either of these methods, but SharePoint will not recognize them and will continue to use the out of the box accessdenied.aspx page.

The comments on that page suggest that it is expected to be patched Feb. 2014.

Additionally, in SharePoint 2013, the path to files in the layouts folder has changed. If the files are in the 15 hive, your path should be /_layouts/15/SignOutCustom/SignOut.aspx.

The article Virtual directories in SharePoint 2013 solutions explains this as:

For files in the virtual folders _layouts or _controltemplates, SharePoint needs to use the version of the files in %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\15\ (sometimes called the 15 hive) or in the corresponding 14 hive, depending on the mode of the site collection. SharePoint adds “/15” into the virtual directory path just after the virtual directory name to signal that the SharePoint 2013 files should be used. The absence of that extra string indicates that SharePoint 2010 files should be used.

Answer 2

There is a Bug in SharePoint in setting up Custom Access Denied Page. To achieve this, please find the workaround in below URL

Configure Custom Access Denied Page - BUG in SharePoint 2013

Answer 3

You should update sharepoint server to october or november build. Don't forget to run iisreset after spcustom layoutpage execution.