Open Source and Free Tools, Web. Parts, Utilities for Share. Point 2. 01. 0 and Share. Point 2. 01. 3. The Share. Point 2. 01. 0 Visual Studio 2. Extensions project (CKSDEV) is a collection of Visual Studio templates, Server Explorer extensions and tools providing accelerated Share. Point 2. 01. 0 development based on Microsoft's new Share. Point 2. 01. 0 development tools.. Category . sharepoint,Visual Studio 2. VS2. 01. 0,CKS,SP2. Share. Point Dev Tools. Customizing the Display of a Share. Point 2. 01. 0 Blog. I’ve changed pages countless times in Share. Point Designer, but this case, where I wanted to make a relatively small change to the home page of a Blog site, proved especially onerous. In most cases, overriding the default XSL is as simply as editing what’s there and saving your changes. It would seem that the team that works on blogs doesn’t chat with the rest of the product group, because blogs work differently. Blog pages use an XSL file called blog. Pictured: SharePoint mobile app is now available on iOS, coming to Android. On May 4th, Jeff Teper unveiled our new vision and. Open Source and Free Tools, WebParts, Utilities for SharePoint 2010 and SharePoint 2013. One of my users has a SharePoint site with a list called Admin Tips, currently with 45 tips (list items). She has a List View Web Part (LVWP) on the main site page to. Blog site for Gary LaPointe, the PowerShell/STSADM expert for SharePoint. So one of the things that you may notice when you create a new site collection in SharePoint Server 2010 based upon the Publishing Portal is that your initial options. Creating SharePoint themes used to require editing CSS style sheets manually or using a tool like SharePoint Designer. Furthermore, packaging and deploying. How to send Real Meeting Requests from Sharepoint 2010 – Part4 Usage: Here is the links for How to send Real Meeting Request From Sharepoint 2010 Series. All I wanted to do in this case was display a different column instead of Created By (@Author) . Because in many organizations someone different that the author is the person who types the post, we had added a Written By column to the Posts list. The logic was simple: if the Written By column had a value, show it, otherwise show the Created By column as usual. I wanted to keep the XLV Web Part in place in case we needed to work with it in the future, plus the markup it emits is a bit crufty and I didn’t want to have to replicate it all with a custom DVWP. I don’t want *you* to go down those rat holes, so here’s what ended up working. Open the page in Share. Point Designer, position your cursor on the XLV Web Part which displays the posts and in the List View Tools section of the ribbon, choose Customize XSLT / Customize Entire View. This pulls the XSL from blog. However, don’t go down that path; there be monsters. Instead, find the line. This will open the blog. Share. Point Designer window for the root of the Site Collection. This is handy, because you now want to save a copy of blog. Document Library in the root site of the Site Collection. I usually create a Document Library called XSL anyway to hold frequently- used XSL templates, like the ones I have in my SPXSLT Codeplex Project. I named my copy Blog. Written. By. xsl. Close the default. WITHOUT saving it. See, no monsters. Since we had added a new custom column called Written By, I needed to add it to the View. Fields section so that the XLV Web Part would retrieve values for it. View. Fields>. < Field. Ref Name=. Yes, that customizes (or unghosts) the file. I’m OK with that. Back to the Blog. Written. By. xsl file I saved above. I found the section of the XSL where Created By (@Author) is emitted. In the Tool Pane for the List View Web Part which shows the blog posts, I went to the Miscellaneous section and added a link to my XSL file in the Xsl Link field. In my case, since it was stored in the root of my Site Collection, the link was /XSL/Blog. Written. By. xsl. Then I saved the change and voila! Exactly what I wanted. There are other ways to accomplish what I did here with a deployable feature and managed code, etc. In this case, it was a small farm with only a production environment and a single blog where we wanted to make the change. All you enterprise types just gasped, but this is the reality in many organizations. Obviously it wasn’t all as simple as what I outline above. Here are some of the things I found: If I edited the XSL in Share. Point Designer (after the Customize Entire View step), my changes worked great in Share. Point Designer. However, when I went to the browser, I saw the page the same way it had looked before. I believe this is because the blog. If I tried to add the XSLLink in Share. Point Designer, which ought to work, it always stripped off the leading / in the link to the XSL file. This meant that the link was invalid and blog. The sequence I ran through above seems to be the only reliable way to make this work. It’s pretty quick (after 4. I did it twice as I was writing this. Of course, I had a copy of the original default. Never edit the default files without making a copy. Here are two threads from the MSDN Forums that helped a bit. I didn’t have any luck with the ddwrt: ghost=.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2016
Categories |