Hi All,

I was able to "Pull In" an RSS News Feed into my website using the core module.  That works fine.

The question I have is, when I check the "Allow Syndicate" box in Page Settings, I see no icon where a visitor to my web page would be able to click and subscribe?

Can someone point me in the right direction to having my content RSS'd out?

Thanks!

The syndication is done at the module level, not at the page level. So, unless a module on the page allows syndication, you won't the the button. You have to turn on syndication for the module. I think that the RSS button will appear inside of the module.

Hi Joe. Thanks for replying.

I do see a "Syndicate" link in the modules dropdown, but I'm not sure what to do with it. I can "Subscribe to this feed using..." with a dropdown that has Live Bookmarks(?) or My Yahoo...but I'm not trying to subscribe to my feed, I'm trying to get other people to subscribe to it and they can't unless they're logged in and can click the dropdown of the content. Does this make sense?

Thanks,

Mark

Which module are you using?

Sorry for not replying (I actually thought that I had!).

I am using the Text/HTML module currently. When I log in, I can click on the drop down arrow and select "Subscribe to this", however, I do not want people to have to log in to my site in order to subscribe.

Any idea?

Thanks!

Mark

Interesting, - I just tested this for the text / html module - go to module settings, tick 'allow syndicate' - all displays until you log out!

- I would suggest when logged in, click on the RSS icon to view the RSS URL - copy the URL

then go into the module settings / advanced settings / footer

Paste in the code for the RSS feed URL - but I would add this by adding the HTML code for an RSS image icon (you will need to upload this to your portal) and then add the feed URL as a link on that image.

This will then permanently display they RSS icon in the footer of the text HTML module

If you want to implement RSS feeds properly to get the most benefit, I would suggest you look at Issue no 3
and
How to create an RSS feed using DotNetNuke
(1 video - 5 min)

a news articles module is much more ideal than the text HTML module for RSS

Hope this helps, thanks,

OK, thanks Lee.  I'll give it a shot and see what happens.  I did actually look at your video and the accompanying article BTW....just nothing to show my users that they can get a feed of my content.

Thanks!

a tip -  a good promotion method is to have a separate page which lists all of your RSS feeds - ie: http://www.dnncreative.com/RSSFeeds...fault.aspx

It looks like I'm having the same problem, or similar. I am on DNN 3.01 and wondering if RSS really works in that version?

I am testing with the standard announcements module, but have also tried, and get the same kind of thing with the text/HTML module.

Just like in the tutorial on this site, I checked "Allow Syndicate?" and that goes ok.

I can, from the module drop-down menu select "Syndicate" and it opens up a new browser window (IE7) showing the newsfeed description, I can then click "subscribe to this feed" and it seems to be a valid url.

Trouble is, nothing ever seems to get published. I tried adding a new announcement, and still, the newfeed content is always empty.

I also set it up in Outlook 2007, and although my other newsfeeds from NPR or whatever seem to work fine, the feed from my site never has any content.

Is there some other magic switch that must be thrown to enable RSS in this version of DNN?

Everything looks like it should work, but nothing ever gets added to the content.

In another forum I saw people that had a similar problem to me -- they had the feed but the feed never had any content. The recommendation was that you should enable the "Search Indexer" in DNN. Trouble is, I don't really know how to do that. Does anyone know?

You'll want to enable the DotNetNuke.Services.Search.SearchEngineScheduler under Scheduled Tasks from the Host menu.

"The engine that drives search also drives RSS syndication. Updated content is not reflected in syndication until the next time the search index is run."

So, if that scheduled task is not running, you won't get any RSS updates.

Ok, I can see that the DotNetNuke.Services.Search.SearchEngineScheduler, DOTNETNUKE is running (set to run every 30 minutes)

When I click on history, though, it looks like it's throwing an exception and failing every time it runs.

Error info below:

EXCEPTION: The type initializer for "DotNetNuke.Services.Search.IndexingProvider" threw an exception.

TYPE: DotNetNuke.Services.Search.SearchEngineScheduler
EXCEPTION: The type initializer for "DotNetNuke.Services.Search.IndexingProvider" threw an exception.
RESCHEDULED FOR: 1/15/2008 12:42:54 PM
SOURCE: STARTED_FROM_BEGIN_REQUEST
ACTIVE THREADS: 1
FREE THREADS: 0
READER TIMEOUTS: 0
WRITER TIMEOUTS: 0
IN PROGRESS: 1
IN QUEUE: 5

Scheduler Exception:

