[Radiant] Shards in Radiant 0.6.7
Hi, Thanks for all the great work going on in the Radiant community. I'm upgrading one of my extensions to be compatible with 0.6.7, and I am migrating it to use the shards feature at the same time. While the release of 0.6.7 indicates that shards has been folded into the core, I can't get it work right. I can see that the render_region calls are present in the views, but when I try to plugin my own partials in the extension activation, I get an error: def activate ... page.index.add :node, 'file_based_layout_column' end /Users/casper/Projects/Work/radiant-0.6.7/vendor/extensions/ file_based_layout/file_based_layout_extension.rb:16:in `activate': undefined local variable or method `page' for #FileBasedLayoutExtension:0x24c334c (NameError) from /Users/casper/Projects/Work/radiant-0.6.7/lib/radiant/ extension.rb:34:in `activate' Does this mean I still have to add the shards extension and put it first in my extension load order? Or have I misunderstood how to use tie in my own stuff in Radaint using shards? Does anyone have a link to an up-to-date tutorial on shards? Cheers, Casper Fabricius ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Shards in Radiant 0.6.7
Casper, page is a method/property on the admin object. Change that to admin.page.index.add :node, 'file_based_layout_column' Sean Casper Fabricius wrote: Hi, Thanks for all the great work going on in the Radiant community. I'm upgrading one of my extensions to be compatible with 0.6.7, and I am migrating it to use the shards feature at the same time. While the release of 0.6.7 indicates that shards has been folded into the core, I can't get it work right. I can see that the render_region calls are present in the views, but when I try to plugin my own partials in the extension activation, I get an error: def activate ... page.index.add :node, 'file_based_layout_column' end /Users/casper/Projects/Work/radiant-0.6.7/vendor/extensions/file_based_layout/file_based_layout_extension.rb:16:in `activate': undefined local variable or method `page' for #FileBasedLayoutExtension:0x24c334c (NameError) from /Users/casper/Projects/Work/radiant-0.6.7/lib/radiant/extension.rb:34:in `activate' Does this mean I still have to add the shards extension and put it first in my extension load order? Or have I misunderstood how to use tie in my own stuff in Radaint using shards? Does anyone have a link to an up-to-date tutorial on shards? Cheers, Casper Fabricius ___ 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] Update on DreamHost
thanks! The update worked now :) But after having done rake radiant:update, and putting back ENV['GEM_PATH'] into config/environment.rb I try to do the rake db:migrate. But after a while I get: rake aborted! development database is not configured Which is true, cause I removed it, cause I didnt think I needed it. And it worked with 0.6.6. Does 0.6.7 require one? Even if i don't really want one? =/ -- From: Sean Cribbs [EMAIL PROTECTED] Sent: Monday, May 19, 2008 4:09 PM To: [EMAIL PROTECTED]; radiant@radiantcms.org Subject: Re: [Radiant] Update on DreamHost In case you didn't know, Radiant's gem doesn't depend on any gems except rake. All other dependencies are packaged, including Rails. Sean Bill Barnard wrote: On Sun, 2008-05-18 at 17:06 +0200, Torleif Berger wrote: How can I upgrade radiant to the new version 0.6.7 on DreamHost? I do gem update radiant, and it works for a while, then ends with Killed ( ? ). Dreamhost runs a procwatch daemon that kills any process that takes excessive memory. Most gem processes (update, install, etc.) use a lot of memory when checking dependencies. The way I've worked around this in the past is to install the gem manually and resolve dependencies myself. Download the gem file, then from the directory containing the gem run: gem install --local gem_name I added this note to http://wiki.dreamhost.com/index.php/RubyGems Best of luck, Bill ___ 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] Update on DreamHost
If you only want to use the production database, prefix your rake command with production: rake production db:migrate Sean Torleif Berger wrote: thanks! The update worked now :) But after having done rake radiant:update, and putting back ENV['GEM_PATH'] into config/environment.rb I try to do the rake db:migrate. But after a while I get: rake aborted! development database is not configured Which is true, cause I removed it, cause I didnt think I needed it. And it worked with 0.6.6. Does 0.6.7 require one? Even if i don't really want one? =/ -- From: Sean Cribbs [EMAIL PROTECTED] Sent: Monday, May 19, 2008 4:09 PM To: [EMAIL PROTECTED]; radiant@radiantcms.org Subject: Re: [Radiant] Update on DreamHost In case you didn't know, Radiant's gem doesn't depend on any gems except rake. All other dependencies are packaged, including Rails. Sean Bill Barnard wrote: On Sun, 2008-05-18 at 17:06 +0200, Torleif Berger wrote: How can I upgrade radiant to the new version 0.6.7 on DreamHost? I do gem update radiant, and it works for a while, then ends with Killed ( ? ). Dreamhost runs a procwatch daemon that kills any process that takes excessive memory. Most gem processes (update, install, etc.) use a lot of memory when checking dependencies. The way I've worked around this in the past is to install the gem manually and resolve dependencies myself. Download the gem file, then from the directory containing the gem run: gem install --local gem_name I added this note to http://wiki.dreamhost.com/index.php/RubyGems Best of luck, Bill ___ 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 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] New metatags for keywords, description feature
First of all, thanks very much to the dev team for all of the latest release activity. It is greatly appreciated! I do have a question about the new metatags fields for keywords and description. These work great, but I noticed that there is no way to set them to inherit (unless I am missing something). It does not look like you can set these fields on a parent page and have the children inherit them. I thought that this would be the desired behavior, but maybe I am missing something. Thanks. Jamey Cribbs ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
Ok, so now that you have a running Radiant app, you now should do the following to install the extension: 1. Copy the Styles 'n Scripts Extension to the following path: radiant_app/vendor/extensions/styles_n_scripts You can find the latest version of the extension here: https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/v0.2.2 2. From your radiant_app directory, migrate the extension's db changes (adding the text_assets table). Run: rake radiant:extensions:styles_n_scripts:migrate If you have any problems, run the rake task with the '--trace' option to show the details (and post them here). 3. Finally, copy the images used by the extension. Again, from your radiant_app directory, run: rake radiant:extensions:styles_n_scripts:update This doesn't sound like where your problem lies but, if you should have any problems here, run rake with the --trace option again. Good luck and let us know how it goes and post any specific error messages here. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish [EMAIL PROTECTED] wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish [EMAIL PROTECTED] ___ 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
[Radiant] Fails when using Gallery in brand new Radiant setup
I'm having a problem with the Gallery extension: When setting up a new site most deployment related rake tasks stop working if your Radiant app contains the Gallery extension. This happends because of the first statement in the GalleryItem class (vendor/extensions/gallery/app/models/gallery_item.rb): has_attachment :storage = :file_system, :path_prefix = Radiant::Config[gallery.path_prefix], :processor = Radiant::Config[gallery.processor] As you can see in the above code, the Gallery extension uses the has_attachment plugin. When setting up the ruby environment the gallery_item.rb file is loaded and the above code is executed. When executed it makes a call to the [] method in Radiants config.rb which in turn tries to find the key gallery.path_prefix in the database by calling find_by_key(key). This fails with the message: Mysql::Error: Table 'radiant.config' doesn't exist: SHOW FIELDS FROM `config` This is because the config table has not yet been created (remember we are setting up a brand new site and have not run the db:bootstrap rake task yet). Whos fault is this? Is it the Gallery extension that must check to see if the config table exists? Or is it the config handler in Radiant that should make this check? I'll happely fix and submit a patch for this bug, but need to hear what you guys think is the best solution. /watson___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Fails when using Gallery in brand new Radiant setup
On 19/05/2008, at 17.29, Sean Cribbs wrote: It's generally not a good idea to install extensions until you have bootstrapped your database. Usually I would agree with you on this, but in this case I've set it all up locally in my development environment. Now I want to put the site online. It's in Subversion and I'm deploying with Capistrano to the production server. Because I've been using it locally to set everything up, all the extensions and plugins are already in the Subversion repository. So uninstalling the extensions just to get it up and running sounds like the wrong way to solve this. If multiple developers are working on the same project, new developers should be able to join - also after extensions have been installed and comitted to the source repository. That said, maybe the Gallery extension could avoid loading that model until it's absolutely needed? Yes that is one solution. But what about building a safety valve into Radiant it self: Do not load any extensions unless the database have been bootstrapped? /watson___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] New metatags for keywords, description feature
Personally, I'd like to see inheritance of meta info be optional and not the default. Sean Chris Parrish wrote: I just wanted to mention that I just noticed this change and am glad to see it implemented in core as well. It eliminates the need for my page_meta extension. I too, like the inheritance idea (an optional attribute of the tag) but I would also like to see a feature I had implemented in my extension. I the 'tag' attribute (mine was 'as_tag'), I had allowed true | false | unless_blank for the reverse case that Jamey is mentioning. I have sites where I *don't* want keywords to inherit. They need to be explicitly defined or else the page gets none. So, by using the 'unless_blank' option, I was able to prevent the page from kicking out an empty set of meta tags. I'd be happy to write up a patch for this if others think that this would be helpful. -Chris Jamey Cribbs wrote: First of all, thanks very much to the dev team for all of the latest release activity. It is greatly appreciated! I do have a question about the new metatags fields for keywords and description. These work great, but I noticed that there is no way to set them to inherit (unless I am missing something). It does not look like you can set these fields on a parent page and have the children inherit them. I thought that this would be the desired behavior, but maybe I am missing something. Thanks. Jamey Cribbs ___ 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] New metatags for keywords, description feature
I'm curious about why r:meta was implemented. Couldn't you get the same result by using page parts and dropping them in the appropriate place in your layout? I haven't used r:meta yet, so perhaps I'm unaware of some particular benefit -Jim On May 19, 2008, at 11:47 AM, Sean Cribbs wrote: Personally, I'd like to see inheritance of meta info be optional and not the default. Sean Chris Parrish wrote: I just wanted to mention that I just noticed this change and am glad to see it implemented in core as well. It eliminates the need for my page_meta extension. I too, like the inheritance idea (an optional attribute of the tag) but I would also like to see a feature I had implemented in my extension. I the 'tag' attribute (mine was 'as_tag'), I had allowed true | false | unless_blank for the reverse case that Jamey is mentioning. I have sites where I *don't* want keywords to inherit. They need to be explicitly defined or else the page gets none. So, by using the 'unless_blank' option, I was able to prevent the page from kicking out an empty set of meta tags. I'd be happy to write up a patch for this if others think that this would be helpful. -Chris Jamey Cribbs wrote: First of all, thanks very much to the dev team for all of the latest release activity. It is greatly appreciated! I do have a question about the new metatags fields for keywords and description. These work great, but I noticed that there is no way to set them to inherit (unless I am missing something). It does not look like you can set these fields on a parent page and have the children inherit them. I thought that this would be the desired behavior, but maybe I am missing something. Thanks. Jamey Cribbs ___ 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 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
RE: [Radiant] Update on DreamHost
thanks! that fixed it :) http://geekjuggler.net Date: Mon, 19 May 2008 09:29:16 -0500 From: [EMAIL PROTECTED] To: radiant@radiantcms.org Subject: Re: [Radiant] Update on DreamHost If you only want to use the production database, prefix your rake command with production: rake production db:migrate Sean Torleif Berger wrote: thanks! The update worked now :) But after having done rake radiant:update, and putting back ENV['GEM_PATH'] into config/environment.rb I try to do the rake db:migrate. But after a while I get: rake aborted! development database is not configured Which is true, cause I removed it, cause I didnt think I needed it. And it worked with 0.6.6. Does 0.6.7 require one? Even if i don't really want one? =/ -- From: Sean Cribbs [EMAIL PROTECTED] Sent: Monday, May 19, 2008 4:09 PM To: [EMAIL PROTECTED]; radiant@radiantcms.org Subject: Re: [Radiant] Update on DreamHost In case you didn't know, Radiant's gem doesn't depend on any gems except rake. All other dependencies are packaged, including Rails. Sean Bill Barnard wrote: On Sun, 2008-05-18 at 17:06 +0200, Torleif Berger wrote: How can I upgrade radiant to the new version 0.6.7 on DreamHost? I do gem update radiant, and it works for a while, then ends with Killed ( ? ). Dreamhost runs a procwatch daemon that kills any process that takes excessive memory. Most gem processes (update, install, etc.) use a lot of memory when checking dependencies. The way I've worked around this in the past is to install the gem manually and resolve dependencies myself. Download the gem file, then from the directory containing the gem run: gem install --local gem_name I added this note to http://wiki.dreamhost.com/index.php/RubyGems Best of luck, Bill ___ 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 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant _ Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! http://spaces.live.com/spacesapi.aspx?wx_action=createwx_url=/friends.aspxmkt=en-us___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] upgrading 0.6.6+shards extension to 0.6.7
My experience with upgrading from 0.6.4 to 0.6.7, in case someone is in a similar situation... I'm using several extensions: gallery (0.7.8), scheduler (0.2), reorder (0.1 with the up/down icons in the adminUI), and shards (0.3). Having read in other posts that the shards extension was integrated into 0.6.7 and no longer needed, I removed the reference to it from config/environment.rb and deleted the shards directory from vendor/extensions. Installed the latest radiant gem and ran the rake update. The rake radiant:update creates a new config/environment.rb file. I updated it to put the RADIANT_GEM_VERSION constant back in and set it to 0.6.7. The rake production db:migrate failed with an error related to the reorder extension. Deleted the reorder directory from vendor/extensions and the migration ran without any errors. Gallery and scheduler extension did not cause any problems. Running 0.6.7, everything looking good (except pages are all out of order, of course). There are a couple of other extensions similar to reorder that I wanted to try, copy-move and a drag-n-drop reorder. Grabbed the copy-move from git, but its rake install failed because it needs the shards extension. Same thing with the drag-n-drop reorder. So, installed shards, updated the config/environment.rb file accordingly and the copy-move and a drag-n-drop reorder extensions installed without any problems. Tried removing the shards extension to see if it was still needed, but the webserver choked with a 505 error; put it back in and all seems to be okay. Hope this is helpful to someone. PS. copy-move and the drag-n-drop reorder extensions are great! Thanks. On Fri, May 16, 2008 at 5:44 PM, john muhl [EMAIL PROTECTED] wrote: UPGRADING FROM 0.6.x 1. Update the Radiant gem: % gem update radiant 2. Change the RADIANT_GEM_VERSION constant in config/environment.rb to 0.6.7. 3. Run the update rake task: % rake radiant:update 4. Run migrations: % rake db:migrate 5. Restart the server Should an existing shards extension be removed before upgrading? Is removing the shards edit from environment.rb and the shards folder from vendor/extensions the proper way to uninstall the extension version? thanks. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- marshal ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Using the gallery extension
Hi Ollivier. ...some of this you might have already figured out.
Create a new gallery by going to the Admin UI and clicking on the
Galleries tab. Click on the New Gallery button and from there
upload some pics, edit the gallery description, etc. Name the gallery
MyPics for example.
Then go to the Pages tab and create a new page, call it Photos for
example, and make sure you select the Gallery page type from the
Page Type drop-down selections. In the body of this page, you'll put
some html and radiant tags to display pics from your MyPics gallery.
Here's the code I use for my galleries with some explanations added:
!-- galleries --
r:gallery:if_galleries
div class=galleries
## I have several galleries, so the next statement loops through each
of them, producing links to the individual
## galleries. You can still do this even with only one gallery.
r:galleries:each level=current
div class=gallery
r:gallery:if_items
div class=thumb style=background-image:
url('r:gallery:item:thumb width=120 position=first /');
a href=r:gallery:gallery_url /
title=r:gallery:name /
r:gallery:name /
/a
/div
/r:gallery:if_items
div class=description
h2r:gallery:link //h2
pr:gallery:description //p
/div
div class=clearer/div
/div
/r:galleries:each
/div
/r:gallery:if_galleries
!-- end galleries --
r:gallery:unless_galleries
!-- items --
r:gallery:item:unless_current
r:gallery:if_items
div class=gallery
pr:gallery:description //p
## This next loop picks up information about each item (ie. photo) in
the gallery and creates thumbnails and links
## to each of the photos. This is what you see when you click on the
gallery link produced above.
r:gallery:items:each
!-- item --
div class=container
div class=thumb style=background-image:
url('r:gallery:item:thumb width=150 /')
a href=r:gallery:item:thumb width=500 /
rel=lightbox[r:gallery:name /] title=r:gallery:item:name /
r:gallery:item:name /
/a
/div
/div
!-- end item --
/r:gallery:items:each
div class=clearer/div
/div
/r:gallery:if_items
/r:gallery:item:unless_current
!-- end items --
!-- item page --
## This next bit is what formats the page for individual photos, with
navigation links to next/previous items.
r:gallery:item:if_current
r:gallery:item:current
div class=item
div class=navigation
div class=prev
r:gallery:item:if_prev
a href=r:gallery:item:prev_page_url /laquo;
prev/a
/r:gallery:item:if_prev
/div
div class=next
r:gallery:item:if_next
a href=r:gallery:item:next_page_url /next
raquo;/a
/r:gallery:item:if_next
/div
div class=clearer/div
/div
div class=clearer/div
h2r:gallery:item:name //h2
div class=image
a href=r:gallery:item:path /
img src=r:gallery:item:thumb width=450 /
alt=r:gallery:item:name / /
/a
/div
p
r:gallery:item:description /
/p
/div
/r:gallery:item:current
/r:gallery:item:if_current
!-- end item page --
/r:gallery:unless_galleries
Most of the above code will be in the sample gallery, if you installed it.
Assuming you used my example names, you can go to
yourwebsiteaddress/photos (the Photos gallery-type page) and the
above code should display your MyPics gallery (and any others you
add later).
Hope this helps.
On Sun, May 18, 2008 at 1:04 AM, Ollivier Robert [EMAIL PROTECTED] wrote:
OK, I guess I must be missing something obvious but I just can't see
how it works. I've created public/galleries, create a Test one, put
a picture in it and... where is it supposed to appear?
/galleries/index? /galleries/Test? Do I have to create an new Page
with one of the gallery layouts, probably with a Gallery page type?
Is it documented somewhere??
Thanks.
--
Ollivier Robert -
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
--
marshal
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search:
