You need to check in the pages and publish them. The pages library (part of the publishing feature) is not a normal list.
Also have a look at the "Manage checked out files", this lets admins take ownership of a file if it is checked out to someone else. [cid:[email protected]] Regards, Paul Turner Senior Solutions Specialist M: 0412 748 168 P: 08 8238 0912 F: 08 8234 5966 A: 66 Henley Beach Road, Mile End SA 5031 E: [email protected]<mailto:[email protected]> W: www.dws.com.au [cid:[email protected]] ADVANCED BUSINESS SOLUTIONS LTD This email and any files transmitted with it are confidential and are only for the use of the person to whom they are addressed. If you are not the intended recipient you have received this email in error and are requested to delete it immediately. Any opinion expressed in this e-mail may not necessarily be that of DWS Pty Ltd. Please consider the environment before printing this email. From: [email protected] [mailto:[email protected]] On Behalf Of Wampers, Wilson [Talent International] Sent: Friday, 13 November 2009 5:34 PM To: ozMOSS Subject: RE: Item Level Security Hi Sezai, The system account and my personal account are both site collection admins. Yet, either way I 'run as', I cannot see pages in a specific site's pages library pages. It is actually showing no pages at all. That shouldn't be possible either since one can't delete/recycle the welcome page of a sub site. So the only explanation is, and I have evidence, that the pages are set with exclusive item level permissions. When trying to create an already existing page (not visible though) the error page reveals the existence and claims either: ERROR The file "http://##########/de######s/O###E/re####s/#######ge/Pages/######.aspx"; is checked out or locked for editing by #########. at Microsoft.SharePoint.Library.SPRequestInternalClass.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object varFile, PutFileOpt PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage) at Microsoft.SharePoint.Library.SPRequest.PutFile(String bstrUrl, String bstrWebRelativeUrl, Object varFile, PutFileOpt PutFileOpt, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String bstrCheckinComment, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage) Kind Regards, Wilson Wampers From: [email protected] [mailto:[email protected]] On Behalf Of Sezai Komur Sent: Friday, 13 November 2009 14:08 To: ozMOSS Subject: Re: Item Level Security Site Collection Administrators can always access all content, even if they've been 'kicked out' (I think) you could try adding your 'system account' to site collection administrators for that site collection. If you investigate permission levels a little closer, there's the following permission you could try disabling as a way to prevent people messing with permissions: Enumerate Permissions - Enumerate permissions on the Web site, list, folder, document, or list item. No idea if disabling this will have the desired affect though, its worth a shot. Sezai. On Fri, Nov 13, 2009 at 1:25 PM, Wampers, Wilson [Talent International] <[email protected]<mailto:[email protected]>> wrote: Hi All, Is there a recommended way of preventing (owner rights) users from breaking inheritance and even more remove the systems account from seeing content? Any suggestions? Kind Regards, Wilson Wampers _______________________________________________ ozmoss mailing list [email protected]<mailto:[email protected]> http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
<<inline: image001.png>>
<<inline: image002.jpg>>
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
