Just to throw my $.02 in, I agree with most of what Ruben says, especially with regards to MailerBehavior. I've spent atleast 10 hours the last week and a half between testing, talking to my host, searching for the little bit of documentation that is out there, etc trying to figure out how to get it working and I just can't get anything going there, nor can I figure what's actually wrong with it.
I also agree that user roles and the publishing system needs to be improved. I'm not talking about a total re-design but it would be nice to be able to change a page, view some sort of "draft" before it gets published, and then publish it if it was ok. Also, versioned pages would be VERY nice, and I wouldn't think it would be that difficult to implement with acts_as_versioned, but I've never tried. And then there is the documentation, which I plan to help with as soon as I get my site launched. I feel like Radiant is right on the edge of being ready, and hopefully the next version (mental?!?) will be just enough to push it to fully ready. -BJ Clark On 1/14/07, John W. Long <[EMAIL PROTECTED]> wrote: > Ruben D. Orduz wrote: > > * Mailer Behaviour is shaky at best. > > Sean Cribbs has been working on a replacement extension for the mailer > behavior. I'm hoping that he will be gracious enough to allow us to > eventually pull it into the official extensions repository. It seems a > lot of people have had trouble with the mailer behavior and I agree that > we need a better supported solution. > > > * Print page to PDF/PS/CSV is not even completely supported by Rails. > > This would probably be a lot of work. I'd suggest you try to come up > with something that would function well as an extension. > > > * User roles. > > I'm open to patches that make it easy for people to swap in their own > user management/permissions system. Everyone and their uncle seems to > have an opinion about how this should be done. > > > Sorry for soapboxing, but in closing I must echo the thoughts of a > > list contributor who said something to the effect that if a project > > stagnates for too long, it eventually fades away. > > I have no intention of seeing Radiant stagnate and fade away, but I do > have a living to make. :) Part of the reason things have been slow is > that we are still bringing core developers up to speed on the current > code base and the direction of the project. I'm adding developers as I > can, but it takes time. > > Thanks for helping out with the documentation. Your work there is > appreciated. > > -- > John Long > http://wiseheartdesign.com > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
