I have a subsite that I wanted to give over to our Documentation group to maintain. It is a publishing site with a custom page layout. I tested the security with a test user account. I gave the test account full control access to the subsite. When signed in as the test user, I could see the Site Actions button, see pages, security, etc. But when I would try to add a page, I got an Access Denied error. I tried it on a different subsite to just see if there was something wrong with that particular site, and I still got the error. After digging and poking around the web, I found a reference to give the user read access to the Master Page gallery. I gave the test user read access to the master page library and then signed back in and voila, it works!
Sometimes SharePoint just doesn’t make sense, with all the hoops you have to jump in to do seemingly simple things. Like add reusable content lists to a page layout. All i want to do is just add the references to two reusable content lists directly into a page layout so they are there when i make my pages. Apparently, to do this requires custom programming, still waiting on the estimate. In the old days, I’d simply add a library item into a Dreamweaver template and call it a day. Bah.
As I have mentioned before, my team and I are working on redesigning our corporate intranet in SharePoint. Our programmers are learning .Net and have been getting comfortable coding in it and creating applications. They haven’t really taken the time to figure out how to code within SharePoint though, and this leaves us with a problem. There was a lot of custom code on our old intranet and SharePoint doesn’t have an out-of-the-box solution for everything. My programmer started looking into creating a custom webpart but decided it was a pain and due to time constraints, we came up with an easy solution that works quite well.
He created a .net page with the necessary code for the widget and we pulled the code into the Sharepoint page using the Page Viewer webpart. We currently have two of these on our home page. One randomly loads a different slideshow image that upon clicking the image launches a slideshow in a popup window. The other loads stock quote data that is pulled from a web service.
I’m sure that hard-core programmers and SharePoint developers will weep at this hack, but for a small team with limited resources and time, this works quite well for us and was way easier to implement than a custom webpart. I have also used the page viewer webpart to pull in a Google map. On our old intanet, I was able to add the iframe code that Google Maps generates, but SharePoint seems to hate iframes and wont render them, so the page viewer webpart was a decent workaround here as well.