1. We cannot modify
OOB defaulttemplates.ascx as this would be unsupported
2. Make a copy of
defaulttemplates.ascx under CONTROL TEMPLATES FOLDER of 12 hive
and rename it to CustomDefaultTemplates.ascx
What exactly needs to
done/Resolution:
1. To hide “Respond
to this Survey” if a user has already responded to the survey,
Create a class which inherits from the Microsoft.Sharepoint.WebControls.NewMenu.
2. In this override
CreateChildControls and have your logic to hide unhide "Respond
to this Survey" based on your need.
3. Build the class
library and install the dll to the GAC.
4. Modify the
“ViewToolBar” in the custom ascx such that to render your custom
"Respond to this Survey" menu from the class library you created.
(Note: You need to add your assembly reference and register the tag prefix in
the
Custom ascx control.)
5. Next step is to
render the custom rendering template to the "Survey List" so
that the
custom "Respond to this Survey" menu will be rendered in the toolbar.
6. For this the
"ToolbarTemplate" property of the View should be changed in the
schema.xml file of the Survey List
definition.
7. As modifying the
OOB files are not supported, Copy the “SurveyList” folder from
12/Template/Features and paste in the
same place as “CustomSurveysList”.
Change the feature ID of the
“CustomSurveyList”
8. Open the
schema.xml file available under survey folder of “CustomSurveysList”
and add the
“ToolbarTemplate=CustomViewToolBar” attribute to the “View BaseID=0”.
In
SharePoint 2013 Dev dash has helped the admins to help troubleshoot a
lot of
performance issues .
The Developer Dashboard can now be extended by injecting custom
JavaScript code into the developer dashboard window.
Your current Contributor Settings
prevent you from creating, editing and deleting workflows
Probable Cause:
By Default the Contributor Settings
will be enabled on your site. You will notice this in the SharePoint Designer
task pane.
Resolution:
This is because your account is
present in the Content Authors group, which may “Restrict the use of some
features” as the task pane mentions. This behavior can be modified if you turn
off the "Contributor Settings" in SPD.
1. Open the site in SharePoint
Designer
2. Site Menu
3. Choose Contributor Settings.
4. Click on Disable Contributor
settings
5. Refresh the page you should not see
the message.
Important Information:
If you are a site manager or
administrator, you are probably working with various groups such as Web
designers or content authors who are working on different aspects of a Web
site. With so many groups working simultaneously, you are probably worried that
somebody might inadvertently break a site — for example, by changing the design
of the home page, modifying the style sheet, saving files in a wrong location,
or breaking the site navigation or search functionality. If you are concerned,
the good news is that you can avoid these scenarios by using Contributor
Settings to turn on and configure Contributor mode in Microsoft Office
SharePoint Designer 2007.
In Windows PowerShell 2.0 (the
November 2007 Community Technology Preview release) the PowerShell team has
taken an interesting approach to script debugging. As you know, PowerShell
doesn’t require a specialized script editor or development environment.
Instead, PowerShell users can, and do, use any and all text editors (from
Notepad on up) to write their scripts. Because of that, the PowerShell team
decided to build their debugging tools into Windows PowerShell itself; in turn,
that means that you can use the new debugging cmdlets to debug any script from
the console window itself.
June 2014 Cumulative Update for SharePoint 2013 has been released. SharePoint Foundation - KB2881063 http - //support.microsoft.com/kb...
Disclaimer
The opinions expressed on this blog are the personal views of Pratik's SharePoint Blog, and do not represent or reflect the viewpoints or policies of any past, present, or future employer, colleague, or customer, or any other entity. The posts on this blog are provided ‘as is’ with no warranties, express or implied, and confer no rights. Use of information contained within this blog, including specific technical steps mentioned herein, is at your own risk. References to specific software products, processes, resources, or companies do not imply any endorsement.
