Subject: [ANN] Radiant On Crack - msg#00227

List: cms.radiant.general

Date: Prev Next Index Thread: Prev Next Index

Radiant on Crack is my experimental branch of the Radiant CMS project.

http://soxbox.no-ip.org/radiant/

I've been making experimenting with a few things that need some fairly
fundamental changes to the underlying codebase of radiant, and my
immediate needs are somewhat different to those of the core developers.
The primary goal of what I'm doing here is to make Radiant powerful
enough to run The Groggy Squirrel http://www.thegroggysquirrel.com ,
which is currently powered by a hand-rolled and very unfriendly cms-like
system.

I'm hoping to have implemented within the couple of weeks: Images,
Attachments, Comments and some other goodies.

Before you ask, this is not a political fork of the project, it's a
practical one. I'm extending the capabilities of Radiant in ways that
are going to break things, but in ways that I need it to change. I need
to track my changes anyway, so I might as well do it publicly rather
than turn up in 2 months time with a pile of patches.

I look forward to most of my changes working their way into core in some
way, shape or form - probably with a better implementation than I can
come up with. I'm happy for others to cherry-pick changes from R.O.C.
and patch them into core, or to ask for my help to do so.

********************************************************************
* I Do Not Recommend Running Radiant On Crack on your live site *
********************************************************************

I've given it a stupid name for a good reason. I don't want anybody
basing their livelihood on it. I will have no qualms about ripping out
implementations and completely reworking things in a possibly backward
incompatibly manner. Unless you're willing and able to dive into both
ruby and sql to hack it about to fix it and make it work, don't use it.
Consider yourself warned.

Was this page helpful?

Thread at a glance:

Previous Message by Date: click to view message preview

Re: Installation Problem

> I installed from the subversion repository. All I have in my > vendor dir is > bluecloth, plugins and a rails folder. Is it better to > install Radiant > through Gem? If so, you don't happen to have a link to > instructions for > doing so? Your problem is probably that you're sitting behind a firewall and you can't get to the radius repository (which is served over the svn:// protocol rather than http:// like the other externals). If you can't get around your firewall, then doing a "gem install radius" will also get you through. Daniel.

Next Message by Date: click to view message preview

Determining the Page Missing Behavior

This is a multi-part message in MIME format. Currently Page Missing is a fairly hardcoded thing. If I wanted to create a new page missing behavior, I would have to do so by modifying the behavior of the parent to look for my new type of page missing behavior - This is because the page missing behavior is found based on behavior_id. I'd like to suggest that this actually be determined in another manner, possibly falling back to the behavior_id. I like the idea of looking for a page with "404" as it's slug, or some other string that seems appropriate. What say you? As an example of what I'd like to do, I want to introduce a 'best guess' page missing behavior that tries to find a matching page and if so redirects to that page, so that if there are the pages at the slugs: /monkeys-are-good /monkeys-are-bad then a request to /monkeys-are-g would get redirected to the first page, as would a request for /monkeys-are-good-arent-they or /monkeys-are-good.fdasa - a request to /monkeys-are would end up actually rendering the page missing page, as it couldn't tell which is which (though the behavior might want to render the list of possibly matching urls). This is really useful when people email your links around and they end up getting slightly truncated due to line-wrapping or get extra punctuation from a bad cut/paste or a mail-agent that can't tell tell that http://www.google.com/search. is not meant to have that trailing period. Other parts of your site might have aliases - such as obseleted products where there's a table mapping old products to new names and you want to take advantage of that table to send people to the right location. Dan.

Previous Message by Thread: click to view message preview

Radiant Mailer Behavior

Hi,i am pretty much excited by using Radiant. I am a bit confused by the Mailer behavior. I am trying to implement it but it gives me errors. Can someone talk about this from his experience? Also config part needs to be defined the same way as a page part, right? Is there a need of defining smtp? Thanks in advance.Regards,Rizwan Reza

Next Message by Thread: click to view message preview

Re: [ANN] Radiant On Crack

Hi Daniel, that sounds great, will be watching. > Radiant on Crack is my experimental branch of the Radiant CMS project. > > http://soxbox.no-ip.org/radiant/ > > I'm hoping to have implemented within the couple of weeks: Images, > Attachments, Comments and some other goodies. Yeah, these seem very important. At least images and attachments. I can't use Radiant without those + a WYSIWYG editor like FCKEditor. I want to use it for my customers so Textile/Markdown is a nono. Once it has those three things I would / could use it. Maybe one of the cores can comment on if this is acceptable to the plan? I don't know about comments though. Once Radiant has comments it effectively becomes a blogging system. Maybe as a plugin? > I look forward to most of my changes working their way into core in some > way, shape or form - probably with a better implementation than I can > come up with. I'm happy for others to cherry-pick changes from R.O.C. > and patch them into core, or to ask for my help to do so. That would be great. -Sascha Ebach

Loading Comments...