Microsoft Sharepoint Server 2007, 2010 & 2013

Open your master page. Switch to Code View. Search for "TopNavigationMenu". This should take you to the global navigation (top nav) instance of AspMenu. Using Intellisense in the code view, or using the Properties pane, add the following property to the AspMenu tag: DynamicPopOutImageUrl="insert image URL/path here"So your code should look like: Runat="server" DataSourceID="topSiteMap" DynamicPopOutImageUrl="/images/myimage.gif" >

At this point you have two options: 1) hide the View All Site Content link for everyone or 2) hide the View All Site Content link for everyone who does not have Full Control to the site. I prefer the second option because it gives administrators the ability to still have access to the link. Option 1 – Hide View All Site Content for everyone: Click on the View All Site Content link in the Design view. This will select the Sharepoint:SPSecurityTrimmedControl. In the Tag Properties pane (typically located in the lower left), change the Visible Property to False Option 2 – Hide View All Site Content for anyone who does not have Full Control: Click on the View All Site Content link in the Design view. This will select the Sharepoint:SPSecurityTrimmedControl. In the Tag Properties pane (typically located in the lower left), PermissionsString="ViewFormPages" to PermissionsString="ManageWeb" Save the page and Check-in and publish

Automated" email response to the applicant who sent their Comments OR Resume into our Job Site email address 1. Create a list with Name, Email, column 2. Open Sharepoint Designer to the site where list exists. 3. Create a New workflow from File->New->workflow. 4. Give the workflow a name 5. Decide if you want the workflow to Manually, Automatically, or whenever an item is changed. My suggestion is "Manually" while in development at the minimum. This will keep you from having to continuously upload new documents to test the workflow. You can upload one "test document" and keep using it, by manually starting the workflow on that document. If you want "Automatic" starting of the workflow, turn that on after you are done testing/building, if you'd like, but if you are building this workflow on an "already existing" document library, you don't want your workflow to inadvertently run while you are building it, should someone put a fi

Debugging SharePoint can be problematic at times, it does like to hide debugging information from you. The bain of my life recently has been “An unexpected error has occurred” with nothing written to log files, trace or the event log. Normally I can debug the problem with a little commenting & narrowing down of the problem, but today I have managed to get rid of that error screen completely. The solution is to change a single entry in web.config, by modifying the line… SafeMode MaxControls=“200“ CallStack=“false“… to… SafeMode MaxControls=“200“ CallStack=“true“… You will also need to set custom errors to 'Off' . You will no longer see the “An unexpected error has occurred” error page and instead you get a lovely ’standard ASP.Net error page’ with the stack trace and everything…development has got that little bit easier