Content Query Ticker Web Part
This web part provides a ‘newsticker’ for SharePoint, although it’ll actually query for news, documents, or anything else you can query for with the Content Query Web Part (CQWP). In fact, it’s just a configuration of the CQWP, which also uses jQuery for animation and stuff. Typically web sites use this for displaying news or announcements, but you can use it to query for any SharePoint content type(s), as you would with the Content Query Web Part.
Display Mode
Page Edit Mode
The Content Query Ticker Web Part looks like this in operation…
Comes with styles for:
- Title only
- Title and Description
- Group, Title and Description
- Roll-up Image, Title and Description
It does require MOSS 2007, and you do need to enable the Publishing Infrastructure on your site collection.
Latest Version 1.0.0, April 20th – download here – Source
Hello Andy,
This looks fantastic, thank you for allowing download, however I am having problems making it work and wondered if you could help please, I have used the stsadm tool to add the solution to Sharepoint restarted IIS enabled the feature (we already have the publishing features enabled).
I can add the webpart to the page but it just comes up saying unable to display this web part and when you try to modify it you get a could not load XSL file error.
Many Thanks
Alan.
Hi Alan,
As well as adding the solution, you have to enable the feature. Go to your Site Collection Features administration page – has it been enabled?
Hello Andy,
Thank you for your quick reply, we have enabled the feature on the site collection, however we are not so sure on whether or not we have installed the solution correctly.
The steps we used are as follows (on the MOSS server under the sharepoint admin account)
stsadm -o addsolution -filename c:\CQTickerWebPart.wsp
stsadm -o deploysolution -name CQTickerWebPart.wsp -allowgacdeployment -immediate
iisreset
We then enabled the feature on the site collection which seemed to work correctly.
The site collection that we are using is https://comp.dom.org/sites/sitecollectionname
Many Thanks for your help
Alan.
Hmm. Looks okay. If you’ve got SharePoint Designer, try looking in the Style Library for the root site of your site collection. That’s where the XSL gets installed to.
I don’t know if it’s too late, but it might be worth examining your logs to see what happened (and if there were errors) during deployment of the solution, and activation of the feature on the site collection.
Hello Andy,
Thanks for the advice, all the files appear to be where they are supposed to be and I can not find any logs with errors, however I may not be looking at the right logs! Looking at the Site Collection Features, the only ones not activated are Server Search Web Parts and Three-state workflow all other are enabled.
We are running the Enterprise edition if that makes any difference.
We also have versioning running.
The only other thing that springs to mind is; do I need to make it a trusted source (Sorry not quite sure on the correct term, but remeber seing something mentioned about adding a line to a web.config file)
The other thing i have noticed is that the feature does not appear in the Site’s feature list only the site collections feature list.
Sorry to be a pain and thanks for your help
Alan.
Yes, that’s all correct. It was developed on Enterprise, and it is a Site Collection feature. I’m not sure what the issue might be.
This web part should not require changes to the web.config; it’s just the Content Query Web Part with some fancy XSL and a bit of JavaScript.
I wonder – if you check the Style Library for the XSL, is it that the XSL file needs ‘approved’?
Alternatively, does it look correct if you open up that XSL file?
Final thought – it’s a bit rubbish, but have you tried uninstalling and reinstalling it?
If push comes to shove, I could talk you through a manual installation, but that would be less than ideal.
From my experiences with content query webparts it seems that you have not modified the absolut pathes. In the CQWP you set the link to item.xsl and main.xsl, but it’s not possible up to my knowledge to make them site-relative. Therefore, you have to write a feature receiver that sets the correct URL. Otherwise you get the exeption shown above.
Hope that helps
Regards
René
This is a great solution. I really like it.
I was wondering if it is possible to have the option of changing to the next item with a next or previous button instead of the ticker based on time.
Is that possible?
Yeah, you could do that. It would mean rewriting a chunk of the JavaScript, but it wouldn’t be that hard, and what I’ve made would make a good starting point.
I don’t intend doing this, though, unless there’s lots of demand!
I understand that you wouldn’t want to rewrite it as this is already a great feature.
I have tried to rewrite some of the JS but I am having a problem calling a function from the Main.xsl
I have updated the JS so that it doesn’t run at the start
I added this to the OuterTemplate in Main.xsl
Is this way off?
Thanks for any help you can provide.
Also if I get this working I will post it up here to share with everyone.
sorry my last comment removed the html I put in. Here is What I added to the mail.xsl
img onclick=”resumeTicker()” src=”\_layouts\images\PLSLBACK.GIF” border=”0″ alt=”none”/
with the around it of course
I implemented this on my site but it conficts with another jquery menu I have on my site. I read about something to do with this not using a unique variable. Is this something that can be fixed
Hi,
any hints on how to manage this in WSS 3.0?
Sorry Kelly, it won’t work in WSS 3.0. WSS3 doesn’t have the Content Query Web Part that this web part is based around.
Hi
I really like this web part and I have had it working perfectly on my machine at home however when I attempt to deploy to my works environment it gives me the following errors:
*****
Unable to display this Web Part. To troubleshoot the problem, open this Web page in a
Windows SharePoint Services-compatible HTML editor such as Microsoft Office SharePoint Designer. If the problem persists, contact your Web server administrator
****
and when I open “modify shared web part”
*****
Could not load XSL file. The system cannot find the file specified. (Exception from HRESULT: 0×80070002)
Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.
Troubleshoot issues with Windows SharePoint Services.
****
The web part successfully deployed and central admin states that to me, the web part is activated as a site collection feature and appears in the gallery.
All the assets are located in the style library which as admin I have full control over, each item is also published.
The frustrating thing is that I have instgalled this on my local machine at home yet at work it fails. The only significant difference is that the local machine is
http://someurl/
and the one at work is
http://someurl/sites/somesite
The style library for each of the above examples is situated as follows:
http://someurl/style library
and the one at work is
http://someurl/sites/somesite/style library
Any help appreciated