Thread

Hi,

I’m very new to EE and this is my first post so please bear with me. I’ve read the Quick Start tutorials and watched the videos a couple times and I understand the basic idea of how EE works but, not surprisingly, I’m still finding my legs so perhaps someone could suggest a way to approach this project.

I need to set-up 10 separate directories for 10 users to create/edit/publish their RSS feeds using EE.

For example:

http://www.mysite.com/rss/user_1/index.php
http://www.mysite.com/rss/user_2/index.php

The only thing these pages need to show is a dynamic list of available feeds/links as they’re created and/or removed, that’s all.

I understand the use of templates and tags (well, at least the basics) but I can’t grasp how I can create this functionality and everything I try is a failure. Eventually I will need to build a simple template for the feed pages (I actually do understand html and css) but for now one of the default templates is fine for experimenting. I’m sure this is EE 101 for most of you but any insight will be much appreciated. Remember, small words please.

Regards,

Todd

Hey Todd - Welcome to the forums.
Just so you know, you don’t need to start a second thread in a different forum, usually the moderators will move it if they feel it would be better placed somewhere else.
—————

Question to clarify…
You don’t want to actually bring in the posts from the feeds, just list the available feeds?
If so, couldn’t you just set up a weblog where the authors can enter feeds/links as entries (one per feed) and they can close ones when no longer valid? You would then just use an ordinary weblog:entries tag to display them. You’d need to display by author to separate them out by author.

If you do want to display the entries from a feed, then the Magpie suggestion (from other thread) is a good one.

Hi,

Yes, just a list of available feeds created by any of several “editors”. The site admin (not me) will then copy (the feed link) into a local broadcast system. Here’s a more detailed explanation from the site admin:

“I have a broadcast system which plays on TV’s in the Hotels in my area.
That system has a text feed that scrolls along the bottom of the screen…just like CNN if you will.
I can datamine 1 or more RSS feeds (like the CBC link) straight into the system.

I want to have several sources of RSS feeds into the system: News, Snow Reports, Local Events, Hotel information.

So for example, a person at the hotel (one of several “editors”) logs in to their own password-protected directory page and using the EE cp they create an rss feed, say, “Keynote Speech for Oilmans conference - Main Ballroom - 8:30 am——Steakhouse Restaurant - 50% off Thursday Evening——- Pool Hours - 8 am to 10 pm, No Children 6pm - 10pm”

Bottom line is this simple RSS editor page can be updated by a low skill computer person at the hotel.
Then their RSS feed is feed into our Broadcast system.”

Todd

Unless I’m not totally misunderstanding, I guess I would do it the way I mentioned above…a weblog (maybe one for each hotel for security) to accept the feed listings (individual events) through either Publish or a stand alone entry form. I would then create a protected template (access controls) to display these entries from which the admin could then copy the feeds and paste them into their system.

I guess what I find confusing is the use of the word feed and RSS. I’m not sure that is involved. If the admin just needs to get anything new entered, then maybe an RSS feed might be helpful but I don’t sense that from your description so far.

When it was explained to me this page, http://www.cbc.ca/rss/ was cited as an example of “RSS feeds” which he could copy into the broadcast system.

Todd

Yes, you could use an RSS feed but you’d still need to create the weblog, etc. as I mentioned to feed out rss. The other thing with an rss feed is it’s going to spit out just what’s new, add to a list in an rss reader. That could be ok or not. It won’t reflect anything that has expired or been closed by your editors, all entries will be fed out once to the reader. The admin would then have to determine what to copy/paste in I would guess.

Edit-Add: EE is fully capable of creating rss feeds from weblog entries.

He seems to be fine for now with the fact that expired entries will not be shown, as long as all the current entries for a given feed appear in the broadcast system when a link is copied over.

Originally he wanted to use a pw-protected directory (probably protected straight from the server CP) for each editor to restrict them to their own feed page; no access to anything else. But you mentioned that it’s possible to restrict their control using EE, did I understand that correctly? So they could only access their own page from the EE cp and nothing else?

Now I have to figure out how to build a test page to see how it all actually works which is where I’m at right now.

Thanks,

Todd

quote]it’s possible to restrict their control using EE, did I understand that correctly? So they could only access their own page from the EE cp and nothing else?[/quote]

Yes, you can control what an editor can see or get at through Member Groups, make each editor their own group for maximum control and restrict away. You can also restrict the viewing of certain templates to a Member Group through the template Access controls. Or you can restrict in the templates by using conditionals based on user name/id. Many different ways to get at the solution.