I have replaced the default Search Box in SharePoint using Delegate control.
Now my delegate control has a Text Box and a Button.
On Button Click it should take the users to a web part Page wich has all my Custom Web Parts added.
But this Web Part page should be accessible from every site in sharePoint as my Custom Delegate control can be added anywhere within the farm.
Ex: like OSSSearchResults.aspx but my custom web part page can be modified by users.
Can some one tell me how to do this?
You can put url of the custom results page in Search settings in site collection administration section.
Also You can customize the default search results page with out of the box webparts like SearchCoreResults webpart, refinement pane, search box etc.
But my question is can i add a custom webpart to this results.aspx.
Related
I'm currently working on a registration form for a conference. I made a form for the SharePoint list using the PowerApps link in SharePoint (web). I published the form, and now I can't find it on the PowerApps site when I go to open applications for editing. I can edit the form using the edit link in my SharePoint list, but I'm unable to find it anywhere on the PowerApps website... Any ideas?
Did you use the "Customize forms" option or "Create an App"?
If you used the former, then your app will not be listed if you try accessing it through the Powerapps site or Mobile App.
There is a difference between these two. Customize form is specific to the list while create an app creates a new app for you on powerapps using the Sharepoint list as the datasource
I am able to add webpart zone snippet (from design manager) in my custom page layout. Although it gets added on the page layout.
But when I click on add a webpart in the my custom webpart zone section on the aspx page nothing happens.
What could be wrong?
I tried to add a custom created webpart to a customized team site which I then saved as a template. The webpart in question worked fine with the original site. However, when I created a new site based on this template(within the same server that the webpart in question was deployed to) the area which was supposed to contain the webpart was blank. Is there anything I'm missing or is it not possible to deploy a custom webpart into a custom site template?
Just guessing here because I haven't tried it but when you add a webpart to the page you are essentially customizing that page for that specific site. The webpart location is stored in the content database just for that individual page.
When you save a site as a template you are just saving the structure so when you provision a new site the customized page isn't there.
On MOSS mysites I want to be able to create a new tab that every mysite user can view, it should show a web part page.
How can I do this?
Create a site collection as a parent to all the MySites. Or to put it the other way, make the MySites a subsite to a site collection that has the site that you want all the MySites to see.
In your Shared Services Provider (Central Admin/Shared Services Admin), look under User Profiles and My Sites. You can select Personalization Site Links and point to an existing site that contains the web part page you want to display.
You can also filter the display using the Audiences functionality so that it only displays to a select group of users.
In regards to #Brian Meinertz's comment. This a detailed blog on Microsft's site about feature stapling:
Customizing MOSS 2007 My Sites within the enterprise
I've been asked to customize the following:
In the left quick launch menu, is it possible to remove these menus: Documents, Lists, discussions and Sites? These menus need to be remove/disable/hidden by default when the user creates it's My Site.
In the site action menu, is it possible to remove/disable/hide the Create menu, so the user can't create any kind of subsite, lists, etc..?
I'm working with MOSS 2007.
As you are using MOSS 2007, you can customise the menu on the left by going to Site Actions -> Site Settings and Navigation in the middle.
Sharepoint Navigation on MSDN
Create rights are based on the roles assigned to the user logged in, so not giving the user create rights should remove this from the menus.