SharePoint
Remove “View all site content” and “Recycle Bin” from SharePoint quick launch
Change:
<Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="ViewFormPages">
to:
<Sharepoint:SPSecurityTrimmedControl runat="server" PermissionsString="ManageWeb">
OR
http://www.wagnerlive.com/mark/Lists/Posts/Post.aspx?List=c0001cfc%2Dd84a%2D4be0%2Db437%2D6a625925a9d5&ID=36
No Left Navigation when new web part pages are created in sharepoint
Republished from http://geekswithblogs.net/naijacoder/archive/2007/09/23/115552.aspx
Creating web part pages or basic pages on the fly in sharepoint is pretty easy just with a click of a button 
But here comes a little set back you won’t get to see the left navigation menu when you view the page 
But here comes a solution for this you will notice that the page’s layout and design are all inherited from the master page
but the side navigation is not.
The cause i reckon is the left side navigation is defined in the Master Page in the “PlaceHolderLeftNavBar” content place holder and templates for Web Part Pages shipped with SharePoint are overriding this content place holder and delete its content.
The solution for this is to change the page so it will not override the menu place holder, but inherite it from the Master Page. The place holders we are interested in are:
“PlaceHolderLeftNavBar” and “PlaceHolderNavSpacer”.
Start by opening the Sharepoint Designer
Open the web part page you want to add the menu to.
In Code view – Look for the following lines and delete them:
<asp:Content ContentPlaceHolderId=”PlaceHolderLeftNavBar” runat=”server”></asp:Content>
and
<asp:Content ContentPlaceHolderId=”PlaceHolderNavSpacer” runat=”server”></asp:Content>
Save the file. You will get a warning saying you are about to customize the page .Just go ahead.
Hope that svaes time.
What happens when a SharePoint solution is installed & its features are activated?
This post applies to a SharePoint feature being deployed through a solution applying to the site level. You may download the sample solution and read how to build this feature.
First, to install the solution:
> stsadm -o addsolution -filename C:\Projects\Brian\BrianTestFeature4\BrianTestFeature4\BrianTestFeature4.wsp
What happened?
The solution was registered with the SharePoint engine and can now be seen in Central Administration > Operations > Solution Management. The status should be Not Deployed.
Next deploy the feature to a web application. This can be done by clicking on the solution name of the solution you just added in the Central Admin page you are on from the next step.
What happened?
The following dir was just created:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\BriansTestFeature4\
What’s in this new directory?
So far only feature.xml & elements.xml. Where are the rest of the files from my feature?
The assembly for my feature was installed to:
C:\Inetpub\wwwroot\wss\VirtualDirectories\80\bin\BrianTestFeature4.dll
Now my feature is available to be activated on this site. If I navigate to my site features administration page (Portal > Site > Site Settings > Site Features) I will now see my feature in the list of available features. Status will be empty.
Next I can activate my feature on my site. From the site admin page we navigated to in the last step, click Activate on the feature. The status should now be Active.
What happened?
The content in my feature just got deployed to:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\BriansTestFeature4\WebForm3.aspx
An entry pointing to this file was also created in the SharePoint content database so the virtual path provider can actually find this file. So now I can navigate to my new aspx. This file is at the root of the site because that is where my elements.xml file told the file to be deployed to.
http://cibmtr-dev01/dbtc2/webform3.aspx
Next deactivate the feature on the site by clicking the Deactivate button on the screen that we formerly clicked Activate. Now the feature should be deactivated.
What happened?
Well…it appears as if nothing has happened. If you hit the WebForm3.aspx from the browser everything still renders just fine. After a bit of research it appears as if I will have to write custom code into the FeatureDeactivating method of the feature receiver to remove my content from the content database. I will have to add an additional post once I figure that out.
Since nothing happened on deactivate, what if I retract the solution from my site? It appears that retracting this solution has removed my dll and aspx page from the file system. However, since I can still see WebForm3.aspx in SharePoint designer, apparently retracting the solution does not remove the page from the content database. Again, this looks to confirm that I need to add a custom feature receiver to remove my files from the content database.
So how do I remove these content files without adding a feature receiver. It’s a pain, but you can remove any leftover content files without coding a feature receiver to do it. Since the big problem is that the content files have been provisioned in the SharePoint content database you need a way to get into this database to remove the references to these files so that the virtual path providers will no longer know about the files. How do we do this? With our favorite tool SharePoint Designer *and the crowd falls silent*. Yeah, I hate it too, but what are you gonna do? If you open your site in SP Designer and find the content files that your feature provisioned and failed to remove, you can simply delete them through this tool. That will remove the references from the content database and your feature will be fully removed.
What’s Next?
That’s about all for now. I will try to follow-up with another post on feature receivers once I have a chance to play with that a bit more. But for now, this should be enough to get a simple feature installed for you.