[Radiant] Gem dependencies
How do I set up gem dependencies in Radiant? When I include a "config.gem 'foo'" in environment.rb, I get the following error: /config/environment.rb:88: private method `gem' called for # (NoMethodError) Manuel ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Cycle extension
Oh, bummer. I thought I checked the standard tags. Well then, use the built in tag I guess... Manuel On Wed, Jan 14, 2009 at 6:22 PM, Sean Cribbs wrote: > Radiant already includes an tag which essentially does the same > thing, but doesn't use the helper. > > Sean > > Manuel Meurer wrote: >> >> Hi all! >> >> Just wanted to tell you quickly about an extension I wrote a couple of >> days ago that might be useful to somebody else as well. >> http://github.com/manuelmeurer/radiant-cycle-extension >> It basically makes the ActionView::Helpers::TextHelper::cycle function >> available through the tag, so you can do stuff like >> >> >> ">bla >> >> >> Did something like that exist already? >> I didn't really investigate I have to admit... >> >> Manuel >> ___ >> 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] Cycle extension
Hi all! Just wanted to tell you quickly about an extension I wrote a couple of days ago that might be useful to somebody else as well. http://github.com/manuelmeurer/radiant-cycle-extension It basically makes the ActionView::Helpers::TextHelper::cycle function available through the tag, so you can do stuff like ">bla Did something like that exist already? I didn't really investigate I have to admit... Manuel ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Edit History Extension
Gosh darnit! Completely missed that one... Good catch, Nicholas! Manuel On Wed, Jan 7, 2009 at 6:17 PM, Nicholas Henry wrote: > You might want to checkout what is available on github. For example: > > http://github.com/astashov/page_versioning/tree/master > > Cheers, > Nicholas > > > On Wed, Jan 7, 2009 at 7:46 AM, Tim Gossett wrote: >> On Mon, Jan 5, 2009 at 12:09 PM, Manuel Meurer >> wrote: >> >>> Tim, why would you like the git option better? For me it seems cleaner to >>> have all your stuff in one place, not the pages in a db and page versions in >>> git. >>> >> >> Good point. >> -1 for Acts like Git. >> +1 for Acts as Versioned. >> >> -- >> Tim >> ___ >> 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] Edit History Extension
Wow, lots of ideas here. I will go for the acts_as_versioned plugin as Andreas suggested. Once that is working we can think about saving incremental changes, different published versions etc. Tim, why would you like the git option better? For me it seems cleaner to have all your stuff in one place, not the pages in a db and page versions in git. Manuel On Mon, Jan 5, 2009 at 5:52 PM, Adam van den Hoven wrote: > You should also consider that if you're going to keep a version history that > only one revision (and certainly not necessarily the "current" revision) > should be published. This will allow you make a number of changes to a page > (especially useful if you extend the page preview extension to work with > versions) without affecting the current public version. This would also > allow you to reduce the size of the version history by keeping all the > incremental edits once this version is "published" collapse the version > history down to the published version. This gives you a history that > includes all the published versions and all the incremental changes since > the last published version. > > The core development team may want to consider a modification to the core > status properties which will (a) make it easier to do versioning as I've > mentioned and (b) make things clearer. The change is to break the current > status into 2 two fields. The first would be called "status" and would have > values like "draft", "reviewed", "published". The second field would be > "visibility" and would have values like "visible" and "invisible". Visible > and the three status values map directly to the current status values, and > published + invisible is the same as the current hidden status. This allows > you separate the purpose of a page (RSS, CSS, etc) from its status. I think > this simplifies the meaning of things since whether or not a page is > publicly accessible is completely independent of whether or not that page > appears in navigation. It will also make it easier, I think, to create a > workflow extension. > > My 2 cents . > > Adam > > On 5-Jan-09, at 8:14 AM, Andreas Roedl wrote: > >> Shouldn't be too hard to implement, at least, when you use one of the >> following plugins: >> >> Acts as versioned (see the example code): >> http://wiki.rubyonrails.org/rails/pages/ActsAsVersioned >> >> A Rails plugin that uses Git to version ActiveRecord fields: >> http://github.com/courtenay/acts_like_git/tree/master >> >> >> Andreas >> ___ >> 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] Edit History Extension
Hello world. I was thinking about creating an extension that saves the edit history for pages, layouts, snippets etc. That way you could go back to previous versions, perhaps make diffs between versions etc. Has something like that ever been done before? (Wow, what a dramatic sounding question...) Manuel ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Localization
Hi all! I am currently searching for a way to have a Radiant site with several languages (on the actual site, not the back-end). Searching on Github I found the following extensions: http://github.com/peburrows/translator/ http://github.com/cradle/radiant-translator-extension/ (seems to be an exact copy of http://github.com/peburrows/translator/, but not a fork... anyone know what's going on there?) http://github.com/Aissac/radiant-globalize-extension/ http://github.com/DefV/site_language/ http://github.com/lorenjohnson/radiant-language-switch/ I am gonna go with peburrows' translator extension first since it seems to do exactly what I want (one page part per language, storing the language setting in a cookie or discovery from the user's Accept-Language header). Does anyone have any experiences to share with any of those extensions? Manuel On Fri, Dec 19, 2008 at 10:05 AM, Haselwanter Edmund wrote: > Hi, > > On 19.12.2008, at 08:46, Istvan Hoka wrote: >> >> The extension is in use in production on two sites so far: >> http://www.atp-exodus.ro, (Romanian, English, German) and http://euro5.ro >> (Romanian and English). >> >> The version on github is slightly outdated but I will push my local >> changes asap if anyone is interested. > > That would be great :-) > > cu edi > > -- > DI Edmund Haselwanter, edm...@haselwanter.com, > http://edmund.haselwanter.com/ > > > > ___ > 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] 1st Extension - Class Call from module newext_tags.rb
Hi Bartee (or Lamar?), Where are the files newext_tags.rb and newext.rb located? When you declare methods in newext.rb (which should be located somewhere in \lib) you should declare them as class methods (def self.my_method) to be able to call them like this with Newext.my_method. You don't need to use the rake update command, it just copies the files from your extension's \public folder to the Radiant application's \public folder, which is not what you want at this point. Restarting the web server is necessary, though. Manuel On Sun, Dec 28, 2008 at 5:20 PM, Bartee Lamar wrote: > I am writing my 1st extension.. also new to rails and ruby.. oh why > not... > > In the newext_tags.rb module I am trying to call a method from a > newext.rb Class Newext > > The method cannot be found. > > If I move the Class definition at then end of the module NewextTags it > works. > > I am using the rake command: > > rake radiant:extensions:newext:update after each update to the code > > Also restarting the web server each time. > -- > 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 > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RSS Reader Extension and Wordpress Blogs
Hi Patrick, Looks like a bug in the extension. In lib/rss_reader.rb, it tries to read from the url (http://example.com/?feed=rss2 in your case), but just looks at the host and port (http://example.com:80 in your case) and dismisses the url parameters. The Github user bryanl has forked the extension from lorenjohnson and fixed the bug (see http://github.com/bryanl/radiant-rss-reader/commit/be405349966cbf520c44303f184453284843acdc). I recommend that you get a fresh copy from his latest version at http://github.com/bryanl/radiant-rss-reader/tree/master and try your luck with that one. Manuel On Mon, Nov 24, 2008 at 2:49 PM, Patrick Scheips <[EMAIL PROTECTED]> wrote: > Hi all, > > I'm using Radiant CMS with the RSS Reader Extension > (http://github.com/lorenjohnson/radiant-rss-reader) and would like to read > use the extension for reading in the RSS feed of a Wordpress Blog. > Unfortunately that doesn't work very well. > > Instead of the RSS articles Radiant just shows the following comment (only > visible when viewing the source comment, because it's a comment): > > > > I don't think that the extension is configured wrong, because the RSS reader > works well with various RSS feeds from various web pages. > Maybe the feed parser doesn't like the URL format of the feed, which is: > http://example.com/?feed=rss2, because there aren't any problems with some > (but not all) Wordpress RSS feeds using the URL format > http://example.com/feed/. > > Any ideas? > > Thanks, > Patrick > ___ > 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] Could not load extension from file:
Hi Michael, Could you run the rake task with --trace and post the output? Manuel On Wed, Nov 19, 2008 at 11:10 PM, Michael Krisher <[EMAIL PROTECTED]> wrote: > Hello, > I am trying deploying my first Radiant site and am running into issues when > trying to start the server/console/whatever and running the rake task to > migrate the extensions fails as well: > > > Could not load extension from file: fckeditor_extension. > # > Could not load extension from file: mailer_extension. > # > > > The directory names do not have _extension on them. > > vendor > extensions > fckeditor > mailer > > I've tried renaming the directories, etc I've installed them locally no > problem, but on production this is not the case. Radiant is frozen, if that > makes a difference. I'm deploying from a git repo. Anyone have any thoughts. > This is being deployed via capistrano to a Joyent Shared Accelerator. > > Thanks, > -- Mike > ___ > 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] Access the request object in tags
Hi Sean, Yes, this would solve the problem, but most extensions in my project use @page.render and I did not want to go through them all to change this... What do you think about this as a general solution? Manuel On Mon, Nov 17, 2008 at 5:24 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Manuel, > > Instead of render :text => @page.render, try @page.process(request, > response); @performed_render = true. > > Sean > > Manuel Meurer wrote: >> >> Hi! >> >> I've had a problem reoccuring in a couple of extensions and was not >> sure if it was a conceptual error on my side or if something was >> lacking in Radiant's tag system. I solved this problem now and wanted >> to share it to get some feedback from you guys. >> >> Take the 'url' tag from the standard tags for example. It tries to >> access the request object through tag.globals.page.request. >> Now this works fine if you render a page using the SiteController. But >> when you have an extension that uses its own controller and renders >> the page by calling 'render :text => @page.render', >> tag.globals.page.request is nil. >> I solved this problem by defining a filter in the >> ApplicationController that sets @page by looking at params[:url] and >> then sets @page.request (and @page.response). This way >> tag.globals.page.request is always available, no matter if you use >> your own controller or not. >> >> I hope this explanation was somewhat understandable. >> Do you guys think this is a good idea or do you see any problems? >> >> Manuel >> ___ >> 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] Access the request object in tags
Hi! I've had a problem reoccuring in a couple of extensions and was not sure if it was a conceptual error on my side or if something was lacking in Radiant's tag system. I solved this problem now and wanted to share it to get some feedback from you guys. Take the 'url' tag from the standard tags for example. It tries to access the request object through tag.globals.page.request. Now this works fine if you render a page using the SiteController. But when you have an extension that uses its own controller and renders the page by calling 'render :text => @page.render', tag.globals.page.request is nil. I solved this problem by defining a filter in the ApplicationController that sets @page by looking at params[:url] and then sets @page.request (and @page.response). This way tag.globals.page.request is always available, no matter if you use your own controller or not. I hope this explanation was somewhat understandable. Do you guys think this is a good idea or do you see any problems? Manuel ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Captcha
Did anyone ever get the simple_captcha plugin (http://expressica.com/simple_captcha/), or any other captcha plugin for that matter, to work with Radiant, i.e. show a captcha from rendering a tag? I'm having difficulties with that, since the view helpers of the plugin want to access the session, but the tag code is in the Page model, so no session there... Any comments and thoughts are appreciated. Manuel ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Problem using children:each and the Dynamic Image extension
Finally found the cause for this problem. Change the file lib/dynamic_image.rb in the Dynamic Image extension: #13 is config = tag.attr but should be config = tag.attr.dup Manuel On Sat, Oct 4, 2008 at 4:29 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote: > Hi! > > I'm experiencing some strange behavior using the children:each tag and > the Dynamic Image extension > (http://github.com/narced133/radiant-dynamic-image-extension) > I have a page with, say, 3 subpages and implement the following code > in the main page: > > > > > > I expect to see the title of each subpage in the given size, font > color and background color. > The thing that happens, though, is that only the title of the first > subpage appears in the correct size and colors. The other titles > appear in the size and colors defined as standards in my > environment.rb. > Seems that the tag attributes (size, color and background) are only > transferred for the first child. > > Any thoughts and comments are appreciated! > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Conditional Tags Extension
Ok, you're right. For me, would not feel right, though. Manuel On Sat, Oct 25, 2008 at 8:35 PM, Chris Parrish <[EMAIL PROTECTED]> wrote: > Manuel Meurer wrote: >>>> >>>> I think that there is a place for these tags and I'd love it if there >>>> was >>>> an easy way to use this to create both if_ and unless_ tags. Something >>>> like: >>>> >>>> conditional_tags "my_tag" do |tag| >>>> #return a boolean >>>> false >>>> end >>>> >>>> which would then create if_my_tag and unless_my_tag tags. For the if_ >>>> tag, >>>> the contents of the tag is executed when block returns true, and the >>>> reverse >>>> happens for the unless_ tag. >>>> >>> >>> This is interesting. I'll have to think about this. Essentially what >>> you're going for here is the removal of the attributes (something I agree >>> with). I bet my extension would be more comfortable if only you could >>> write: >>> >>> >>> >> >> This would not be valid XML. >> Attributes must have a value. >> http://www.w3.org/TR/xml/#attdecls >> >> Manuel >> ___ >> Radiant mailing list >> Post: Radiant@radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > > Radius isn't really xml -- it just eerily *looks* like xml. For example, > Radius will allow all kinds of characters in the tag that XML doesn't > permit. > > And that's fine. We aren't really marking up the document structurally > we're just borrowing a familiar notation for a templating language. > > I see no reason we couldn't create, say, a php-radius tag extension that > parsed: as a snippet tag. Or maybe ERB's > <%%> > > > I really wasn't proposing changing radius there (though I am intrigued by > the above). Instead I was looking at how the pattern of xml can make radius > tags less comprehensible. Round peg, square hole in some cases. > > Another example would be creating if, else if, else structures. I don't see > how you could use an xml-like notation to pull that off. Lucky for us, > if-then is plenty sufficient for 99.99% of all the needs for Radiant users. > > -Chris > ___ > 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] [ANN] Conditional Tags Extension
>> I think that there is a place for these tags and I'd love it if there was >> an easy way to use this to create both if_ and unless_ tags. Something like: >> >> conditional_tags "my_tag" do |tag| >> #return a boolean >> false >> end >> >> which would then create if_my_tag and unless_my_tag tags. For the if_ tag, >> the contents of the tag is executed when block returns true, and the reverse >> happens for the unless_ tag. > > This is interesting. I'll have to think about this. Essentially what > you're going for here is the removal of the attributes (something I agree > with). I bet my extension would be more comfortable if only you could > write: > > This would not be valid XML. Attributes must have a value. http://www.w3.org/TR/xml/#attdecls Manuel ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] parameterized_snippets extension
I think your extension folder has to be /vendor/extensions/parameterized_snippets. Always replace dashes by underscores. Manuel On Thu, Oct 23, 2008 at 1:27 AM, Luis Lebron <[EMAIL PROTECTED]> wrote: > How do you install the extension? In the vendors/extensions folder I did a > git clone > git://github.com/manuelmeurer/radiant-parameterized-snippets-extension.gitparameterized-snippets > and the files were downloaded from the repository but > I cannot get it to work. > > thanks, > > Luis > > On Tue, Oct 21, 2008 at 9:44 PM, Manuel Meurer <[EMAIL PROTECTED]>wrote: > >> Fixed, thanks for testing. >> Please grab a fresh copy from >> http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ >> >> Manuel >> >> On Tue, Oct 21, 2008 at 12:10 PM, Simon Josi <[EMAIL PROTECTED]> wrote: >> > I've got a case where parameters to snippets are not availabe. It >> > occurs when I call a snippet with parameters from another snippet: >> > >> > Content of page "Referenzen": >> > >> > >> > The "Referenzen" page contains childs with "text", "image" and "body" >> > parts defined. >> > >> > Content of snippet "list_childs_as_generic_entries": >> > >> > >> > >> > >> > >> >!(photo)()! >> > >> > >> > >> > >> > >> > >> > Content of snippet "image_with_border": >> > class=""> >> > >> > >> > >> > >> > >> > The class parameter is not set if a open the page "Referenzen". >> > >> > If i call the snippet "image_with_border" directly from a page and not >> > from a snippet, it works. >> > >> > Any ideas on that? >> > >> > Thx, >> > /smon >> > ___ >> > 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] parameterized_snippets extension
Oops... fixed. But you're right, the missing="ignore"-variant looks much cleaner. The if_var and unless_var tags should just be used if you want to execute several lines based on if that parameter exists or not. Manuel On Wed, Oct 22, 2008 at 11:49 AM, Simon Josi <[EMAIL PROTECTED]> wrote: > Thank you! > > Unfortunately i've came across another error: > The tag ist not working, as for my example it only works if I > change the line: > > class=""> > > to > > "> > > Stack trace: http://pastie.org/297893 > > The latter variant is absolutely perfect mor me though, thank you. > > > /simon > > On Wed, 22 Oct 2008 04:44:32 +0200 > "Manuel Meurer" <[EMAIL PROTECTED]> wrote: > >> Fixed, thanks for testing. >> Please grab a fresh copy from >> http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ >> >> Manuel >> >> On Tue, Oct 21, 2008 at 12:10 PM, Simon Josi <[EMAIL PROTECTED]> wrote: >> > I've got a case where parameters to snippets are not availabe. It >> > occurs when I call a snippet with parameters from another snippet: >> > >> > Content of page "Referenzen": >> > >> > >> > The "Referenzen" page contains childs with "text", "image" and >> > "body" parts defined. >> > >> > Content of snippet "list_childs_as_generic_entries": >> > >> > >> > >> > >> > >> >!(photo)()! >> > >> > >> > >> > >> > >> > >> > Content of snippet "image_with_border": >> > class="> > name="class" />"> > > class="top"> > > class="body"> > > class="bottom"> >> > >> > The class parameter is not set if a open the page "Referenzen". >> > >> > If i call the snippet "image_with_border" directly from a page and >> > not from a snippet, it works. >> > >> > Any ideas on that? >> > >> > Thx, >> > /smon >> > ___ >> > 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] parameterized_snippets extension
Fixed, thanks for testing. Please grab a fresh copy from http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ Manuel On Tue, Oct 21, 2008 at 12:10 PM, Simon Josi <[EMAIL PROTECTED]> wrote: > I've got a case where parameters to snippets are not availabe. It > occurs when I call a snippet with parameters from another snippet: > > Content of page "Referenzen": > > > The "Referenzen" page contains childs with "text", "image" and "body" > parts defined. > > Content of snippet "list_childs_as_generic_entries": > > > > > >!(photo)()! > > > > > > > Content of snippet "image_with_border": > class=""> > > > > > > The class parameter is not set if a open the page "Referenzen". > > If i call the snippet "image_with_border" directly from a page and not > from a snippet, it works. > > Any ideas on that? > > Thx, > /smon > ___ > 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] [ANN] Updated fork of radiant-mail-to-extension
> That block won't be called until it hits in the snippet. Right, but I think what Casper is looking for is a way to define a snippet parameter in the inner template of with ... in the page and then access it via in the snippet, not using . On Sat, Oct 18, 2008 at 4:16 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Actually, you wouldn't. That block won't be called until it hits /> in the snippet. I think adding arbitrary attributes on the snippet tag > seems reasonable. Well-designed and -specced patches will be accepted! > > Sean > > Manuel Meurer wrote: >> >> Jepp, I found that out a minute ago as well. >> Never used that feature, though. >> >> It would still be possible to do something like Casper suggested, but >> to do it cleanly you would have to filter out the > name="...">... part when calling in the snippet... >> not so nice. >> >> I just included another feature in the parameterized snippets extension, >> though. >> You can now do > matches=".le(?:ph|f)ant">... to check if a parameter >> matches a certain regex. >> >> Manuel >> >> On Sat, Oct 18, 2008 at 3:46 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: >> >>> >>> Snippets already support "inner-templates" via . >>> >>> Sean >>> >>> Casper Fabricius wrote: >>> >>>> >>>> Great - thanks! >>>> >>>> What would it take to also make it possible to provide "inner templates" >>>> as parameters for snippets? >>>> >>>> For example: >>>> >>>> >>>> >>>> Lions are great cats >>>> Read more >>>> >>>> >>>> >>>> Med venlig hilsen / Best regards, >>>> Casper Fabricius >>>> http://casperfabricius.com >>>> >>>> On 18/10/2008, at 13.23, Manuel Meurer wrote: >>>> >>>> >>>>> >>>>> Done. >>>>> >>>>> Manuel >>>>> >>>>> On Sat, Oct 18, 2008 at 12:49 PM, Manuel Meurer >>>>> <[EMAIL PROTECTED]> >>>>> wrote: >>>>> >>>>>> >>>>>> Will do. >>>>>> >>>>>> Manuel >>>>>> >>>>>> On Sat, Oct 18, 2008 at 12:00 PM, Casper Fabricius >>>>>> <[EMAIL PROTECTED]> wrote: >>>>>> >>>>>>> >>>>>>> Looks like something I could use. How does it work? Could add some >>>>>>> examples >>>>>>> and explain about any limitations in the readme-file? >>>>>>> >>>>>>> Med venlig hilsen / Best regards, >>>>>>> Casper Fabricius >>>>>>> http://casperfabricius.com >>>>>>> >>>>>>> On 18/10/2008, at 00.55, Manuel Meurer wrote: >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> Yep, I use in my parameterized snippets extension: >>>>>>>> >>>>>>>> >>>>>>>> http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ >>>>>>>> The idea originates from here, though: >>>>>>>> http://www.nabble.com/Snippets-with-Parameter(s)-td19772449.html >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> BTW, anyone heard anything about a Radius tag? Or >>>>>>>>> anything >>>>>>>>> about >>>>>>>>> setting arbitrary page variables? >>>>>>>>> >>>>>>>> >>>>>>>> ___ >>>>>>>> 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 > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Updated fork of radiant-mail-to-extension
Jepp, I found that out a minute ago as well. Never used that feature, though. It would still be possible to do something like Casper suggested, but to do it cleanly you would have to filter out the ... part when calling in the snippet... not so nice. I just included another feature in the parameterized snippets extension, though. You can now do ... to check if a parameter matches a certain regex. Manuel On Sat, Oct 18, 2008 at 3:46 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: > Snippets already support "inner-templates" via . > > Sean > > Casper Fabricius wrote: >> >> Great - thanks! >> >> What would it take to also make it possible to provide "inner templates" >> as parameters for snippets? >> >> For example: >> >> >> >>Lions are great cats >>Read more >> >> >> >> Med venlig hilsen / Best regards, >> Casper Fabricius >> http://casperfabricius.com >> >> On 18/10/2008, at 13.23, Manuel Meurer wrote: >> >>> Done. >>> >>> Manuel >>> >>> On Sat, Oct 18, 2008 at 12:49 PM, Manuel Meurer <[EMAIL PROTECTED]> >>> wrote: >>>> >>>> Will do. >>>> >>>> Manuel >>>> >>>> On Sat, Oct 18, 2008 at 12:00 PM, Casper Fabricius >>>> <[EMAIL PROTECTED]> wrote: >>>>> >>>>> Looks like something I could use. How does it work? Could add some >>>>> examples >>>>> and explain about any limitations in the readme-file? >>>>> >>>>> Med venlig hilsen / Best regards, >>>>> Casper Fabricius >>>>> http://casperfabricius.com >>>>> >>>>> On 18/10/2008, at 00.55, Manuel Meurer wrote: >>>>> >>>>>> Yep, I use in my parameterized snippets extension: >>>>>> >>>>>> http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ >>>>>> The idea originates from here, though: >>>>>> http://www.nabble.com/Snippets-with-Parameter(s)-td19772449.html >>>>>> >>>>>>> BTW, anyone heard anything about a Radius tag? Or anything >>>>>>> about >>>>>>> setting arbitrary page variables? >>>>>> >>>>>> ___ >>>>>> 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] [ANN] Updated fork of radiant-mail-to-extension
Good idea. I'm gonna look into that. Manuel On Sat, Oct 18, 2008 at 1:53 PM, Casper Fabricius <[EMAIL PROTECTED]> wrote: > Great - thanks! > > What would it take to also make it possible to provide "inner templates" as > parameters for snippets? > > For example: > > > >Lions are great cats >Read more > > > > Med venlig hilsen / Best regards, > Casper Fabricius > http://casperfabricius.com > > On 18/10/2008, at 13.23, Manuel Meurer wrote: > >> Done. >> >> Manuel >> >> On Sat, Oct 18, 2008 at 12:49 PM, Manuel Meurer <[EMAIL PROTECTED]> >> wrote: >>> >>> Will do. >>> >>> Manuel >>> >>> On Sat, Oct 18, 2008 at 12:00 PM, Casper Fabricius >>> <[EMAIL PROTECTED]> wrote: >>>> >>>> Looks like something I could use. How does it work? Could add some >>>> examples >>>> and explain about any limitations in the readme-file? >>>> >>>> Med venlig hilsen / Best regards, >>>> Casper Fabricius >>>> http://casperfabricius.com >>>> >>>> On 18/10/2008, at 00.55, Manuel Meurer wrote: >>>> >>>>> Yep, I use in my parameterized snippets extension: >>>>> >>>>> http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ >>>>> The idea originates from here, though: >>>>> http://www.nabble.com/Snippets-with-Parameter(s)-td19772449.html >>>>> >>>>>> BTW, anyone heard anything about a Radius tag? Or anything >>>>>> about >>>>>> setting arbitrary page variables? >>>>> >>>>> ___ >>>>> 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] [ANN] Updated fork of radiant-mail-to-extension
Done. Manuel On Sat, Oct 18, 2008 at 12:49 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote: > Will do. > > Manuel > > On Sat, Oct 18, 2008 at 12:00 PM, Casper Fabricius > <[EMAIL PROTECTED]> wrote: >> Looks like something I could use. How does it work? Could add some examples >> and explain about any limitations in the readme-file? >> >> Med venlig hilsen / Best regards, >> Casper Fabricius >> http://casperfabricius.com >> >> On 18/10/2008, at 00.55, Manuel Meurer wrote: >> >>> Yep, I use in my parameterized snippets extension: >>> http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ >>> The idea originates from here, though: >>> http://www.nabble.com/Snippets-with-Parameter(s)-td19772449.html >>> >>>> BTW, anyone heard anything about a Radius tag? Or anything >>>> about >>>> setting arbitrary page variables? >>> >>> ___ >>> 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] [ANN] Updated fork of radiant-mail-to-extension
Will do. Manuel On Sat, Oct 18, 2008 at 12:00 PM, Casper Fabricius <[EMAIL PROTECTED]> wrote: > Looks like something I could use. How does it work? Could add some examples > and explain about any limitations in the readme-file? > > Med venlig hilsen / Best regards, > Casper Fabricius > http://casperfabricius.com > > On 18/10/2008, at 00.55, Manuel Meurer wrote: > >> Yep, I use in my parameterized snippets extension: >> http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ >> The idea originates from here, though: >> http://www.nabble.com/Snippets-with-Parameter(s)-td19772449.html >> >>> BTW, anyone heard anything about a Radius tag? Or anything >>> about >>> setting arbitrary page variables? >> >> ___ >> 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] Radiant tag errors
I agree, Jim. You should only see the 500 page in development mode. In production mode, the message of the thrown error is shown directly on the page instead of the rendered tag. No need to poke around in page_context.rb, unless it's important for you to have the same behavior in development mode. Manuel On Sat, Oct 18, 2008 at 4:09 AM, Jim Gay <[EMAIL PROTECTED]> wrote: > On Oct 17, 2008, at 10:04 PM, Joe Van Dyk wrote: > >> This is in production mode. I'm using the radiant exception notifier >> plugin, which lets you put up your own 500 page. >> >> I'm using Radiant to build a website that lets some non-technical >> people update it. I'm trying to make it as easy as possible. It >> doesn't seem right, if one person makes an error on a snippet that's >> being used by every page, to not show the rest of the page's content >> (and replace the snippet or tag with the error message). That would >> let them easily figure out where the error occurred and would give >> them clues to how to fix it. >> >> Joe > > From my past experience and this recent test, that is what *should* be > happening. > What does the 500 error say? > > -Jim > ___ > 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] Radiant tag errors
As I said, I am pretty happy with Radius' tight validation, but I am
sure there is a way to fix this, probably as easy as defining your own
Radius Context and overwriting a couple of methods.
Poke around in radius.rb a bit, it's commented very well.
Manuel
On Sat, Oct 18, 2008 at 12:52 AM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> What if the user types in:
>
> (forgets to close the tag)
>
> (uses title instead of id)
>
> (doesn't specify the name)
>
> Instead of the exceptions bubbling up to the top and just seeing a 500
> error page, wouldn't it be better to catch those errors and insert the
> error message directly into page content?
>
> Joe
>
> On Fri, Oct 17, 2008 at 3:44 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>> >From radius.rb #284
>>
>># Like method_missing for objects, but fired when a tag is undefined.
>># Override in your own Context to change what happens when a tag is
>># undefined. By default this method raises an UndefinedTagError.
>>def tag_missing(name, attributes, &block)
>> raise UndefinedTagError.new(name)
>>end
>>
>> Guess it's just a preference thing.
>> I like strong validation.
>>
>> Manuel
>>
>> On Fri, Oct 17, 2008 at 11:54 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>> Makes sense -- why wouldn't that be that way by default?
>>>
>>> Joe
>>>
>>> On Fri, Oct 17, 2008 at 1:37 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>>>> Change #28 in vendor/radiant/app/models/page_context.rb from
>>>>
>>>> raise StandardTags::TagError.new(e.message)
>>>>
>>>> to
>>>>
>>>> "Radius error: #{e.message}"
>>>>
>>>> Manuel
>>>>
>>>> On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>>>> Err, sure:
>>>>>
>>>>> On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>>>>>> What exactly do you mean by "messes up a radiant tag"?
>>>>>> Do you have an example?
>>>>>>
>>>>>> Manuel
>>>>>>
>>>>>> On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>>>>>> Right now, when an editor messes up a radiant tag, a 500 page gets
>>>>>>> rendered.
>>>>>>>
>>>>>>> Would it be possible to display the page content, except for the
>>>>>>> radiant tag that had the error, and show the error message in place of
>>>>>>> that tag?
>>>>>>>
>>>>>>> Joe
>>>>>>> ___
>>>>>>> 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
>
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Updated fork of radiant-mail-to-extension
Yep, I use in my parameterized snippets extension: http://github.com/manuelmeurer/radiant-parameterized-snippets-extension/ The idea originates from here, though: http://www.nabble.com/Snippets-with-Parameter(s)-td19772449.html > BTW, anyone heard anything about a Radius tag? Or anything about > setting arbitrary page variables? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant tag errors
>From radius.rb #284
# Like method_missing for objects, but fired when a tag is undefined.
# Override in your own Context to change what happens when a tag is
# undefined. By default this method raises an UndefinedTagError.
def tag_missing(name, attributes, &block)
raise UndefinedTagError.new(name)
end
Guess it's just a preference thing.
I like strong validation.
Manuel
On Fri, Oct 17, 2008 at 11:54 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> Makes sense -- why wouldn't that be that way by default?
>
> Joe
>
> On Fri, Oct 17, 2008 at 1:37 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>> Change #28 in vendor/radiant/app/models/page_context.rb from
>>
>> raise StandardTags::TagError.new(e.message)
>>
>> to
>>
>> "Radius error: #{e.message}"
>>
>> Manuel
>>
>> On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>> Err, sure:
>>>
>>> On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>>>> What exactly do you mean by "messes up a radiant tag"?
>>>> Do you have an example?
>>>>
>>>> Manuel
>>>>
>>>> On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>>>> Right now, when an editor messes up a radiant tag, a 500 page gets
>>>>> rendered.
>>>>>
>>>>> Would it be possible to display the page content, except for the
>>>>> radiant tag that had the error, and show the error message in place of
>>>>> that tag?
>>>>>
>>>>> Joe
>>>>> ___
>>>>> 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] Nested tags
Here you go: http://github.com/manuelmeurer/radius-improved/tree/master Manuel On Fri, Oct 17, 2008 at 10:15 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > On Sat, Oct 11, 2008 at 3:59 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote: >> I am using an extension that gives me parameterized snippets (like >> here: http://www.ruby-forum.com/topic/125007#601242). Now, if I pass a >> value into a snippet, I would like to be able to pass it on to a tag >> as a parameter, which isn't currently possible in Radius. >> E.g., I want to do this: >> >> Page: >> >> >> >> Snippet my_snippet: >> >> >> >> With a few changes in Radius this works for me now. >> I didn't test it a lot yet but at least for what I want to use it for >> it works fine. >> >> The changes were quite simple so I wonder why it wasn't done like that >> from the beginning. >> Did anyone else ever feel the need to do something like that? > > Yes, we do feel that need. Please release ur codez! > ___ > 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] Radiant tag errors
Change #28 in vendor/radiant/app/models/page_context.rb from
raise StandardTags::TagError.new(e.message)
to
"Radius error: #{e.message}"
Manuel
On Fri, Oct 17, 2008 at 9:31 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
> Err, sure:
>
> On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer <[EMAIL PROTECTED]> wrote:
>> What exactly do you mean by "messes up a radiant tag"?
>> Do you have an example?
>>
>> Manuel
>>
>> On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote:
>>> Right now, when an editor messes up a radiant tag, a 500 page gets rendered.
>>>
>>> Would it be possible to display the page content, except for the
>>> radiant tag that had the error, and show the error message in place of
>>> that tag?
>>>
>>> Joe
>>> ___
>>> 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] Radiant tag errors
What exactly do you mean by "messes up a radiant tag"? Do you have an example? Manuel On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > Right now, when an editor messes up a radiant tag, a 500 page gets rendered. > > Would it be possible to display the page content, except for the > radiant tag that had the error, and show the error message in place of > that tag? > > Joe > ___ > 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] slug inside url_matches
I patched Radius so that you can use tags as attributes in other tags. (Posted to this list five days ago) Extremely useful and only a couple of lines have to be changed actually. If anyone is interested I can make a patch. Manuel On Thu, Oct 16, 2008 at 7:12 PM, Chris Parrish <[EMAIL PROTECTED]> wrote: > For sure Radiant's parser won't permit tags within tags but this sounds like > a job for... > an extension I built and need to re-release. > > I have some pretty lofty goals for this weekend involving Radiant. And > getting my conditionals extension back online is one of them. So maybe > I'll have something for you next week (fingers crossed). > > Just FYI, using my extension you'd do something like: >your stuff here > > -Chris > > > Jeffrey Jones wrote: >> >> Hoi all, >> >> Does anyone know how I could get the following working? >> >> > ignore_case="true"> style="display: none;" > >> >> Basically, if the page's slug is in the url somewhere I want the css style >> display to be none. I have tried with double and single quotes but this >> doesn't appear to be working. Using a hard-coded value instead works. I am >> assuming the isn't being translated to the actual slug value >> before being matched in the regexp. >> >> Thanks >> >> Jeff >> >> >> ___ >> 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] navigation tag question
Sure. Have a look at standard_tags.rb #667 and hack away. Better yet, create a better_navigation extension and publish it on Github so everybody else can use it as well. Manuel On Fri, Oct 17, 2008 at 6:58 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > Wow -- that's craziness. Wonder if it would be possible or advisable > to modify the navigation tag to be smarter as to what it highlights as > being the active link? > > On Fri, Oct 17, 2008 at 8:44 AM, Manuel Meurer <[EMAIL PROTECTED]> wrote: >> I found the r:navigation tag become too limited to do that kind of stuff. >> See below for an example of how to do your navigation "by hand". >> >> >> >>active> matches="^/$">inactive">Home >> >> >>> class="activeinactive"> >> >> >> >> >> >> > class="activeinactive"> >> >> >> >> >> >> >> >> >> >> >> On Thu, Oct 16, 2008 at 9:56 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: >>> In the below case, I would want the About link to be highlighted, >>> since that's the closest match to the current page. Is there a good >>> way to do that? >>> >>> Joe >>> >>> On Thu, Oct 16, 2008 at 12:39 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: >>>> Yes. Use if you want exact matches. However, often I just break >>>> out the navigation special cases (Home is a typical one). >>>> >>>> Sean >>>> >>>> Joe Van Dyk wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>> /> >>>>> >>>>> >>>>> >>>>> Say I'm on the page /about/page. Won't both the Home and the About >>>>> links have the 'selected' class specified? Since /about/page is a >>>>> child of both those pages? >>>>> >>>>> Joe >>>>> ___ >>>>> 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] navigation tag question
I found the r:navigation tag become too limited to do that kind of stuff. See below for an example of how to do your navigation "by hand". activeinactive">Home On Thu, Oct 16, 2008 at 9:56 PM, Joe Van Dyk <[EMAIL PROTECTED]> wrote: > In the below case, I would want the About link to be highlighted, > since that's the closest match to the current page. Is there a good > way to do that? > > Joe > > On Thu, Oct 16, 2008 at 12:39 PM, Sean Cribbs <[EMAIL PROTECTED]> wrote: >> Yes. Use if you want exact matches. However, often I just break >> out the navigation special cases (Home is a typical one). >> >> Sean >> >> Joe Van Dyk wrote: >>> >>> >>> >>> >>> >> /> >>> >>> >>> >>> Say I'm on the page /about/page. Won't both the Home and the About >>> links have the 'selected' class specified? Since /about/page is a >>> child of both those pages? >>> >>> Joe >>> ___ >>> 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] Nested tags
I am using an extension that gives me parameterized snippets (like here: http://www.ruby-forum.com/topic/125007#601242). Now, if I pass a value into a snippet, I would like to be able to pass it on to a tag as a parameter, which isn't currently possible in Radius. E.g., I want to do this: Page: Snippet my_snippet: With a few changes in Radius this works for me now. I didn't test it a lot yet but at least for what I want to use it for it works fine. The changes were quite simple so I wonder why it wasn't done like that from the beginning. Did anyone else ever feel the need to do something like that? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Problem using children:each and the Dynamic Image extension
Hi! I'm experiencing some strange behavior using the children:each tag and the Dynamic Image extension (http://github.com/narced133/radiant-dynamic-image-extension) I have a page with, say, 3 subpages and implement the following code in the main page: I expect to see the title of each subpage in the given size, font color and background color. The thing that happens, though, is that only the title of the first subpage appears in the correct size and colors. The other titles appear in the size and colors defined as standards in my environment.rb. Seems that the tag attributes (size, color and background) are only transferred for the first child. Any thoughts and comments are appreciated! ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
