If you're trying to brand/customize SharePoint you might want to check this out. It's a stencil for Visio that lets you do your design without having to work in SharePoint, HTML, or a graphics program.
Get link
Facebook
X
Pinterest
Email
Other Apps
Comments
Anonymous said…
thanks, but these stencils/templates look like they are for SPS and WSS2, not MOSS2007 or WSS3.
I'm sure one could easily modify the templates to suit their needs for MOSS/WSS.
Thanks for the comment, but I still believe this can be a useful tool to quickly mock up a page/site for a client when you don't want to have them sit and watch you do the actual customization.
Given the date of the blog post I would also assume that this was originally designed for SharePoint '03, but it doesn't take a lot to see how this could be of use for a 2007 implementation.
There is a huge collection of SharePoint shapes for Visio at http://www.visio-for-sharepoint.com There are 3 main libraries for Architecture, Design and High Level Design. All-in-all more than 1,200 shapes with dozens of templates too. Not Free, but well supported for SharePoint professionals. Well worth a look.
I updated my page layouts that I deployed as a feature, but found that I could not overwrite the Layout File. The solution was to add a new page layout and then you would have to associate the new layout with every page on your site that used it. Obviously with a site of any size you'd have a lot of manual work to get this done, so doing it programmatically makes for a much better (and thorough) approach. After you've got your new page layouts, you could do something like this (in your event receiver class): public override void FeatureActivated(SPFeatureReceiverProperties properties) { //replace current page layouts with new page layouts on all pages SPWeb web = SPContext.Current.Web; SwapPageLayout(web, "FullWidthContentWithTitleV1.aspx", "FullWidthContentWithTitleV2.aspx"); } private void SwapPageLayout(SPWeb web, string oldPageLayoutName, string newPageLayoutName) { PublishingWeb pubWeb = PublishingWeb.GetPu...
If you've gotten sufficiently comfortable generating solutions with STSDEV, you've probably found that debugging doesn't seem to work. The reason is because the DebugBuild configuration is the only configuration that includes Debug code. Here's how to set up your project so that you can debug the other builds: Go to your Project Properties, click the 'Build' tab and turn on 'Define DEBUG Constant' and 'Define TRACE Constant'. Then click on the 'Advanced' button at the bottom of the Build configuration screen and change the 'Debug Output' value to 'full'. This tip came from the STSDEV discussion forum .
I had a customer who accidentally synched a (very large) SP Online library and then decided they didn't want the files on their PC anymore...so they deleted them and were shocked to learn that they'd been deleted from SharePoint too! Thanks to PnP Powershell you can use the following to restore a batch of files quickly (and filter). First, you'll want to make sure you only select the files you want to restore. I used a combination of filtering by the person who deleted the files and the date they were deleted, e.g. Connect-PnPOnline https://yourtenanturl $restoreSet = Get-PnPRecycleBinItem | Where-Object { $_.DeletedByEmail -eq "imsorry@company.com" -and $_.DeletedDate -gt "1/1/2019" } Make sure you have a fairly updated version of the PnP Powershell module as the objects that come back have more properties populated than in older versions so you can do more powerful filtering Next you can restore the files like this: $restoreSet | Rest...
Comments
I'm sure one could easily modify the templates to suit their needs for MOSS/WSS.
Given the date of the blog post I would also assume that this was originally designed for SharePoint '03, but it doesn't take a lot to see how this could be of use for a 2007 implementation.