Open a new document from a word template for a SharePoint Document Library

Open a new document from a word template for a SharePoint Document Library, instead of opening the dotx file itself – as SP would normally do.
————————————————————————————
<script type="text/javascript" src="/_layouts/jquery.min.js"></script>
<script type="text/javascript">
$( function () {
$("a[href$='.dot'], a[href$='.dotx'], a[href$='.xlt'], a[href$='.xltx']").attr("onclick", "").click( function () {
saveLocation = $(this).attr("href").split("/").slice(0, -2).join("/")
createNewDocumentWithProgID(window.location.protocol + '//' + window.location.host + $(this).attr("href"), window.location.protocol + '//' + window.location.host + saveLocation, 'SharePoint.OpenDocuments', false)
return false
})
})
</script>
—————————————–
As always when we are working with jQuery you have to make sure that you reference the location of that .js-file
I got it from
 <script src="//ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js"></script>
—————————————–
Advertisements

“Document Property” menu item greyed out under Insert/Quick Parts

The Document Property feature  works only in Word 2007-format documents, using the new content control feature.

Old-style document properties (using fields, via Insert – Quick Parts – Field – DocProperty) Work in Word 2007 and Word 97-2003 documents, but the content control variety work only in .docx documents.

So you will need to convert the document to docx format to use the Document Property Feature.

Increase the SharePoint 2010 Upload File Size Limit

  • Central Administration
  • “Manage Web Applications”
  • Select desired web application row (don’t click on the title, just select)
  • “General Settings” in the ribbon
  • Under Maximum Upload Size, change the setting to the desired value (e.g. 200 MB in our example)
  • “OK”

if it still doesn’t work…..

Increase the IIS7 request length

Use the following command on the machine you are running the IIS 7:

%windir%\system32\inetsrv\appcmd set config -section:requestFiltering -requestLimits.maxAllowedContentLength:valueInBytes

In our case, we’ll simply put 200x1024x1024=209715200 bytes.

You will receive a confirmation message after applying the command. Please bear in mind that you will need to run the cmd.exe in administrator mode.

 

 

Credits

Find SharePoint GUIDs using PowerShell

2007 version:

