_access_denied_splash() wording doesn't account for insufficient permissions

[kawauso]

The error presented when a user can't access a page either due to insufficient permissions or because it doesn't exist in 3.1 was:

You do not have sufficient permissions to access this page.

whereas in 3.2 it is now:

You attempted to access the "Foo" dashboard, but you do not currently have privileges on this site. If you believe you should be able to access the "Foo" dashboard, please contact your network administrator.

The new message implies the user doesn't have any permissions, rather than just insufficient permissions.

It only affects plugin/theme created pages, since core admin pages still use the "Cheatin’ uh?" message.

Related: #17511

[ryan]

If the user belongs to the current blog, perhaps _access_denied_splash() should simply return and let the default handler take over.

[sorich87]

access_denied_splash() return if the user belongs to the current blog

[ryan]

In [18008]:

Don't show _access_denied_splash() if the user has permissions for the site but insufficient perms for a particular page. Props sorich87. fixes #17514