Try using this template :) http://www.google.com.au/search?q=creating+rss+feed+in+reddot+cms
On 15 Okt., 10:06, kimdezen <[email protected]> wrote: > ..and if you are unable to reference lists, ive always found this > technique does the same sort of thing (outputs the location of the > 'main link' for the page - effectively the same publication package > where the page resides in the project) > > <!IoRangeList> > > <!IoRangeNoRedDotMode><!IoRangeRedDotMode><!-- <%lst_pages%> > --><!/IoRangeRedDotMode><!/IoRangeNoRedDotMode> > > .... > > <link><%!! Context:Indexes.GetIndexByPageId(Guid:<%inf_pageguid > %>).Page.GetUrl() !!%></link> > > ..... > > <!/IoRangeList> > > although it wont stop the CMS from publishing multiple files (unless > everything is published to the root directory) - all links across the > site will point back to the same page. > > Kim > > On Oct 15, 10:38 am, Jian Huang <[email protected]> wrote: > > > Yes, you can use the workflow publish reaction to publish the article > > page and related page, which mean any other page that the article page > > is connected to. However, in that case, I would not be using > > lst_pages to reference list_nextlevel because a reference is not a > > page connection. > > > How do you achieve an automatic push to lst_pages in the RSS feed > > page, you ask? Use category and keywords. > > > However, watch out in the scenario that a page is connected in > > multiple locations because if each location has a different pub > > package, then the page will get published multiple times to multiple > > locations according to pub package. > > > How to avoid this you ask? > > > We use a technique call "shadow list". Have lst_pages and > > lst_pages_ref in you RSS feed content class. Reference lst_pages_ref > > to lst_pages. In the content class code, wrap lst_pages in XML > > comments and SmartEditModeOnly blockmark, and use list_pages_ref to > > illiterate through your articles instead. > > > What does this technique accomplish? > > A page is connected to multiple places, a publish related page command > > will be triggered if needed, but the publish will follow > > lst_pages_ref, which is used in the template, and lst_pages_ref is a > > reference, so the pub package used for those pages defaults to pub > > package on mainlink, where you really want your pages to go to. > > > On Oct 14, 10:10 am, Kristaps Karlsons <[email protected]> wrote: > > > > Hi, Jian, > > > > Can you tell us what fields, some are optional will be used in your > > > > > RSS feed? For example, if you are planning on using a > > > > inf_last_modified from the page as <pubDate>, then you might not want > > > > to use rendertag or navigation manager to return value of > > > > inf_last_modified. > > > > Title, description, link and publication date would be everything I'd > > > need. > > > > For publication date I guess I'll be using info element - Page: Release > > > Date. > > > > Personally, I would avoid creating a RSS project variant, just create > > > > > a content class that outputs xml, with lst_pages referenced to > > > > list_nextlevel. > > > > So - just iterate trought a referenced list and add XML markup manually. > > > Ok. > > > > Last thing - is it possible to automatically publish this (rss) page when > > > new page is added and published? If yes - can the rss page be in other > > > branch of site? > > > > Thank you -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
