Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#1 2009-12-17 14:06:23
- PaulJ
- New Member
- Registered: 2009-12-17
- Posts: 3
Setting the title and link for the rss/atom feed
I’m setting up a blog at example.com/blog, which is a very different entity to the main site. It’s the only part of the site I want an rss feed for, so I can use the standard <txp:feed_link> but the title appears in my feedreader as “Site Name – Blog Name”, and the link (for the main feed, not individual posts) is to the main page which has no direct link to the blog. Is there a way round this?
Offline
Offline
#3 2009-12-21 17:16:13
- PaulJ
- New Member
- Registered: 2009-12-17
- Posts: 3
Re: Setting the title and link for the rss/atom feed
Thanks, Blue Dragon (can I call you Blue?!), that sort of worked. To be fair, following the instructions on the first post did do what I was asking. It works in a feed reader.
There is a problem though, the url www.example.com/rss-feed/ displays the xml and a message “This XML file does not appear to have any style information associated with it.” Whereas if I use the txp:feed_link tag, then the page ‘www.example.com/rss/?section=blog’ displays as a page that asks me to select what feedreader I want to use to subscribe. Obviously that’s more the sort of thing I’d like to provide users with a link to.
I’m not sure if it’s because I need to provide a style sheet for the rss-feed section, or some other reason, but clearly the txp tag is doing something different. Is there any way I can make the custom section do the same thing – use the same style sheet or whatever it is?
I’m using FireFox by the way, I read somewhere that some browser provide a style for the rss feed, but I don’t know it that’s relevant.
Offline
Re: Setting the title and link for the rss/atom feed
Mmm…can you please post your page & form codes here?
Offline
#5 2009-12-24 15:30:48
- PaulJ
- New Member
- Registered: 2009-12-17
- Posts: 3
Re: Setting the title and link for the rss/atom feed
Not to worry – putting it through Feedburner seems to have fixed the problem – or perhaps that should be “avoided” ;-)
Offline