Hey, I finally got around to building this out, and wanted to thank
you, this approach is mostly working, with just one problem:
-Sharing the description txt element is problematic, unless I use a
short blurb that needs zero formatting, an stf. But we're going to
need multiple paragraphs for at least half this stuff. If someone
wants a carriage return, then the xml will have html in it. Any ideas
for how to get around this?
Just so everyone understands what I'm trying to do: I have an html
page and a xml (podcast rss feed) page, sharing the same content
elements. What I need is for the text elements that are shared, for
the minimal amount of markup that they would contain, the tags would
need to be converted to <p> , </p> , etc.
Thanks,
-Dino
On Nov 5, 1:57 am, heiko <
heikosebastian.fr...@googlemail.com> wrote:
> Hi,
> you can probably get around that without using variants (and I would
> recommend to do so if this is the only other variant in the project).
> I would use a list instead of a container and let the overview-page
> pull the contents ("transfer from connected pages" or something along
> those lines) . This way, you can use a new template (the RSS feed)
> with another list, reference the original list or connect it to a
> keyword like "Environment-Podcast" and display the pulled contents in
> a RSS-manner in that template.
> If you want to continue using the container, you would probably have
> to go with project variants (not sure though).
> cheers
> Heiko
>
> On Nov 5, 5:53 am, dino <
ldj5...@gmail.com> wrote:
>
> > Hi,
> > Has anyone successfully used reddot to generate apodcastxml version