Defining a category for articles

Hi,

I would like to know if it’s possible with the mental branch to have a
category / tag attached to an article.
I made a search and it seems that a ticket corresponding to this feature
has been closed. I also read on a previous subject that mephisto (at the
moment) is better suited for a weblog with such category feature.
But I tried to install mephisto without success (I use sqlite3 as the
DB).
Radiant works and I like it and I prefer not to change.

Thanks for any help.

On 2/19/07, Ruby A. [email protected] wrote:

But I tried to install mephisto without success (I use sqlite3 as the DB).
Radiant works and I like it and I prefer not to change.

You’d be better off with Mephisto in this case. Content management in
Radiant is plain hierarchical (tree - based). However, it has a neat
extension system now and, if you pull up your sleeves and have some
experience, you could make a plugin for yourself that adds category
select
to the admin interface and a couple of handy Radius tags.

You can also resort to some sort of a clever hack. With categories
you’re
basically trying to make some content appear in multiple places, right?
Well, if you could hack the Page model to have multiple parents instead
of
just one, you could easily achieve this goal.

However, it has a neat extension system now and, if you pull up your sleeves >and have some experience, you could make a plugin for yourself that adds >category select to the admin interface and a couple of handy Radius tags.

I’m just discovering Radiant and I’m a bit lost with behaviour, plugin
and extension.
I understand that behaviour will be deprecated with the 0.6 release.
But what is the difference and relationship between an extension and a
plugin ?

I found the following How Tos :

  • “How To: Create Global Tags in a Plugin”- “How to Write an Extension
    (work in progress)”

But I still don’t know how to link all the things together.

CM.

On 2/19/07, Ruby A. [email protected] wrote:

I’m just discovering Radiant and I’m a bit lost with behaviour, plugin and
extension.
I understand that behaviour will be deprecated with the 0.6 release.
But what is the difference and relationship between an extension and a
plugin ?

Errm I interchanged the two terms in my sentence, which wasn’t right. I
meant extension. Plugins in Radiant are like general Rails plugin which
can
add functionality, monkeypatch existing stuff and so on. For instance,
adding Radius tags is done with plugins, while admin interface hackery
is in
extensions.

“John W. Long” [email protected] wrote:

Actually no. Extensions are the new model for extending Radiant.
The use of Rails plugins for this purpose is deprecated.

Behaviors have been merged into the Page class in 0.6.
You can still do the same things, but you inherit from the Page
class instead of
inheriting from Behavior::Base.

When the 0.6 is expected to be released ?
I suppose that there will be some release notes indicating what are
the deprecated features and what are the new way for doing things.

I’m a bit lost as the How-Tos seems to mix deprecated features (e.g.
behaviour) and new features (e.g. extension).
Is it possible to tag How-Tos with the version of Radiant it is
applicable (e.g “deprecated in 0.6”, “since 0.6”, …).
For example, in the “Define Global Tags” How To, there is a reference
to the app/models/page_context.rb app/models/page_context.rb but that
file from the mental branch doesn’t look like in the How To.

Thanks in advance.

CM.

Mislav Marohnić wrote:

Errm I interchanged the two terms in my sentence, which wasn’t right. I
meant extension. Plugins in Radiant are like general Rails plugin which can
add functionality, monkeypatch existing stuff and so on. For instance,
adding Radius tags is done with plugins, while admin interface hackery
is in extensions.

Actually no. Extensions are the new model for extending Radiant. The use
of Rails plugins for this purpose is deprecated.

Behaviors have been merged into the Page class in 0.6. You can still do
the same things, but you inherit from the Page class instead of
inheriting from Behavior::Base.


John L.
http://wiseheartdesign.com

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs