Re: [Radiant] Volunteers Needed! Radiant Wiki Migration
On Thu, Apr 9, 2009 at 11:21 PM, N. Turnage wrote: > It looks like some of the projects they mention as success stories have > themselves moved their wikis to git (e.g. Typo). I know about typo and talked to Frédéric about it but they were using an old version of Redmine. -- Ollivier Robert - ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Volunteers Needed! Radiant Wiki Migration
On Thu, Apr 9, 2009 at 11:26 PM, John W. Long wrote: > Its just another thing to maintain. One of the chief advantages of migrating > stuff over to github is that upgrades and maintenance are free. I'd say that Redmine does more than github but I can also understand your point. -- Ollivier Robert - ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Something I noticed about Textile in 0.7.1
Nate, I didn't really follow you. Can you have another go at it? Radiant 0.6.9 locked you into using RedCloth 3.0.4 for Textile, which was released in September of 2005. 0.7.1 lets you use RedCloth from gems, so you can get the latest RedCloth—4.1.9 which is much better. It handles HTML or already-rendered Textile (i.e. HTML) much better. I find occasionally I still have to wrap some radius tags in blocks, but it's a big improvement over what we had before. Maybe something within Radiant changed between 0.6.9 and 0.7.1, but I doubt it. Are you saying it's an overall improvement? Do you have suggestions for additional improvements. That reminds me, I made a pure-Ruby version of RedCloth a couple months ago and I should submit that to Radiant to be bundled in in place of 3.0.4. Have a great weekend! I'm probably offline 'til Tuesday. Jason On Apr 10, 2009, at 12:36 AM, N. Turnage wrote: During the upgrade to 0.7.1 from 0.6.9 (seriously, could we add another couple more decimal places?) is that Textile is handled a bit differently. It used to be that You could pile on the textile'd page parts and snippets on top of one another inside of a page that had Textile set and it would (usually) render the html properly. But in 0.7.1 the Textile processing is much more specific in how the html gets rendered. I found that specifying the Textile filter in the parent snippet/ page/page part will sort it out for the parts that are placed within it. Nice. Just something I noticed. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Something I noticed about Textile in 0.7.1
Jason, Please do submit that - it would be great to be compliant with the Textile spec OOB. As an aside, last weekend I was working with Chef (which uses Merb) and somehow when I updated the gems, it would install the wrong versions of certain Merb gems, causing version mismatches and gem activation errors. To keep Radiant's dependencies simple and optionally use external gems is the way to continue, I'm convinced. Sean Jason Garber wrote: Nate, I didn't really follow you. Can you have another go at it? Radiant 0.6.9 locked you into using RedCloth 3.0.4 for Textile, which was released in September of 2005. 0.7.1 lets you use RedCloth from gems, so you can get the latest RedCloth—4.1.9 which is much better. It handles HTML or already-rendered Textile (i.e. HTML) much better. I find occasionally I still have to wrap some radius tags in blocks, but it's a big improvement over what we had before. Maybe something within Radiant changed between 0.6.9 and 0.7.1, but I doubt it. Are you saying it's an overall improvement? Do you have suggestions for additional improvements. That reminds me, I made a pure-Ruby version of RedCloth a couple months ago and I should submit that to Radiant to be bundled in in place of 3.0.4. Have a great weekend! I'm probably offline 'til Tuesday. Jason On Apr 10, 2009, at 12:36 AM, N. Turnage wrote: During the upgrade to 0.7.1 from 0.6.9 (seriously, could we add another couple more decimal places?) is that Textile is handled a bit differently. It used to be that You could pile on the textile'd page parts and snippets on top of one another inside of a page that had Textile set and it would (usually) render the html properly. But in 0.7.1 the Textile processing is much more specific in how the html gets rendered. I found that specifying the Textile filter in the parent snippet/page/page part will sort it out for the parts that are placed within it. Nice. Just something I noticed. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Something I noticed about Textile in 0.7.1
Jason Garber wrote: Nate, I didn't really follow you. Can you have another go at it? Sure. It was late when I posted. When I upgraded to 0.7.1 I noticed that I was getting extra line breaks () between lines, even though the exact same stylesheet was used and nothing else in the conten had changed. Well as it turned out, the pages with the problems had the Textile filter on and the snippets and page parts added on the pages each had textile turned on. In 0.6.9 this didn't create problems, everything went through it's own filtering process and the html rendered correctly. In 0.7.1, every time a page part or snippet was processed on the page, the Textile filter was invoked and I was getting html with extra line breaks as Textile filter was called multiple times on the same page content. I may be the only person experiencing this, but for me, this excellent. This is exactly how I originally imagined the Textile filter to work. With the filter set on a container page, all the page parts and snippets on it are filtered at the same time. Does that make more sense? Radiant 0.6.9 locked you into using RedCloth 3.0.4 for Textile, which was released in September of 2005. 0.7.1 lets you use RedCloth from gems, so you can get the latest RedCloth—4.1.9 which is much better. It handles HTML or already-rendered Textile (i.e. HTML) much better. I find occasionally I still have to wrap some radius tags in blocks, but it's a big improvement over what we had before. Do you have to do anything special to make this happen? I installed the RedCloth 4 extension to avoid using v3.0.4 that it looks like Radiant uses by default. Are you saying that Radiant should automatically use my gem by default? Maybe something within Radiant changed between 0.6.9 and 0.7.1, but I doubt it. Are you saying it's an overall improvement? Do you have suggestions for additional improvements. I would say that if Radiant uses the gem automatically, then it's perfect. If not, then I am getting the behavior that I wanted by using the RedCloth4 extension. That reminds me, I made a pure-Ruby version of RedCloth a couple months ago and I should submit that to Radiant to be bundled in in place of 3.0.4. That would be great. Have a great weekend! I'm probably offline 'til Tuesday. You too, but I am always online. ;^) ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Something I noticed about Textile in 0.7.1
Do you have to do anything special to make this happen? I installed the RedCloth 4 extension to avoid using v3.0.4 that it looks like Radiant uses by default. Are you saying that Radiant should automatically use my gem by default? You no longer need to install that extension. Radiant will now search for RedCloth using RubyGems before it requires the packaged version. The same goes for RDiscount (vs. BlueCloth). Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Something I noticed about Textile in 0.7.1
Sean Cribbs wrote: Do you have to do anything special to make this happen? I installed the RedCloth 4 extension to avoid using v3.0.4 that it looks like Radiant uses by default. Are you saying that Radiant should automatically use my gem by default? You no longer need to install that extension. Radiant will now search for RedCloth using RubyGems before it requires the packaged version. The same goes for RDiscount (vs. BlueCloth). That rocks! Thanks. ~Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Great job on the wiki!
John Muhl and Stephen Southard-- Just wanted to publicly thank both of you for your wonderful work on the wiki. It's needed a little gardening for a long while now. Thanks for pulling out the weeds. I feel much better about how everything is organized now and the move to GitHub was the right call. Both of you just earned a place in my hall of heros--along with Sean Cribbs, Andrew Vonderluft, Mohit Sindhwani, and anyone else who has helped with the wiki. Keep it up team! -- John Long http://wiseheartdesign.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Mailer extension question
So I went and solved my own problem by modifying things (http://github.com/adsmart/radiant-directory-mailer-extension) and it turns out that it was a very simply addition. Simply change recipients to directory in you mailer part and add recipients_field. The value of the recipients field is now a list of the indexes of items in the directory to use as the recipients. That is, given a mailer of: subject: "Sent from your mailer form" recipient_field: destination directory: - z...@example.com - o...@example.com and the form from my original post, the message will be sent only to the email address(es) that are selected in the form. I do need help with one bit. I'm not well versed on (T|B)DD so I haven't modified the specs to account for the new behaviour. I'm not quite sure how to do it. Manually keeping the form and the mailer config in sync is more prone to error than I'd like so I'm thinking of adding a tag that would let you do: To get the names, I'm not sure if I prefer directory: - z...@example.com - o...@example.com names: - "First Address" - "Second Address" or directory: - name: "First Address" email: z...@example.com - name: "Second Address" email: o...@example.com either approach has its advantages and disadvantages. On Thu, 2009-04-09 at 23:26 -0700, Adam van den Hoven wrote: > Hey all, > > I need some help. I'm trying to make a mailer page where I want to allow > users to select the recipient. However, I really don't want to expose > the recipient's address. I was planning on using the following form: > > > > Destination > > First > Second > > > ... Other stuff ... > > > The code suggests that the mailer part is rendered before it is parsed > as YAML. So I set my mailer to: > > subject: "Sent from your mailer form" > from_field: email > recipients: > - > z...@example.com > - > o...@example.com > > But when I run it I get the following error: > > syntax error on line 4, col 53: `' > > I'd rather not have to customize the extension if I don't have to. > -- Adam van den Hoven Hybrid Web Developer Little Fyr Media p: 604.618.0845 e: adam.vandenho...@gmail.com w: http://www.littlefyr.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
