Over the last couple of years, I’ve written a few SharePoint-based blog posts as I’ve hacked my way around the company’s infrastructure, trying to get it working the way I’d like it to (creating dashboards, adding the odd bit of workflow and custom columns to pre-populate list data, embedding video, etc.). \u00a0There’s a rumour that we might get SharePoint 2013 soon but, for now, all of my hacks\/tweaks have been based on 2007.<\/p>\n
In the last few weeks, one of the projects I’ve been involved in has taken a major step forward, engaging a real designer and a real web developer, instead of li’l ol’ me. \u00a0From my perspective, this has been great news, although there have been some times when I’ve questioned the\u00a0maintainability\u00a0of custom code used in situations that have caused problems in the past (e.g. to edit the default forms used for displaying list items).<\/p>\n
As you might expect, I’ve also picked up a couple of tips, working alongside some experts – and I thought I’d make a quick note of them here, for future reference.<\/p>\n
First up, a handy little trick to edit list forms (like DispForm.aspx) without having to resort to using SharePoint Unfortunately, this doesn’t seem to work on my Office 365 SharePoint site, so it might be 2007-only but useful nevertheless. In our case, this was used to add a (hidden) Content Editor Web Part with some jQuery and CSS to style up the form.<\/p>\n Sometimes, there are standard elements of a page that you don’t want to display and, without access to the templates used on a corporate site, that might be difficult. As it happens, all that’s required is a little in-line CSS, included in a (hidden) Content Editor Web Part:<\/p>\nDestroyer<\/del> Designer, which is little more than Microsoft FrontPage (just about OK in it’s day but long past its sell-by date now). Just add ToolPaneView=2<\/code> into the query string, for example http:\/\/sharepoint.intranet.com\/00001\/Lists\/ListName\/DispForm.aspx?ToolPaneView=2.<\/p>\nHiding page elements<\/h3>\n