Geeklog Forums

Hello

I'm just wondering (yes, I searched the GL2 site and this one and googled for it) if it may be in the works, or possibly maybe there's a plugin available that I can't find, to add the ability to categorize topics/feeds?

I've seen this ability in other systems feature lists, but I like geeklog

It just so happens that the project I'm using GL for right now would greatly benefit from categorized feeds and I can see uses for it in existing projects as well.

Thanks!!

It would help if you'd explain what a "categorized feed" is for you ... Geeklog 1.3.11 already supports separate feeds for each topic.

bye, Dirk

Sorry for not being clear.

Much like you can categorize links, it would be good to be able to give numerous encompassing categories for topics i.e. a "Web Development" category would contain relevant topics/feed; or in my case, I'd like to create regional categories for my topics.

I envision the feeds being broken into seperate physical directories (named by topicID) within the /backend/ folder, but I'm only a fledgling self-taught programmer, so I dunno about implementation there; simply, (and not to fork this thread) from what I've read about support for "private" or protected feeds, you could use this method with http_auth..... ??

I'm just sort of pipe dreaming here, honestly This should probably be in the GL2 'feature requests' forum. And maybe I should not waste Dirk's et al time

Thanks for the reply.

Allan

[quote="AllanH"]...physical directories (named by topicID) within...[/quote]

I did not mean topicID, I meant that the feed directories could be named by categoryID (as created by having topic categories).

I'm probably totally out to lunch here, eh? Should I try to explain myself further? is there any interest in this at all?

Not even close to tryin' to be impatient or nothin' like that

Geeklog currently requires that all feeds are in the same directory.

And, frankly, I don't see the point either. What's the difference between having feeds backend/topic1.rss, backend/topic2.rss, etc. and topic1/feed.rss, topic2/feed.rss?

bye, Dirk

I'm not thinking /backend/topic1/feed.rss, I'm thinking

/backend/category1/topic5.rss
/backend/category1/topic10.rss
/backend/category1/topic25.rss

/backend/category2/topic1.rss
/backend/category2/topic3.rss
/backend/category2/topic18.rss

/backend/category3/topic2.rss
/backend/category3/topic12.rss
/backend/category3/topic9.rss

Catch my drift?

PS 'moods' are a fun option

Nope, sorry, still don't see the point ...

bye, Dirk

Really? Am I completely alone on this? I just see it making perfect sense to be able to categorize your feeds - if you've more than 10 topics that cover multiple, diverse area's of discussion and want to provide more than one type of feed for each topic, that /backend/ directory is getting huge and dis-orderly.

I've a feeling I'm just using the wrong words to describe what I'm talking about. Perhaps Sub-topics would be a better description?

I'll leave this alone from here on in, I guess. I'll probably end up coding a plugin that does what I want. In the meantime, I'm going to find a system that does what I'm looking for and provide a link in here to it so maybe someone will see wtf I'm trying to say.

Thanks for your time Dirk

Allan

BTW, until I find time to do that plugin, I'm simply using a naming convention to accomplish what I need:

/backend/category1-topic5.rss
/backend/category1-topic8.rss
/backend/category2-topic1.rss
/backend/category3-topic2.rss

If you want to categorize your feeds you will have to get into the code, or roll your own, or modify some of those progs out there that already do this for you, but not for geeklog. My advice? ...go the plugin way.

when you begin writing your plugin, you may want to consider that categorizing your feeds should only entail an extra field in a table somewhere next to the feed name/id. There really isn't any need to use naming conventions of any kind or to separate categories into directories.

The only reason to separate into directories would be if you were not going to make use of a database, but rather just scan dirs recursively for content. This would not be the way to go. Your code would be much simpler and more efficient using the db.

just my

No, I agree. We have like 300 articles in 20 categories and off course we doesn't want 1 topic for each category. It's better with sub topics.

articles/category1/
articles/category2/
articles/category3/
etc etc

Mikael