Thread

Hello, I’m not sure if this makes sense, but basically I’m wondering if there’s a workaround known for getting the rss/atom feeds to work properly when running the forums tag in a regular EE template that is access protected.

I’m sure that sounds crazy, but the reason is this is for a company intranet and we don’t want to just have private threads, but anyone accessing any intranet area at all we want to just redirect to a login page. I’m running the forum module through the template parser for other reasons which is working perfectly except for the broken feeds.

The forum feeds error out as they also try to redirect to the login page then. So I’ve tried setting the “trigger” word and using that as the feed path only, but then the “read more” links use the trigger word as the path instead of the forums URL.

Any help or ideas would be appreciated, and I suppose if the answer is “that’s unsupported!” I’ll figure something else out but I’d rather get the official word before I bang my head on my desk any more tonight…

Heh- ok, it is confusing.  So- you’re using access restrictions to redirect non-members to a login page.  But what I don’t get- if they’re logged in and try to access the rss, they shouldn’t be redirected.  Right?  Like- you can pull up the rss page no problem logged in.  It’s just the readers bork.

So really, to get the feed working, you need to have http authentication- which you don’t want otherwise.  That sound reasonable so far?  So maybe… not sure this would work.  But if you stick another forum tag on a new template- 1. can you access the rss going there; 2. can you http access restrict it so readers that store passwords can get to it?

And did any of that make sense? 😉

Thanks Robin! I think you made sense of my general situation. The problem with using a separate template for the feeds is that the “read more” links within the feeds then take on the url of the feed template instead of the main forum template, which was the same problem as using the trigger word for the feeds - not using/respecting the forum url setting for all the urls within the feed itself.

BUT, your suggestions got me to re-think my approach and I was able to make this work by instead of using the template access restriction, just using a conditional in the template with the forum tag to check if logged the user is logged in, and if not embed a login template instead. That works, and the feeds work as well, the only problem now is that enabling http authentication for the feeds in the forum module settings doesn’t seem to be honored - no http login prompt at all. That might just be something I’m missing now after messing with this way too much. I’m going to step back and see if I can simplify further.

imagehat - you have an alternate solution, I see.  That’s great! But you said you’re trying to use template access restrictions and and HTTP authentication? So you’re trying to double authenticate?  I’m not sure if that would be expected to work….