Re: [Radiant] Shards in Radiant 0.6.7
Thanks Sean, worked like a charm. I this documented anywhere? Perhaps I should add an explanation to the wiki, since shards is now part of Radiant. Cheers, Casper On 19/05/2008, at 16:18, Sean Cribbs wrote: 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 # (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 ___ 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 Gallery Extension
> Processing GalleryItemsController#create (for 24.114.252.234 at 2008-05-18
> 05:47
> :55) [POST]
> Session ID:
> BAh7CCIMdXNlcl9pZGkHIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpG%0AbGF
> zaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsAOg5yZXR1cm5fdG8w--a1ffbb314fb3178222cccae86eec0
> 8c69e470641
> Parameters: {"form_id"=>"1", "format"=>"js", "gallery_id"=>"5",
> "action"=>"cre
> ate", "gallery_item"=>{"uploaded_data"=>#},
> "controller"=>
> "gallery_items"}
>
>
> ActionController::InvalidAuthenticityToken
> (ActionController::InvalidAuthenticit
> yToken):
I didn't try the new radiant yet. It seems that I need to add the
authenticity_token in the form.
I'll add it asap and I let you know.
Thank you very much.
--
Andrea Franz
http://gravityblast.com - http://nimboo.net
___
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 Gallery Extension
> I didn't try the new radiant yet. It seems that I need to add the > authenticity_token in the form. > I'll add it asap and I let you know. > Thank you very much. Added. You can pull from github, let me know. -- Andrea Franz http://gravityblast.com - http://nimboo.net ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] File based layout extension now compatible with 0.6.7
My extension for using standard Rails layout files with Radiant pages are now fully compatible with 0.6.7. Get it here: http://svn.casperfabricius.com/extensions/file_based_layout/tags/for-radiant-0.6.7/ = File Based Layout This extension allows pages served by Radiant to share a standard file- based Rails layout with Rails-generated pages. Full ERb, HAML or any other rendering engine can be used as normal in the layout, however, Radiant tags cannot currently be used in the layouts. Tested with Radiant 0.6.7 == Installation 1. Place this extension in the RAILS_ROOT/vendor/extensions/ file_based_layout directory 2. Run % rake db:migrate:extensions == Usage You must have a Rails layout file ready in the app/views/layouts/ directory of Radiant or an extension. === The Rails layout (typically .html.erb) file There are no special requirements to the layout file. It contain anything a normal Rails app will accept. The body page part is always rendered where it says <%= yield %> in the layout. Other page parts are rendered where they yielded by their name. For instance, the page part "extended" are rendered where the layout says <%= yield :extended %>. === The Radiant Administration interface Create a new layout from the "Layouts tab". Click the "More" link below the "Name" text-box, and select a layout file. Any contents in the "Body" text area will be ignored. Any page that has this new Layout, or has inherited the layout, will now render using the selected Rails layout file. == Changes made by this extension * layout_file field added to the Layouts table * file_based? method added to the Layout model * SiteController's process_page method aliased to render using a file- based layout, or normal * Render methods added to SiteController (eventually forwarding to Page's render methods), to be able to map various page parts to different content snippets in the layout * LayoutController's new and edit method changed to supply list of layout files to the view * Layout File drop-down list added to the Layout edit view (using shards) == About the author Casper Fabricius is a Danish Rails and Radiant developer living in Copenhagen. Weblog: http://casperfabricius.com Email: [EMAIL PROTECTED] ___ 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
1) nope that gave the same config error... but this way it worked charmly.. thank you rake RAILS_ENV="production" radiant:extensions:styles_n_scripts:migrate rake RAILS_ENV="production" radiant:extensions:styles_n_scripts:update p.s.: uncommenting ENV['RAILS_ENV'] ||= 'production' on config/enviroment.rb dont help 2) is there any way to call js/css files from anywhere of the page/layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Extension initialization code reloads on each request in dev mode
Radiant 0.6.7 seems to call the activate method of each extension upon each request when in development mode. Perhaps it has always been so, but it gets very visible and quite annoying when extensions use the "shards/facets" feature. Here is an example of a clean 0.6.7 with the reorder extension for 0.6.7 installed, where a couple of pages has been visited in development mode: This unwanted behaviour goes away in production mode, so it must be related to Rails reloading all files on each request in development mode. How do I avoid that the activate method is called upon each request in development mode - or - how do I avoid that it "caches" previously added fragments/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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
> is there any way to call js/css files from anywhere of the page/layout? > suppose, i use one template and many subpages? > but i use different/extra css/js files on subpages (and also common), for > example i will use accordion script on a subpage and putting this on > template or on header snippet is nonsense > so i am looking for a way to call these files from inside page/layout The way I usually do this is to put a content part in my layout's header called "head-meta" that appears in the header, e.g. http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en"> ...other header stuff ... Then you can just add a part to the page called (what else) head-meta and add whatever page-specific Javascript, CSS, meta tags, etc. you might want. Hope this helps! Rufo ___ 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
hmm, thats nice but it can be good to inject css/js files from body part inside head thank you On 5/20/08, Rufo Sanchez <[EMAIL PROTECTED]> wrote: > > > is there any way to call js/css files from anywhere of the page/layout? > > suppose, i use one template and many subpages? > > but i use different/extra css/js files on subpages (and also common), > for > > example i will use accordion script on a subpage and putting this on > > template or on header snippet is nonsense > > so i am looking for a way to call these files from inside page/layout > > > The way I usually do this is to put a content part in my layout's > header called "head-meta" that appears in the header, e.g. > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> > http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en"> > > ...other header stuff ... > > > > Then you can just add a part to the page called (what else) head-meta > and add whatever page-specific Javascript, CSS, meta tags, etc. you > might want. > > Hope this helps! > > > Rufo > > ___ > 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] Extension initialization code reloads on each request in dev mode
Casper, Someone already notified me of this and the fix is on github. I'll probably be rolling out a bugfix release on Friday. Sean Casper Fabricius wrote: Radiant 0.6.7 seems to call the activate method of each extension upon each request when in development mode. Perhaps it has always been so, but it gets very visible and quite annoying when extensions use the "shards/facets" feature. Here is an example of a clean 0.6.7 with the reorder extension for 0.6.7 installed, where a couple of pages has been visited in development mode: This unwanted behaviour goes away in production mode, so it must be related to Rails reloading all files on each request in development mode. How do I avoid that the activate method is called upon each request in development mode - or - how do I avoid that it "caches" previously added fragments/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
[Radiant] Re: [ANN] Radiant 0.6.7 Mordant Release
Sean Cribbs wrote: > Looks like it's time for another release of Radiant: > Radiant 0.6.7 "Mordant" ... Excellent! I'm glad to see Shards integrated into the core. Question about the switch to Haml... Does this affect extensions that utilize Shards and ERb files (either as .rhtml or .html.erb) and their ability to get injected into the new templates? I'm guessing they are all parsed first before being injected so they all play together nicely, but I figured I'd ask anyways. Also, any other known extension problems when upgrading from 0.6.6 to 0.6.7? Thanks, - Dave -- Posted via http://www.ruby-forum.com/. ___ 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: [ANN] Radiant 0.6.7 Mordant Release
Dave, Since ERb templates tend to be preferred by Rails, it should not affect extensions that override the defaults. Sean David Piehler wrote: Sean Cribbs wrote: Looks like it's time for another release of Radiant: Radiant 0.6.7 "Mordant" ... Excellent! I'm glad to see Shards integrated into the core. Question about the switch to Haml... Does this affect extensions that utilize Shards and ERb files (either as .rhtml or .html.erb) and their ability to get injected into the new templates? I'm guessing they are all parsed first before being injected so they all play together nicely, but I figured I'd ask anyways. Also, any other known extension problems when upgrading from 0.6.6 to 0.6.7? Thanks, - Dave ___ 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
If you'd rather keep this as an extension, Sean, I'd be happy to improve my PageMeta Extension (it needs some tests, at least). I'd also entertain additional features, recommendations to improve my code, or even donate it to the core team's repository -- whatever -- if it would help Radiant. Let me know -- happy to help either way. -Chris Sean Cribbs wrote: Jamey, That's great. In response to Jim, it was a common enough use case for people who do SEO for their sites and such a low overhead to implement, it seemed like a reasonable thing to add. I'd appreciate debates on this matter, however, as I'm open to culling superfluous code from the core. Sean Jamey Cribbs wrote: I just implemented what Jim suggested in my project and it works great. I created a meta_keywords and a meta_description page part in the pages that I want the tags. The nice thing is that you can use the inherit="true" parameter. On Mon, May 19, 2008 at 11:52 AM, Jim Gay <[EMAIL PROTECTED]> wrote: 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 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 ___ 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] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
I played around with the idea of creating an and tag or even enhancing the tag to let you add stylesheet/javascript content in addition to page part content. The problem is that in either case you have to specify which file you want (either explicitly or by first setting up a context to that item) so why not just manually type it and save the noise of yet another radius tag. This case, however, has me thinking the other way. (Plus the other benefit that your users only need to know the name of the script or stylesheet and not their full path -- my tag would build that). I'm going to be putting out a new rev shortly -- it would be simple to add a and tag. I'd certainly welcome other ideas as well. -Chris nurilized wrote: hmm, thats nice but it can be good to inject css/js files from body part inside head thank you On 5/20/08, Rufo Sanchez <[EMAIL PROTECTED]> wrote: is there any way to call js/css files from anywhere of the page/layout? suppose, i use one template and many subpages? but i use different/extra css/js files on subpages (and also common), for example i will use accordion script on a subpage and putting this on template or on header snippet is nonsense so i am looking for a way to call these files from inside page/layout The way I usually do this is to put a content part in my layout's header called "head-meta" that appears in the header, e.g. http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en"> ...other header stuff ... Then you can just add a part to the page called (what else) head-meta and add whatever page-specific Javascript, CSS, meta tags, etc. you might want. Hope this helps! Rufo ___ 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] [idea] snippets just like functions
hey, do you think it is a bad idea? creating a snippets that could take params could be good and will help dry, imho (actually thats what i need atm :D) what do you think? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] event_calendar - setup
Roland, I also came across this issue myself, but after a quick scouring through the mailing list I came up with this post of matt parrish's http://lists.radiantcms.org/pipermail/radiant/2007-June/005504.html basically you have to remove the application.rb and application_helper.rb files from within the event_calendar extension. I hope this helps, Marc. On Thu, May 15, 2008 at 9:59 AM, <[EMAIL PROTECTED]> wrote: > Hi, > > I am trying to set up the event_calendar extension > When I run the rake task, described in Step 3 of the README, I get the > following errors. I am running Radiant 0.6.5, but also tried 0.6.6 (via gem > install) > > 3. Migrate extensions: rake db:migrate:extensions > > http://github.com/seancribbs/radiant/tree/master/extensions/event_calendar/README > > rake radiant:extensions:event_calendar:update > (in /home/rol/rails/rchk) > rake aborted! > undefined local variable or method `no_login_required' for > Admin::WelcomeController:Class > > Any clues where to fix this? I allready checked the rake task but I could > not find a clue there. > > Thanx Roland > -- > Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten > Browser-Versionen downloaden: http://www.gmx.net/de/go/browser > ___ > 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] [idea] snippets just like functions
There's a patch on the dev site for "yielding" snippets. I'm not sure how I feel about it yet. Snippets are already sensitive to local context in the sense that they inherit it from the spot where they are rendered. It could be powerful, but it could also be a can of worms. Do you have a compelling use case? Sean nurilized wrote: hey, do you think it is a bad idea? creating a snippets that could take params could be good and will help dry, imho (actually thats what i need atm :D) what do you think? ___ 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] [idea] snippets just like functions
yes, i use breadcrumbs and slugs in many snippets and that makes it flexible thats nice but in my case, i list sub pages of a subpage and need to repeat the same process 8 or more times i just change the url thingy thats it: On 5/20/08, Sean Cribbs <[EMAIL PROTECTED]> wrote: > > There's a patch on the dev site for "yielding" snippets. I'm not sure how > I feel about it yet. Snippets are already sensitive to local context in the > sense that they inherit it from the spot where they are rendered. It could > be powerful, but it could also be a can of worms. Do you have a compelling > use case? > > Sean > > nurilized wrote: > >> hey, do you think it is a bad idea? >> >> creating a snippets that could take params could be good and will help >> dry, >> imho >> >> (actually thats what i need atm :D) >> >> what do you think? >> ___ >> 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] [idea] snippets just like functions
You can use snippets recursively, just be careful how you do it. Also you're complicating the href on that tag: use . You can find info about the "sitemapper" snippet that recursively calls itself on the wiki. Sean nurilized wrote: yes, i use breadcrumbs and slugs in many snippets and that makes it flexible thats nice but in my case, i list sub pages of a subpage and need to repeat the same process 8 or more times i just change the url thingy thats it: On 5/20/08, Sean Cribbs <[EMAIL PROTECTED]> wrote: There's a patch on the dev site for "yielding" snippets. I'm not sure how I feel about it yet. Snippets are already sensitive to local context in the sense that they inherit it from the spot where they are rendered. It could be powerful, but it could also be a can of worms. Do you have a compelling use case? Sean nurilized wrote: hey, do you think it is a bad idea? creating a snippets that could take params could be good and will help dry, imho (actually thats what i need atm :D) what do you think? ___ 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] [idea] snippets just like functions
thanks for href :) bad(good actually) of me, just learning radius tags and lovin 'em i took a look at sitemapper, but that is not what i want because my design dont let me list all of subpages recursively but instead i wished something that i would pass a param/arg to snippet just like calling a func but no problem, i can live w/o it :) just though it can be a good idea... On 5/20/08, Sean Cribbs <[EMAIL PROTECTED]> wrote: > > You can use snippets recursively, just be careful how you do it. Also > you're complicating the href on that tag: use . > > You can find info about the "sitemapper" snippet that recursively calls > itself on the wiki. > > Sean > > nurilized wrote: > >> yes, i use breadcrumbs and slugs in many snippets and that makes it >> flexible >> thats nice >> >> but in my case, i list sub pages of a subpage and need to repeat the same >> process 8 or more times >> >> i just change the url thingy thats it: >> >> >> >> >> >> >> >> >> On 5/20/08, Sean Cribbs <[EMAIL PROTECTED]> wrote: >> >> >>> There's a patch on the dev site for "yielding" snippets. I'm not sure >>> how >>> I feel about it yet. Snippets are already sensitive to local context in >>> the >>> sense that they inherit it from the spot where they are rendered. It >>> could >>> be powerful, but it could also be a can of worms. Do you have a >>> compelling >>> use case? >>> >>> Sean >>> >>> nurilized wrote: >>> >>> >>> hey, do you think it is a bad idea? creating a snippets that could take params could be good and will help dry, imho (actually thats what i need atm :D) what do you think? ___ 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Firefox vs. IE
Jared Blitzstein wrote: > What do you have the content type set as for the layout you're using? > IE might not think it's an HTML document. I think layouts inherit the "text/html" content type by default, but it doesn't hurt to set it anyway. Its good practice. -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
