Hot answers tagged

13

Here are my 2 cents: Make sure SharePoint still looks and feels like SharePoint. Don't mess about with default font sizes. Even if SharePoint deals with it well, your third party add-ins may not. Try to limit them to just change the colour scheme to whatever the company uses, a customised top (header) area and an optional footer. Don't go nuts, you'll ...


8

You are working with CSS3, this is only supported from Internet Explorer version 9. For older versions of IE you need to have a fallback solution. One of the fallback is CSS3 Pie. More information can be found here: http://css3pie.com/ http://css3pie.com/about/ It requires you to add and reference an additional file (pie.htc) to your environment. ...


7

As already mentioned in another answer, Internet Explorer, up to and including version 8, does not provide support for any CSS3 based styling. While Internet Explorer 9 comes with limited CSS3 support (like border-radius and box-shadow, but neither text-shadow nor background gradients) it would require to change your masterpage as mentioned in another ...


7

Possible uses of hiding (closing) web parts can be if the web part is creating problems, is broken/unusable, or behaving badly. Or if the web part isn't needed anymore (like for an annual survey, only done once a year during May), you can hide it when it is not needed anymore. If the web part is not needed at all, and you do not plan on re-using it, you ...


7

I exactly had the same problem. After some investigation and trying out different approches I finally found the solution: 1) Do NOT place the @Register-statement before the DOCTYPE declaration 2) Instead you can place it directly within your Custom ASP.NET Markup Snippet - just before the usage of your custom control Hope that helps!


6

Courtesy of Randy Drisgill: http://blog.drisgill.com/2008/02/favicons-in-sharepoint-master-page.html Drag a favicon.ico file to the Images directory of your MOSS site with SharePoint designer. Add the following line to your Master Page at the bottom of the head section right before the </head> tag: <link rel="shortcut icon" ...


5

Customisations to the Data Sheet View are not supported, as this is generated using the Microsoft Office Access Web Datasheet Component, which renders the grid using the same base engine as the data sheet view that Microsoft Access uses.


5

I use layered architecture in all my SharePoint solutions and treat SharePoint generally as the UI layer, keeping it very thin. Any logic goes into the business model and I have DAL wrappers to abstract away the List infrastructure (which also helps with testing). For a good read on layered architecture in ASP.NET check out this article here. It's ASP.NET ...


5

The header and footer (the chrome) of SharePoint and most Asp.Net websites is defined in a master page. For SharePoint 2013 this is by default the seattle.master. My tip is to create your own master page by taking a copy of the Seattle.master, or using a Delegate control to insert your control. Create SharePoint master page : ...


5

Having worked a bit with SP Online page layouts now, I think the biggest difference, to the extent that there is one, is that you should not expect SP Online to handle much of anything server-side except for ASP.NET code. Otherwise, the process is pretty much exactly the same: in both cases you're presented with HTML That being said, you don't actually get ...


4

Here's my example for you. You need to place on the page: isotope's css style link on the page jquery script link on the page isotope's script link on the page HTML with your menu data isotope's sturtup script op the page and adjust it for you isotope's HTML And here's the result: Please note that you have to deal with conflict between isotope's ...


4

All you need to do is to follow these steps :) Open the master page, find the div tag: Put the following around it: <Sharepoint:SPSecurityTrimmedControl runat="server" Permissions="ManageWeb"> <div id="s4-ribbonrow" …</div> </SharePoint:SPSecurityTrimmedControl> or you can follow this Blog, it shows you three ways of doing it ...


4

I achieved this in a much more simple way. Follow this link - really easy for beginers linke me... http://blog.incworx.com/blog/sharepoint-administrators-blog/hide-recently-modified-from-the-quick-launch Edit page, insert content editor web part, edit source HTML of web part, paste in this HTML: <style type="text/css"> .s4-recentchanges { ...


4

I accomplished this by using the steps outlined here. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\DocumentTemplates\ Open wkpstd.aspx in a text editor. Find <SharePoint:RecentChangesMenu runat="server" id="RecentChanges"/> and replace with <SharePoint:RecentChangesMenu runat="server" ...


4

Another possible use of hiding a web part (I do this all the time), when you are importing a script onto your page via a content editor web part. Hiding the web part includes the script on the page but makes it so the web part cannot be deleted or closed inadvertantly by users.


4

Option 1: Ditch Visio and draw them by hand and scan them in. I often hand draw documentation these days for clients who appreciate the cutom-look, quick, low-cost, multiple-iteration approach. Option 2: Create the stencils yourself. I've used this approach in network diagrams when I wanted the server icon to represent a web server by adding a world icon to ...


4

Making a SharePoint site fully responsive while keeping all the collaboration functionality is very hard (if not impossible). To overhaul the standard HTML you need to modify the master page and create custom page layouts. Even when doing a complete overhaul you will still have limited control over the HTML that the SharePoint webparts generate. To make ...


3

Workflows The last option I'd go with is the workflow: workflows are slow, buggy, do not work at all when there's a lot of them running, complicated to debug, and most of all they completely disturb the users since they're visible in the UI (with a messy UI). Why would a background task be visible in the UI? In adition, conceptually, your task is not a ...


3

Agree with Bil. Web parts, web controls, application pages etc should only be the UI layer that calls into a layer that is agnostic of the original calling context; calling context could be an event receiver, console application, timer job, workflow, etc. Always ensure that this shared layer you call into does not have a dependency on SPContext.Current ...


3

The class you need to override is 's4-ca s4-ca-dlgNoRibbon'. This is the runtime class that comes from the corev4.css . This class contains a style with background-color set to white and background-image set to 'none'. Try changing this class through an override by the following two approaches:- Dedicated Custom Layout Page - You can create a custom ...


3

It sounds like something is wrong with your setup. Can you try creating a new site collection and making yourself admin or something (to make sure you have the proper rights)? Like you said, you are seeing the right stuff in the Design Manager > Master Pages menu, and sounds like the snippets aren't working either. Your comment about the settings gear ...


3

Add New Item and add Sharepoint/Office Module type in project Add the Folders and Files to the Module In the elements file use this format:- <?xml version="1.0" encoding="utf-8"?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <Module Name="Scripts" Url="Style Library/Scripts"> <File ...


2

Try adding a Script Editor web part to the top of the page, edit the web part, click on "Edit Snippet", and add your style block there. SharePoint strips some things out of the main content areas, but you can effectively add style blocks, links to style sheets, script blocks, and links to script files in a Script Editor web part.


2

For what I have seen so far, the need for three different web applications generally comes from the authentication requirements more than scalability/performance requirements. Ofcourse there is a performance hit if we isolate the app pools for different web applications as they end up reserving more memory. However, you get the option of configuring ...


2

I partially agree with all of the above answers. However, there are a few things I would do to navigate this path while mitigating the risks. Be careful with needless masterpage customizations. - Instead you can use a Content editor web part to inject your custom code into your landing page. I cannot emphasize strongly enough how important having this kind ...


2

You didn't specify a SharePoint version so here's a round-up of authors & books you can trust For SharePoint 2007 : Professional SharePoint Design http://www.amazon.com/Professional-SharePoint-Design-Jacob-Sanford/dp/047028580X/ref=sr_1_45?ie=UTF8&qid=1363205063&sr=8-45 This one was handy back in the 2007 era. For SharePoint 2010 : ...


2

I inspected the green box with the F12 developer tools and found it: The outer box has id="Ribbon.Calendar". You can search for that in the markup to further inspect the inner elements. Edit Why can't you target them? I just did. I tested with: #Ribbon\.Calendar { font-size:12px; } Is it because you aren't escaping the .? Special characters in CSS ...


2

Alex: Some of the jQuery effects are quick to implement and can give some sizzle. jQuery is cross-browser, so little risk there. I also have a stock set of CSS which I can drop into a master page and customize very fast, letting me reskin SharePoint in about an hour so that people don't even realize it's SharePoint anymore. Just changing some colors and ...


2

jQuery is your friend and should be your best buddy when it comes to spicing up a UI (especially SharePoint). Be sure to check out the entire jQuery for Everyone series on End User SharePoint. Also check out the series on converting a free CSS template (Jet30) to SharePoint. Very awesome work! (sorry, link tool not working for me right now) jQuery for ...


2

Well you could mix various Windows version as long as they are using same architecture (32/64bit). But I would recommend an upgrade to 2008 because of following: to ease and uniform patching of your systems SharePoint 2010 will only support Windows 2008, it will be easier to upgrade if you are running 2008 already



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