How To Access List Settings For The Contact Us Form App In Office 365 Sharepoint Online 2013 Public Sites

012614_2140_howtoaccess1The Contact Us Form App from the Sharepoint store can’t be opened in Sharepoint Designer and its submissions list comes with a limited set of ribbon tools which restricts what you can do with the list. Here’s how to regain access to the all important “list settings”, so you can access many of the configuration options of a normal SP list, including:Exporting the list to a spreadsheetList permissions
Validation settings (which you can set up to deter spam)
Advanced settings (item level permissions, content type management etc)
RSS settings
The Steps:
From “site contents”, open the contact us form app
Click the tile to open the “submissions” list
Append ?ToolPaneView=2 to the url so it looks like:
That opens the page for editing
Click the little down arrow on the top right of the web part and “edit web part” to open the web part properties
Under “tool bar type” select “show toolbar” and click “ok”
You’ll now see 3 new links: “New”, “Actions” and “Settings”.


Now you can control all the options of a Sharepoint list!

Fix For Office 365 2010 Style Public Site When Chrome Updates Break Header

013114_1703_fixforoffic1If your site looks like this when viewed in Chrome:DO THIS!
Declare a height for the header element by adding this to your custom stylesheet:
.MS_MasterHeader { height:xxxpx; }
Adjust the xxx to suit your site.
What’s happening?
When Chrome updates to version 32.0.1700.76 m, you may notice the layout of your Office 365 2010 style public site’s header gets broken. The horizontal navigation and page content push up and obscure logo, title etc. I haven’t seen this problem in other web site platforms, so I’m pretty sure it’s a combination of the archaic table layout schema MSFT uses and changes to how tables are rendered by Chrome (see update). Since Chrome auto updates by default, it’s likely this will affect a lot of users and MSFT really has to do a better job of keeping up with browser changes.
If this doesn’t work for you, please post a question in my forum.
UPDATE: Another user had this problem but wasn’t using the header element at all, and when I dug into it a little deeper I found the specific cause is that Chrome doesn’t render the “rowspan” attribute correctly (or as other browsers do). MSFT uses rowspan to split a table column into more rows than other columns in the same table, for example a 3 row column next to a 1 row column. The workaround is to insert another table with multiple rows INSIDE a single row column of the “parent” table. That seems to trick Chrome into displaying it correctly.
If you want to apply that to the header element, you’ll have to make the adjustment to the master page in Sharepoint Designer (2010 sites) or using design manager (2013 sites).

Adding A “File Extension” Field To A Sharepoint 2013 Document Library

010714_2109_addingafile1The default “type” field in a SP library is configured to show a document type ICON, which isn’t very useful if you want to store document types for which there’s no prescribed icon. I wrote about how to add a field for file name INCLUDING its extension in “Show file type in a library view (2010 and 2013)”. But in some cases you may want to show JUST the file extension in a separate field for filtering etc purposes.It turns out there is a field in the library’s xml called “file type” that would do just that – but by default it’s only used to compute the icon to display. Since this is oddly not readily available out of the box, you will have to do a little customization with Sharepoint Designer to get a text version of this field to display in your libraries.Step 1: Create a web part.
Fire up SPD and open any wiki (aspx) or web part page (it doesn’t matter which-this is just to create the web part)
Insert a data view web part of a library on the page


Save the page and click the top of the web part to reveal the “list view tools” (easier in SPD2010 “Split View”!)
Under “options” click “add/remove columns” and add the “File Type” column. Remove any unwanted columns and save the page
This effectively rewrites the xsl used to format the list – so be aware whatever is showing in “displayed fields” is what will be visible in your list.


In the tools, select “web part” and save the web part to the “site gallery”


Step 2: Insert the web part
Now you have the formatted web part in your web part gallery, you can insert it on any page, using the “insert » web part” tool.


If the “file type” field doesn’t appear, go into the library settings » views and add the field to the view in use.


This technique doesn’t change the default behavior of libraries and unfortunately will have to be done for every library individually. The file type field is something MSFT should have included in the library template, but for now that’s unlikely to change.
You can see an example of a revised library here »