I've built a custom SharePoint 2010 web part and deployed it to the home page of a publishing site. It's a very simple web part that just displays items from a SP list in a drop down list. The web part works fine if I'm logged in as a site owner or a member but not if I'm just a reader. The web part doesn't render at all to readers. I don't get any of the web part chrome or title, just nothing. I have other web parts (out-of-box ones) in the same zone that are displaying fine so it's not an issue of the whole zone not displaying.
As a reader, I can still view the list directly so it doesn't appear to be a problem with list permissions.
My web parts are being deployed as a farm solution, not sand-boxed and the assembly is being deployed to the GAC.
I feel like I must be missing something simple here but I'm stumped. Help.
Did you save / Check in the page after editing?
Regards,
Faiz
You may have to actually publish the page for a reader to see it
Related
I'm working on remolding my companies current exsisting Sharepoint site. I installed the SP ZAP Slideshow webpart and went to the sharepoint site to insert it, and absolutely no webparts were listed. I went into the provided Sharepoint 2010 central administration and realized that everything seems to be listed as
//usmvwc0wtf1srv.ww005.work.net/sitepages/
When the website were hosting, and it should be listing is
//usmvwc0wtf1srv.ww005.work.net/sites/
I went to the /sitepages website and all the webparts exsisted and worked, however i need to get them working on the /sites page. Is there some way to switch it so it will not default all the webparts and content i'm uploading to the wrong page? I feel as though the wrong default page is listed? sorry new to all this!
Web Parts, which you see listed and are able to insert on a page when you edit it, come from the Web Part Gallery in the site collection. They are usually installed to the gallery when you activate their site collection-scope feature. Check what features you didn't activate in the new site collection - I suspect that one of them is responsible for the installation of Web Parts you are looking for. (The scope of the feature can be site collection or site - check both.)
I have a blog in a Sharepoint 2010 site (hosted by a 3rd party), and I need to display snippets (title) of last 5 blog posts in the home page of my SharePoint site as a web part.
I have tried to pull the RSS XML of the blog and transform it with XSL, but for that to work the site needs to have anonymous access, which unfortunatelty is out of my hand, that is I cannot do that. I cannot upload a custom web part as well. I can create a Silverlight app, and host in the Silverlight web part, but for that I need to have cross-script enabaled in the Sharepoint, which is again cannot be done as the Sharepoint site is hosted by a 3rd party.
Can anyone please help me and let me know if there is any way, I can do that.
Thanks.
I have found three ways to displaying this:
1) I user use a Content Query Webpart to pull out the data from a Sharepoint Blog and make an setting to show only the top 5 items.
2) I could use XML Viewer webpart to pull the RSS feed of the blog and use a XSL Transformation to display the top 5 items.
3) I could use a Silverlight Webpart to host a Silverlight application which will read the RSS and display the data likewise.
So the limitation here is that you can't get anonymous access to the site - presumably you're using Basic or Forms authentication?
I think the way around then is either create your own RSS style web that can do authenticated access to the RSS XML feed using a service account - this then requires nothing to be installed or changed on the 'source' server.
I have created a test website that contains a single ASP.net index.aspx file that contains a gridview listing information from a MSSQL database.
I would like to have this made available as a webpart on our sharepoint intranet, how would I go about doing that?
You can just put your page under Template/Layouts and attach it to some SharePoint master page. It will look and feel like a regular SharePoint page.
Of course, that is good if you're into the quick&dirty approach :)
You will need to create a web part from the page you already have.
I would suggest isolating your gridview in a user control (ascx) instead of directly on the aspx page, it will be easier to use it in a web part that way.
To create a web part, you should probably start by downloading WSPBuilder or a similar tool that will do most of the work for you.
The following tutorial will give you the information you need on how to create a web part from a user control.
You should have no problem linking to your database or anything else. A web part behaves just like a user control.
Which web part and how to configure it to view a list from a different site collection?
Please note that I do not want to view a page but a list. For example view Announcements from a different team site under a seperate site collection.
Thank you in advance for your help.
The Data Form web part available through SharePoint designer can do this.
The Content Query Web Part (CQWP) which is part of the publishing infrastructure (requires MOSS) does not go across site collections.
Re http://www.spelements.com/spanylistview/
The problem with this one is you have to be able to INSTALL it on the server.
If you do not have those permissions, it cannot be used.
Don't bother asking if they can be obtained. They can't.
I need to provision a custom aspx page which does some work and then redirects to another page. Using a _layouts page, AKA an application page won't work since I only want this page accessible to one site collection.
I looked at using pattern #4 from blog post Application Development on MOSS 2007 and WSS V3. It feels pretty hacky, and it asks you to drop the DLL. Drop it into the bin of the site collection, and upload the file through SP Designer.
I'd rather have this page be a feature that gets included in my site definition or stapled to an existing site definition. I imagine I could use a feature receiver to deploy the files to the pages SP list. One of the comments on the blog post says as much:
Pardon my ignorance on this maybe I am
missing the point completely but
wouldnt it be easier to deploy your
custom pages by programmatically
adding them to the pages splist?
I basically, had a simple .aspx page
with a user control. I deployed it via
this method.
How can a custom page be provisioned without using a _layouts page?
I guess another option is to keep using a _layouts page, but make sure the referrer is correct.
Besides application pages, you also have the possibility to create site pages.
Site pages are in nature related to application pages, but they reside in a site not in _LAYOUTS.
The welcome page (default.aspx) is an example of such a page.
In the same way as with application pages, it is possible to do codebehind in these pages (check out AC's article on this subject, Using ASP.NET 2.0 Code Behind Files in SharePoint v3 Sites)
You can read this article regarding the subtle differences between application pages and site pages: SharePoint Application and Site Pages - Part 1 of 2
You deploy this custom page using a feature, where you specify the file as ghostable (look at the example in ACs article).