Tag Info

Hot answers tagged

5

I ran into the same requirement in a recent project, basically preventing access to any list view or form of a particular (hidden) list via the Web browser. SharePoint designer isn't allowed on Web Application level and Web services (including client object model) is blocked by a custom HTTP handler, so the concerns mentioned in other answers didn't apply ...


5

You can do this programmatically or through PowerShell, setting SPField.Hidden property to false. Tentative PowerShell script: $web = Get-SPWeb http://localhost $list = $web.GetList("/Lists/Test") $field = $list.Fields.GetFieldByInternalName("Created") $field.Hidden = $false $field.Update()


4

Closed Webpart > When you close a webpart , it goes and stays in the closed webpart gallery. You can see this gallery when you click on Edit Page on the 2010 ribbon > Insert > Webpart > Closed Webpart Gallery. When you close a webpart it does not get loaded in the webpage during realtime. The closed webparts even then reside in this gallery which can be ...


4

If you want to just show Sites and Subsites below it, you can setup the Data Source like this: <SharePoint:SPHierarchyDataSourceControl runat="server" ID="TreeViewDataSource" IncludeDiscussionFolders="false" ShowListChildren="false" ShowDocLibChildren="false" ShowFolderChildren="false" RootContextObject="Web" /> And use above data ...


3

Edit the permission of the list and set the access level accordingly, you can even give permission to only a few user to a list or library. You can find list permission under list settings. I would recommend creating a group if you need this set of user in some other place also, otherwise if you know that you have to use this permission set only for a ...


2

You can access all sorts of things in SharePoint by typing in a url or by merely changing the querystring. If the list must be hidden always, then change security on the list so that only those with proper permissions can see it. If you really are set on this, you can also implement some form of URL Rewriter on the IIS server hosting SharePoint and block ...


2

Move the CEWP below the list. Alternatively, don't run the javascript until the page has loaded. A common method of doing this is via jquery: http://api.jquery.com/ready/ <html><head> <script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script> <script type="text/JavaScript"> $(function() { // ...


1

Can you try this: Click on Settings at the top and then click on Edit Page. Then Select the web part representing the list. At the top right click on Edit Web Part. Go to Miscellaneous section and select Server Render. Click OK. Let me know if it helps. I recently faced a somewhat similar issue which I blogged here. ...


1

For some odd reason, the items came back after selecting Modify this View > Scroll down to the bottom of the edit view page and select OK (without making any changes). It exceeds my knowledge why our SharePoint instance behaves this way - but it worked for me.


1

It's nested in one of the many javascript files in layouts folder. You can download a software called FileSeek and search through all files in this folder using keywords, in this case "function HideListViewRows". I have no affiliation with this piece of software.


1

Don't know where HideListViewRows is defined, but its added from the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\GLOBAL\XML\VWSTYLES.xml file. E.g: <xsl:choose> <xsl:when test="$IsDocLib or dvt_RowCount = 0"><script ...


1

I'd aree with Diptarag - MSDN has some good documentation on this one. http://technet.microsoft.com/en-us/library/cc721640.aspx You can set permissions at multiple levels - Site Collection, Site, List. List should give you what you need.


1

As Per my understanding, you can do it by Editing Elements.xml like Hidden="True" and then deploy once again. Also, you can do directly by editing C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\ YourSolutionName \Elements.xml Jinesh


1

It should be pointed out that, without touching the permissions, just because it is hidden or redirected in the UI does not mean it is not accessible through other means. SharePoint designer, web services, object model, etc. will still see it. It's the old 'security through obscurity' discussion. If hiding is all you want, SPList.Hidden and Mark's 2nd ...


1

Hmmm... couple of ideas come to mind, although neither is particularly awesome. 1) Create a custom HTTP handler that detects if a user is browsing to one of the list url's and redirect the user 2) Link a javascript file in your master page that does the same thing (checks the url to see if it contains /Lists/YourList) and redirect the user somewhere else. ...


1

What you need to do to ensure that the fields you don't want to see are not exported, is create a view that shows only those fields that you want to see and export that view. As far as the "Path" that field is exported by default, and you will have to manually delete it from the excel spreadsheet.


1

I'm not sure that is an easy question to answer, as it depends on you definition of "commonly used" and "that we should know of". The web part, list template and master page galleries, along with the users lists are all "hidden" lists, but they are also accessible from the site settings pages, so are they really hidden?



Only top voted, non community-wiki answers of a minimum length are eligible