[Radiant] Using as product catalog and E-commerce solution
Hey guys, i'm working on site which will use big product catalog for now, and they want to have chance to upgrade it later and add cart and payment solution there. Is there are ready solution for this in Radiant? Don't find extension like i need. -- With optimism, Dmitry Belitsky http://belitsky.info ___ 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 as product catalog and E-commerce solution
hi, I actually was looking for some approaches to this direction also. maybe you already know the spree ecommerce framework. it would be very interesting if someone has already some experice with integration of these two projects. regards 2009/11/24 Dmitry Belitsky dmitry.belit...@gmail.com Hey guys, i'm working on site which will use big product catalog for now, and they want to have chance to upgrade it later and add cart and payment solution there. Is there are ready solution for this in Radiant? Don't find extension like i need. -- With optimism, Dmitry Belitsky http://belitsky.info ___ 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] aggreate archive
Is back door still available and working on 0.8? I had a look for it the other day but couldn't find it on github or the ext.radiant.org site. Do you have a link? On 24 Nov 2009, at 05:57, Steven Southard wrote: Not sure why if_first doesn't work here but using back_door I was able to create a simple inline work around. Thanks, Steven On Nov 23, 2009, at 1:33 PM, Steven Southard wrote: Do you know any reason this doesn't work: r:archive:children:each r:if_first div class=date style=text-align:right;r:date format=%A, %B %d, %Y //div /r:if_first ... The date works fine without the if_first yet it is repeated many times. If I add the if_first I just get no date at all. On Nov 23, 2009, at 12:18 PM, Jim Gay wrote: With your code: r:archive:children The current page scope for the r:date tag is the current page. You'd need: r:archive:children:each Or: r:archive:childrenHere are the children r:each...more code.../r:each/r:archive:children This would change the scope to each of the children and iterate through them. I'm sure you've just been staring at it too long ;-) On Mon, Nov 23, 2009 at 12:27 PM, Steven Southard ste...@stevensouthard.com wrote: Okay a little closer. I'm using this on a aggregated archive day: r:aggregate urls=/blog-archives/media; /blog-archives/art-scene; r:archive:children div class=date style=text-align:right;r:date format=%A, %B %d, %Y //div h1r:link //h1 r:content / /r:archive:children/r:aggregate So on http://localhost:3000/blog-archives/2009/11/12 I was expecting the articles written on a given day but I only get the archive page with the date I made the archive page. Also Recursion error: already rendering the `body' part. Thanks for all the help so far. Steven On Nov 23, 2009, at 7:00 AM, Jim Gay wrote: Pull the latest. I just fixed that. On Mon, Nov 23, 2009 at 1:31 AM, Steven Southard ste...@stevensouthard.com wrote: Yes, I was trying it with a normal page and also I re-installed the extension and I got a few more options which make it more possible. I think I understand it a bit better, yet I still don't have it working. now on a request like: http://localhost:3000/blog-archives/ 2009/11/16/ I get: undefined method `next_day' for Mon Nov 16 00:00:00 -0600 2009:Time Any ideas on this one? On Nov 22, 2009, at 5:52 PM, Jim Gay wrote: Are you using it on an archive page? aggregate:archive is undefined on just regular pages. On Sun, Nov 22, 2009 at 4:44 PM, Steven Southard ste...@stevensouthard.com wrote: Does this work for anyone else? r:aggregate urls=/blog-archives/media; /blog-archives/art- scene; r:archive:children:each /r:archive:children:each /r:aggregate All I get is: undefined tag `archive' -- Jim Gay http://www.saturnflyer.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 -- Jim Gay Creative Director and Owner Saturn Flyer LLC j...@saturnflyer.com http://www.saturnflyer.com 571-403-0338 ___ 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] Page Event Extension
Hello, I was just taking a look at the Page Event Extension and wondered if anyone knew what the day, month, season and year pages were and how they worked? Are they like archive pages in that the grab the url in order to display events for that date? What tags enable you to do this - the only ones I see look like they require the dates manually setting... Also does anyone know what the season page is and why it only looks like it has two seasons -presumably these are months? Looks like a really interesting extension, would love to hear from people about how it works. Thanks, Dominic ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] (no subject)
For the first scenario you would could be a bit sneaky by hiding the filter select via JS (or perhaps overriding the _page_part.html.haml partial in your extension), and automatically setting it via JS or hardcoding it via a before_save hook on PagePart. For the second scenario (data cleanup), using a before_save hook on PagePart is the simplest way to get rid of dirty MS Word markup, as well as dealing with some of FCK's quirky markup. If you add a before_save hook, you can modify the content on its way back in the database to remove all troublesome markup, Office tags, etc. You might also find using Hpricot or Nokogiri useful for fixing/standardizing the markup. -Alex On Tue, Nov 24, 2009 at 12:17 AM, Cliff cgali...@gmail.com wrote: Is there a setting or an existing extension that locks down which filters are available to users? In one scenario, I've installed the FckEditor extension is installed and FckEditor is customized to meet the team's needs. I'd like to make this the required filter for standard users when creating new pages. This would allow some lockdown on what can and cannot be pubished, which would also help in my second scenario below. In another scenario, I have one of our blog authors who has some old habits I just can't break. Most notably they still like to use MS Word to write up their text. Since MS Word generates *horrendous* HTML, I'd like to prevent HTML from being used. I'd use r:escape_html for this and nest the content, but because of the order that nested tags are done, this causes proper HTML generated by the textile or markdown filters to get escaped as well. I'd like to find a way to all users to continue using textile or even raw HTML, but prresent some form of whitelist for what can be used. No embedded styles, for example, and only certain tags. Thoughts? -Cliff ___ 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] Page Event Extension
subsor...@gmail.com said the following on 11/24/2009 10:03 AM: Hello, I was just taking a look at the Page Event Extension and wondered if anyone knew what the day, month, season and year pages were and how they worked? Try installing it and you'll see that these are fields added to pages The 'calendar' is a dedicated page. Looks like a really interesting extension, would love to hear from people about how it works. it works real well. Just follow the instructions. -- Beware of bugs in the above code; I have only proved it correct, not tried it. -- Knuth ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] aggreate archive
This is where I got it. http://backdoor.rubyforge.org/ It works fine on 8.1 Steven On Nov 24, 2009, at 8:49 AM, subsor...@gmail.com wrote: Is back door still available and working on 0.8? I had a look for it the other day but couldn't find it on github or the ext.radiant.org site. Do you have a link? On 24 Nov 2009, at 05:57, Steven Southard wrote: Not sure why if_first doesn't work here but using back_door I was able to create a simple inline work around. Thanks, Steven On Nov 23, 2009, at 1:33 PM, Steven Southard wrote: Do you know any reason this doesn't work: r:archive:children:each r:if_first div class=date style=text-align:right;r:date format=%A, %B %d, %Y //div /r:if_first ... The date works fine without the if_first yet it is repeated many times. If I add the if_first I just get no date at all. On Nov 23, 2009, at 12:18 PM, Jim Gay wrote: With your code: r:archive:children The current page scope for the r:date tag is the current page. You'd need: r:archive:children:each Or: r:archive:childrenHere are the children r:each...more code.../r:each/r:archive:children This would change the scope to each of the children and iterate through them. I'm sure you've just been staring at it too long ;-) On Mon, Nov 23, 2009 at 12:27 PM, Steven Southard ste...@stevensouthard.com wrote: Okay a little closer. I'm using this on a aggregated archive day: r:aggregate urls=/blog-archives/media; /blog-archives/art- scene; r:archive:children div class=date style=text-align:right;r:date format=%A, %B %d, %Y //div h1r:link //h1 r:content / /r:archive:children/r:aggregate So on http://localhost:3000/blog-archives/2009/11/12 I was expecting the articles written on a given day but I only get the archive page with the date I made the archive page. Also Recursion error: already rendering the `body' part. Thanks for all the help so far. Steven On Nov 23, 2009, at 7:00 AM, Jim Gay wrote: Pull the latest. I just fixed that. On Mon, Nov 23, 2009 at 1:31 AM, Steven Southard ste...@stevensouthard.com wrote: Yes, I was trying it with a normal page and also I re-installed the extension and I got a few more options which make it more possible. I think I understand it a bit better, yet I still don't have it working. now on a request like: http://localhost:3000/blog-archives/ 2009/11/16/ I get: undefined method `next_day' for Mon Nov 16 00:00:00 -0600 2009:Time Any ideas on this one? On Nov 22, 2009, at 5:52 PM, Jim Gay wrote: Are you using it on an archive page? aggregate:archive is undefined on just regular pages. On Sun, Nov 22, 2009 at 4:44 PM, Steven Southard ste...@stevensouthard.com wrote: Does this work for anyone else? r:aggregate urls=/blog-archives/media; /blog-archives/art- scene; r:archive:children:each /r:archive:children:each /r:aggregate All I get is: undefined tag `archive' -- Jim Gay http://www.saturnflyer.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 -- Jim Gay Creative Director and Owner Saturn Flyer LLC j...@saturnflyer.com http://www.saturnflyer.com 571-403-0338 ___ 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] Upgrade Error
Hi, new user trying to upgrade: [r...@li104-134 radiant]# rake radiant:update --trace (in /var/www/html/radiant) rake aborted! Don't know how to build task 'radiant:update' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1728:in `[]' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2050:in `invoke_task' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in `standard_exception_handling' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run' /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31 /usr/bin/rake:19:in `load' /usr/bin/rake:19 -- Regards Kevin Bett ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page Event Extension
Hmm, How do you list the shows via the archives? I can see r:events:in_range:each but that requires start=/mm/dd manually specified in the tag. r:events:upcoming:each limit=10 just seems to list all upcoming events but is not scoped to the date in the archive... Is creating a simple list of events scoped by month/day possible? On 24 Nov 2009, at 15:31, Anton Aylward wrote: subsor...@gmail.com said the following on 11/24/2009 10:03 AM: Hello, I was just taking a look at the Page Event Extension and wondered if anyone knew what the day, month, season and year pages were and how they worked? Try installing it and you'll see that these are fields added to pages The 'calendar' is a dedicated page. Looks like a really interesting extension, would love to hear from people about how it works. it works real well. Just follow the instructions. -- Beware of bugs in the above code; I have only proved it correct, not tried it. -- Knuth ___ 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] Page Event Extension
subsor...@gmail.com said the following on 11/24/2009 11:53 AM: Hmm, How do you list the shows via the archives? I can see r:events:in_range:each but that requires start=/mm/dd manually specified in the tag. r:events:upcoming:each limit=10 just seems to list all upcoming events but is not scoped to the date in the archive... Is creating a simple list of events scoped by month/day possible? We're talking at cross purposes, then. The Page Event archive is quite separate from the Archive. Its for events that appear in the calendar. Presentations, meetings, trade shows, things like that. Think C*A*L*E*N*D*A*R You have fields on those pages that say when the EVENT is to occur, and that has nothing to do with when the page was written, published or updated. I presume you don't mean shows in your sentence in that sense. Its about shows as a noun, trade SHOWS, theatrical SHOWS, not as the verb. The Archive ties in with when the page was published, as in a Blog. Its quite separate and nothing to do with this plugin. I'm using Page Event for a site that has no blogging. The upcoming Events section take the next 3 from the /events. Which is what its supposed to do. I think you have the wrong idea of what this is for. Think in terms of a CALENDAR of events. Now, instead of the matrix of the calendar, 28. 29, 30 or 31 days per page, think in terms of a linear list that may be over more than one page of the calendar, as might be the case with a once-a-month event. Think C*A*L*E*N*D*A*R -- It's not a good idea to believe anything about security when read in the mass media. by the time it gets there it is usually sensationalized to the point where it's more about hype and marketing than anything else. - Ryan Permeh [ta...@millcomm.com] on Vuln-Dev ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page Event Extension
Sorry I should have been clearer, by shows I did mean events and by archives I meant the additional page types this extension adds: http://github.com/mghaught/radiant-page-event/tree/master/app/models/ e.g. event_archive_page.rb, event_month_index_page.rb, event_day_index_page.rb etc I understand I can list all future events, I also understand I can have a calendar but you can reveal more detailed event information in a list (a short description, content parts etc). I'd like to be able to have a *list* of all upcoming events but scoped to a certain month or a certain day. I saw that this could be done manually with the r:events:in_range:each start=/mm finish=/mm tag for each month but it would get impossible to manage on a more granular level for each day of the year. As I saw this extension added additional page types I simply wanted to know if anyone knew how they worked and what they added; they don't seem to alter the calendar behaviour and my first thought was that they would organise events by year/month/day just like the archive extension does for blog pages. I've just been poking around with it some more and it seems that the 'event month index page' does seem to have gained at least some of this functionality. r:archive:children:eachr:link /br //r:archive:children:each This seems to list events starting in the month (defined by url) but only events starting in that month and not events that carry over from the end of the previous month, those are only listed on the month they started - I'm not sure of its functionality I'm confused at to what these additional page types actually do...? Cheers, Dominic On 24 Nov 2009, at 17:43, Anton Aylward wrote: subsor...@gmail.com said the following on 11/24/2009 11:53 AM: Hmm, How do you list the shows via the archives? I can see r:events:in_range:each but that requires start=/mm/dd manually specified in the tag. r:events:upcoming:each limit=10 just seems to list all upcoming events but is not scoped to the date in the archive... Is creating a simple list of events scoped by month/day possible? We're talking at cross purposes, then. The Page Event archive is quite separate from the Archive. Its for events that appear in the calendar. Presentations, meetings, trade shows, things like that. Think C*A*L*E*N*D*A*R You have fields on those pages that say when the EVENT is to occur, and that has nothing to do with when the page was written, published or updated. I presume you don't mean shows in your sentence in that sense. Its about shows as a noun, trade SHOWS, theatrical SHOWS, not as the verb. The Archive ties in with when the page was published, as in a Blog. Its quite separate and nothing to do with this plugin. I'm using Page Event for a site that has no blogging. The upcoming Events section take the next 3 from the /events. Which is what its supposed to do. I think you have the wrong idea of what this is for. Think in terms of a CALENDAR of events. Now, instead of the matrix of the calendar, 28. 29, 30 or 31 days per page, think in terms of a linear list that may be over more than one page of the calendar, as might be the case with a once-a-month event. Think C*A*L*E*N*D*A*R -- It's not a good idea to believe anything about security when read in the mass media. by the time it gets there it is usually sensationalized to the point where it's more about hype and marketing than anything else. - Ryan Permeh [ta...@millcomm.com] on Vuln-Dev ___ 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] Page Event Extension
subsor...@gmail.com said the following on 11/24/2009 03:04 PM: I'm confused at to what these additional page types actually do...? You've got me confused now. Which extensions are you talking about? you're refering to r:archive and r:events ... Those are two separate extensions. The first comes with the basic Radiant - check the gem if you haven't frozen it into your working tree. The second is a separate plugin that you download and install manually. The Radiant core archive code extracts the Archive pages from their original place in the Radiant distribution. Pages of page-type=archive are intended to provide behaviour similar to a blog archive or a news archive. Child page URLs are altered to be in %Y/%m/%d format (2004/05/06). Looking at the code of the archive extension I see that its based on date published, as you would expect or a blog. The Page Event code adds extra fields and its operation is based on those extra fields. The Archive is based on each page having one specific date. The Page Event is oriented around the idea of a calendar, so that means an event may have a start data and an end date, as would be the case for a conference, a trade show or a Broadway show. They are two completely different things with different objectives. Trying to use them together is going to tie you into knots. -- The art of progress is to preserve order amid change and to preserve change amid order. --Alfred North Whitehead ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Recursion error: already rendering the part
Hello, i'm still getting error about recursion, it happens not only local, but on my server also. What should i check? Any ideas? How i can do same thing other way? Thanks. On Nov 20, 2009, at 1:39 PM, Dmitry Belitsky wrote: On Nov 20, 2009, at 12:02 AM, john muhl wrote: are you by any chance running radiant 0.9rc1 (or a recent master branch)? on a fresh 0.8.1 the snippet works as expected; on master i see the behavior you describe. the test case can be narrowed to: r:children:each r:content part=a/ r:content part=a/ /r:children:each On Thu, Nov 19, 2009 at 3:15 PM, Dmitry Belitsky dmitry.belit...@gmail.com wrote: Thanks for reply, but i can't find any mention of this part in other places. Only here. If i used this snipped on home page - it works, if i used it in other page: Recordings - here i want to show list of children, which have parts which i define in Stereotype: - Rec1 - Rec2 - Rec3 If i remove one of r:content part='amazon_link' / - this page works, if i left both - i get this: Recursion error: already rendering the `amazon_link' part. Any suggestions? Thanks. P.S. I used Paperclipped and Stereotype plugins if this matters. On Nov 19, 2009, at 10:43 PM, john muhl wrote: there is nothing wrong with that snippet. so maybe you have already entered the amazon_link part before you call the snippet; maybe in another snippet or a layout. On Thu, Nov 19, 2009 at 2:35 PM, Dmitry Belitsky dmitry.belit...@gmail.com wrote: Hey guys, take a look at http://pastie.org/706339 i get error: StandardTags::TagError in SiteController#show_page Recursion error: already rendering the `amazon_link' part. Can you help me fix it? -- With optimism, Dmitry Belitsky http://belitsky.info ___ 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 -- With optimism, Dmitry Belitsky http://belitsky.info -- With optimism, Dmitry Belitsky http://belitsky.info ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page Event Extension
I'm referring to the the Page Events Extension that I linked to: http://github.com/mghaught/radiant-page-event As well as the event and calendar support it extends radiant by also adding several pages types, event_archive_page.rb, event_month_index_page.rb, event_day_index_page.rb etc. These look similar to the page types added by the Archive extensions but are added by the Page Event Extension - they are not added by the Archive extension. In the admin area on any particular page, for the page type you can choose Event Archive, Event Month Index, Event Day Index ... as well as the selections for the Blog extension; Archive, Archive Month Index, Archive Day Index. Two different things. It looks like it filters the events by date in the same manner as the blog archive page type filters blog posts by date. You can filter manually with the r:events:in_range:each tag. I'd like to know if you can filter based on the url like the page types suggest and what these page types do? On 24 Nov 2009, at 21:42, Anton Aylward wrote: subsor...@gmail.com said the following on 11/24/2009 03:04 PM: I'm confused at to what these additional page types actually do...? You've got me confused now. Which extensions are you talking about? you're refering to r:archive and r:events ... Those are two separate extensions. The first comes with the basic Radiant - check the gem if you haven't frozen it into your working tree. The second is a separate plugin that you download and install manually. The Radiant core archive code extracts the Archive pages from their original place in the Radiant distribution. Pages of page-type=archive are intended to provide behaviour similar to a blog archive or a news archive. Child page URLs are altered to be in %Y/%m/%d format (2004/05/06). Looking at the code of the archive extension I see that its based on date published, as you would expect or a blog. The Page Event code adds extra fields and its operation is based on those extra fields. The Archive is based on each page having one specific date. The Page Event is oriented around the idea of a calendar, so that means an event may have a start data and an end date, as would be the case for a conference, a trade show or a Broadway show. They are two completely different things with different objectives. Trying to use them together is going to tie you into knots. -- The art of progress is to preserve order amid change and to preserve change amid order. --Alfred North Whitehead ___ 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
