Hot answers tagged

11

The Publishing Features need to be active on the site collection for the web part to appear. It can be activated from the Site Settings, Site collection features screen.


11

You can use ParameterBindings to this purpose. <ParameterBinding Name="Language" Location="Resource(wss,language_value)" /> This will return "en-us" for English locale in xsl:param "Language". Also, you can pass whole resource values this way. You can read more about this in Stefan Stanev's blog: ...


6

You'll need to make sure that the xsl:stylesheet declares the ddwrt namespace. To do this, you'll need to add this to your xsl:stylesheet declaration if it isn't there already, though in your case we know it isn't because you're getting an error: xmlns:ddwrt="http://schemas.microsoft.com/WebParts/v2/DataView/runtime" You can see more details on this idea ...


6

I'm guessing this is SP2013, as I myself have only encountered this in SP2013. My personal explanation to this: SharePoint 2013 Content By Query web part has a minor bug in its early releases. When returning no items it accidentally breaks the HTML structure of the page. My solution: Open the ContentQueryMain.xsl in SharePoint Designer. Find the XSL ...


5

You'll need to use an additional XSL schema called ddwrt. Here is a blog with a good and simple walk-through <xsl:value-of select="@ArticleStartDate"/> You get back a pretty nasty looking result 2009-03-23 00:00:00 However if you use the “FormatDate” function, you can make this look a lot better. <xsl:value-of ...


5

You can use PageQueryString and/or PageFieldValue in the CQWP. Here is an exmaple


5

Your quick question deserves a quick answer: Yes! Bullet images are defined in CSS, so you can override the formatting by adding your own CSS for the elements you want to change.


4

The Content Query web part is included in the SharePoint Standard SKU, which implies MOSS for the 2007 version of the product. | 2007| 2010| ----------|-----|-----| Standard | Y | Y | ----------|-----|-----| Foundation| N | N | I've tried to make a complete reference table of all the SharePoint 2010 out-of-the-box web parts.


4

Don't be afraid of XSLT. This is going to give you a tremendous amount of power without having to develop or deploy anything in return for a little effort to understand it. I always recommend starting with an identity transform so that you can see the XML that is coming in, and then start adding templates to process the nodes you are interested in. Visual ...


4

After looking for ages for the answer to this I stumbled on it minutes after posting this question... Anyway, the answer is here: http://blogs.msdn.com/b/joshuag/archive/2009/03/25/custom-date-formats-in-sharepoint-xsl.aspx Summary: Reference the ddwrt namespace at the top of the itemstyle.xls ...


4

To add your configured web part to the web part gallery, go to Site Settings and then to the web part gallery. You can then upload your .webpart file - the gallery behaves like a normal document library. This is fine for one-off or occasional use. To do this in a repeatable way you would need to develop a feature, to deploy the webpart definition to the ...


4

Please try this: http://www.gloiretech.com/sharepoint-tools/content-slider-sharepoint/


4

Because SharePoint convert special characters in the internal name. _x0040_ = @ - More about mappings for non-alphabetic characters So that means when that column was created, its title was @Active.


4

See if this helps: <xsl:for-each select="rows\row"> <li> <a> <xsl:attribute name="href"> <xsl:value-of select="{@FileURL}" /> </xsl:attribute> <xsl:attribute ...


4

A screenshot for SP 2010 may say more than 1000 words in the linked article about SP 2007.


4

Following snippet can be used to reference the jQuery in your XSLT webpart. Inline Script Block: <xsl:text disable-output-escaping="yes"> <![CDATA[ <script type="text/javascript"> (your JavaScript code here) </script> ]]> </xsl:text> Script Reference Block: <xsl:text ...


4

You wanna target the specific webpart where you wanna change the link color, otherwise every link on the page will change font color. Use F12 Developer tools to find the ID of the specific webpart you wanna change the link text for. Insert the name/ID instead of my example (#WebPartWPQ5) and then use the CSS i provided below (SP2013). <style ...


3

When you use QueryOverride, you can no longer modify all query related values using a browser. So you will need to fix the query, reupload the webpart, and repeat those two until you have a working web part. Use the internal Field name, yours look like the display name which won't work. For Content Type filtering, best is to use ContentTypeId. ...


3

Blogs and Comments are two different lists in the Subsites. So the CQWP only gets you the Blogs You could try quering on a common contenttype to get everything.. but it is going to be some hairy XSLT SP2013 DisplayTemplates (JavaScript programming) instead of the CQWP may be a more helpfull approach. XSLT is something for the past. ...


3

Full Image url is available in property EncodedAbsUrl You can change the webpart property and set this.


3

You can use following code in the display template <div title="_#= $htmlEncode(line4.defaultValueRenderer(line4)) =#_" id="_#= line4Id =#_"> _#=STSHtmlDecode(line4.value)=#_ </div> Source - https://ingessharepointnotes.wordpress.com/2014/03/04/sharepoint-display-templates-display-enhanced-rich-text-field/ Another example var desc = ...


3

From MSDN for SharePoint 2013. If you want complete control over how a Web Part appears on your site, and if you want that Web Part to appear on all pages of a certain type, add the Web Part directly to a page layout. If you want a Web Part to appear on all pages in a site, you can also add a Web Part directly to a master page. Try with this ...


3

You can use the XSLT <xsl:sort> element to customize your sort order. https://sites.google.com/site/icsharepoint2010/xslt/sorting-in-xslt <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:output method="text"/> <xsl:template match="employees"> <xsl:apply-templates> ...


3

Content By Query Web Part is XSL based, by default, Title, Description, ImageUrl, and LinkUrl columns (if present) of the items that the query returns are rendered. The Web Part renders the ImageUrl column and the LinkUrl column as an image and as a hyperlink, respectively. If you want to query for custom content types and render specific columns from ...


3

Modifying the underlying XSL files worked in SP2010: http://blog.kappasolutions.ca/blog/post/2010/09/12/How-to-Display-HTML-in-Content-Query-Web-Part.aspx Specifically, setting disable-output-escaping to yes in ItemStyle.xsl. ie. <xsl:value-of select="@Something" disable-output-escaping="yes" /> I haven't tried it in 2013 yet, but this article ...


3

I was able to do it by modifying the ContentQueryMain.xsl file to insert non-repeating markup before and after content query as shown here. http://blog.mastykarz.nl/wrapping-contents-content-query-web-part-additional-markup/


3

About Social Comments In comparison to page fields (Page Content, Title, Page Image and etc.) that are inserted into the “slots” of the page layout and associated with the content type of the publishing page, social comments are stored separately. Social comments are stored in separate DB and the comment entry is associated by the page Url on which ...


3

It migth be more efficient to use Camlex.NET. It more understandable for new to SharePoint developers. Stramit SharePoint Caml Viewer migth be helpfull if you tried to write caml by hands, nor using UI or C# code.


3

This is not a CSS issue. I don't know how to fix it properly, but I can add this information: Issue occurs in IE 9 with hardware acceleration turned on for any SharePoint 2010 page with a content query web part added. Affects SharePoint menus (Site Actions) and some other forms of drop-down menu add ins. The reason the IE7 mode etc. works, you're then ...


3

Since you're working with the Anythingslider, which is jQuery-based, you could also consider using jQuery all the way. My SPServices library would allow you to pull list items easily using SharePoint's Web Services. Storing that content in different sites would pose no problem, as long as your permissions were set correctly. You could store both the content ...



Only top voted, non community-wiki answers of a minimum length are eligible