[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint")
$site = New-Object Microsoft.SharePoint.SPSite("http://yourserver/sites/yoursite")
$web = $site.OpenWeb("yoursubsite")
write-host "Site: " + $site.id
write-host "Web: " + $web.id
$web.lists | Format-Table title,id -AutoSize
$web.Dispose()
$site.Dispose()

 

2010 version:

$site = Get-SPSite http://yourserver/sites/yoursite
$web = $site.OpenWeb("yoursubsite")
write-host "Site: " + $site.id
write-host "Web: " + $web.id
$web.lists | Format-Table title,id -AutoSize
$web.Dispose()
$site.Dispose()

Sharing One List / Library across multiple sub-sites.

I wanted to create a Master Contact List on the main site & add a webpart to Show Filtered departmental contacts on various department subsites.

The problem I ran into was that I wasn’t able to add list from the main site to any of the subsites.

I spend a few days looking at the issue & realised that I had to export the web-part; but SP2010 doesn’t allow this for List & Libraries.

Googling around a bit I found a post on Mike Smith’s blog with help me resolve the issue.

I have modified it slightly to show the steps I took to get around the problem.

Article summary:

  • I will show how to create a custom web part that represents a list or library’s view and use this web part in other sites (at least in the same site collection) without copying documents between sites.
  • This custom web part supports a tool bar so files can be uploaded and maintained in a single library, but viewed and maintained from any site in the site collection that has this web part.
  • Tools needed:
    • SharePoint Designer (to make one quick change, export the web part, and then optionally roll back the change)
    • Some way to find the site’s GUID (tool available on codeplex – called SharePoint Manager)  link below.

The Question:

What started out as a simple question has led to some interesting results. So interesting that someone somewhere else must have written this up. I’ve not found it, so here goes…

The question that started this was “why don’t list and library web parts have a ‘Export’ option?” Most other web parts do.

First some observations:

  • While editing a web part page, click a web part’s menu and you will usually see an Export option, except for list and library web parts.
  • List and library view pages are web part pages (they have “Edit Page” in the Site Actions menu”) and the displayed list is a web part.

So how can you export a list web part?

Turns out to be pretty easy. Edit the page in SharePoint Designer and change one word.

  1. Create a new web-part page on the main site (eg. WPPage.aspx) and add a webpart with the Library / List you wish to export.
  2. Open the site in SharePoint Designer and double click the page with the web part that you have created (WPPage.aspx in my case)
  3. In the code view find the web part and find
    <ExportControlledProperties>false</ExportControlledProperties>
    and change from “false” to “true”
  4. Save the page (this will “unghost” the page, but you can undo the changes after the export is complete – right-click the file in the Folder List and select Reset to Site Definition)
  5. Go to a browser and visit this page. Go to Site Actions, Edit Page.
  6. Click Edit in web part you just modified and click Export.
  7. Save the file to a location on your local machine
  8. Give the file a name and save it somewhere where you can find it in the next step.

To import the exported settings as a new web part:

  1. Visit your top level site in the site collection and go to Site Actions, Site Settings, and in the Galleries column click Web Parts

To add the web part.

  1. Nothing special here. Add this web part just like any other web part.

Some differences…

Oddly, the displayed columns are different. The AllItems view displayed Type, Name, Modified and Modified By. The new web part displays Type, Name and Modified By. This is easy to fix. Edit the web part and change the Selected View property to All Documents then you will get the same list of columns in both displays.

The new web part does not display a toolbar by default, but this can be enabled from the web part’s properties panel. If the toolbar is enabled you will see all of the buttons found in the AllItems page, New, Upload, Actions and Settings (depending on the current user’s security rights).

Now test the web part in a sub site….

Error!

   Unable to add selected web part(s).
List does not exist.
The page you selected contains a list that does not exist.

On the first attempt it appears that the new exported web part will not work on another site. Time for more research…

Find the missing GUID

Open the .DWP (.WEBPART in 2010) file created by the Export. Find these two lines:

SP 2007 
   <ListName …..>{ list_guid_here } </ListName> 
   <WebId ….> all_zeros_guid_here </WebId>

SP 2010

   <property name=”ListName” type=”string”>{ list_guid_here } </property> 
   … 
   <property name=”WebId” …>all_zeros_guid_here </property>

SharePoint uses Globally Unique IDs (GUIDS) to identify just about everything stored in the databases. Notice that the ListName has a GUID, but the WebId is all zeros. Replace the zeros with the GUID for the site that owns the list and all will then work.

How to find a GUID

Download a tool from CodePlex http://spm.codeplex.com/

You will need to point to the parent site & check the ID field. (I shall post one detailing this step too at some point)

Update the web part file

Edit the WebId element and replace the all zeros GUID with the site’s GUID:

SP 2007”   <WebId ….> all_zeros_guid_here </WebId>

SP 2010    <property name=”WebId” …>all_zeros_guid_here </property>

After updating the DWP file with the site’s (web’s) GUID, re-upload it to the web part gallery and go and test the web part in a sub site.
And for the “Strange Things” list… the GUID for the web site does not include brackets ( { } ) and is in lower case. The GUID for the list must have brackets and MUST be in UPPER CASE or it will not work.

Watch outs and warnings!

  • This has not been tested in a production environment – you are on your own! (Please let me know if it works or does not work for you)
  • So far I have only tested this on MOSS 2007 Enterprise and SharePoint Server 2010, but it should work in WSS and SharePoint Foundation.
  • I have tested this so far with document libraries and several lists such as Announcements, but not with every list and library.
  • This will only work within the same site, or within the same site collection. It will not work between site collections, between applications or between servers.
  • The view displayed in the web part is a copy of the view in the original list or library. Use Edit, Modify Shared Web Part to pick another view or to refresh the view.
  • Users will need rights to the original list or library. This web part is only a view of the real list.
  • Alerts will be stored in the site with the original list so alert management will need to be done from that site’s Site Actions, Site Settings menu.
  • Most menu options will display screens from the site with the original list, but when the user clicks OK, Cancel, Close, etc, they will return to the site with the web part. One exception is if an operation generates as error, the “Go back to site” link will take them to the list’s site, not the web part’s site.

ORIGINAL POST : http://techtrainingnotes.blogspot.com/2009/03/sharepoint-one-library-multiple-sites.html