AssemblyVersion: -1
Method:
FileName:
FileLineNumber: -1
FileColumnNumber: -1
PortalID: -1
PortalName:
UserID: -1
UserName:
ActiveTabID: -1
ActiveTabName:
AbsoluteURL:
AbsoluteURLReferrer:
ExceptionGUID:
DefaultDataProvider:
InnerException: The type initializer for "DotNetNuke.Services.Search.IndexingProvider" threw an exception.
Message: System.TypeInitializationException: The type initializer for "DotNetNuke.Services.Search.IndexingProvider" threw an exception. ---> System.Configuration.ConfigurationException: Exception creating section handler. (C:\pinnacle\web.config line 12) ---> System.IO.FileNotFoundException: File or assembly name PinnCorp, or one of its dependencies, was not found. File name: "PinnCorp" at System.Type.GetType(String typeName, Boolean throwOnError) at System.Web.Configuration.HttpConfigurationRecord.GetFactory(String configKey) === Pre-bind state information === LOG: DisplayName = PinnCorp (Partial) LOG: Appbase = file:///C:/pinnacle LOG: Initial PrivatePath = bin Calling assembly : (Unknown). === LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind). LOG: Post-policy reference: PinnCorp LOG: Attempting download of new URL file:///c:/windows/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files/pinnacle/fb3957cb/4f5209e7/PinnCorp.DLL. LOG: Attempting download of new URL file:///c:/windows/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files/pinnacle/fb3957cb/4f5209e7/PinnCorp/PinnCorp.DLL. LOG: Attempting download of new URL file:///C:/pinnacle/bin/PinnCorp.DLL. LOG: Attempting download of new URL file:///C:/pinnacle/bin/PinnCorp/PinnCorp.DLL. LOG: Attempting download of new URL file:///c:/windows/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files/pinnacle/fb3957cb/4f5209e7/PinnCorp.EXE. LOG: Attempting download of new URL file:///c:/windows/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files/pinnacle/fb3957cb/4f5209e7/PinnCorp/PinnCorp.EXE. LOG: Attempting download of new URL file:///C:/pinnacle/bin/PinnCorp.EXE. LOG: Attempting download of new URL file:///C:/pinnacle/bin/PinnCorp/PinnCorp.EXE. --- End of inner exception stack trace --- at System.Web.Configuration.HttpConfigurationRecord.GetFactory(String configKey) at System.Web.Configuration.HttpConfigurationRecord.Evaluate(String configKey, SectionRecord section) at System.Web.Configuration.HttpConfigurationRecord.GetConfig(String configKey, Boolean cacheResult) at System.Web.Configuration.HttpConfigurationSystemBase.System.Configuration.IConfigurationSystem.GetConfig(String configKey) at System.Configuration.ConfigurationSettings.GetConfig(String sectionName) at DotNetNuke.Framework.Providers.ProviderConfiguration.GetProviderConfiguration(String strProvider) at DotNetNuke.Framework.Reflection.CreateObject(String ObjectProviderType, String ObjectNamespace, String ObjectAssemblyName) at DotNetNuke.Services.Search.IndexingProvider.CreateProvider() at DotNetNuke.Services.Search.IndexingProvider..cctor() --- End of inner exception stack trace --- at DotNetNuke.Services.Search.IndexingProvider.Instance() at DotNetNuke.Services.Search.SearchEngineScheduler.DoWork()
StackTrace:
Source:

Do you recognize the references to pinnacle and PinnCorp.?

What is on line 12 of web.config?

I didn't really recognize the "PinnCorp" on line 12 of the web config, so I removed it and changed it back to DotNetNuke. Then the indexing service ran, at least once. The second time it ran for several hours and then croaked. I'm going to see what happens on the next time it's scheduled to run, and see if we can figure out why it's not happy. But at least it's running! Still no RSS content though.

Presumably PinnCorp was there for a reason? What was the entire line?

And, was there any error message when the indexer "croaked"?

I really think the "PinnCorp" assembly name was erronious. So now that its set to the normal "DotNetNuke" the DotNetNuke.Services.Search.SearchEngineScheduler seems to be running fine on a schedule.

But still no RSS content ever shows up.

There must be something else missing...

Ok, through some magic of restarting the site, restarting the indexing service, and re-saving the announcement module settings with "Allow Syndicate?" it's now publishing content.

That's great!

Does anyone know if there's a way to control the size of the content that gets published? It's only including the first line of the announcement -- could be a lot better if it would include the first two or three lines.

Is there a way to control this?

One of the settings for the Announcements Module is "Description Length (Search & RSS)". If you click the help button next to the field, you'll get this text:

"Specify the number of characters in the description used in search results and rss feeds
Tip: use 0 to use the maximum text length (2000 characters)"

So ... it looks like the default is 100 characters. You can change it to a larger number.

I'm glad that you've gotten this working, too!

Rats my announcements module doesn't have that setting. Perhaps it was added in a later version of DNN. I am still on 3.1.

If you are running DotNetNuke 3.1, I'm probably not going to be able to give you a lot of help.

If possible, I'd recommend that you consider upgrading to 4.8.0. It will be a bit of work, but you'll end up with a much more functional web site!