[Radiant] EventCalendar (iCal) Update
For anyone using or interested in using the EventCalendar (iCal) extension I'd like to announce that it's once again available for check-out, now on the Radiant core extension repository here: http://dev.radiantcms.org/svn/radiant/tags/rel_0-6-4/extensions/event_calendar (stable) http://dev.radiantcms.org/svn/radiant/trunk/extensions/event_calendar (in development) * I've updated the README to better get you through the treacheries of installation and updated the example code so that it actually works (nice! :) NOTE: * This extension doesn't include any direct ability to directly manage events within Radiant but instead draws all it's events from any number or combination of iCal feeds (Google Calendar, .Mac, etc.) It has been carefully modeled to allow the easy addition of a direct entry interface for event within Radiant, so if this is more of your requirement I encourage you to take a look / take apart this code as a starting place. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] EventCalendar (iCal) Update
For anyone using or interested in using the EventCalendar (iCal) extension I'd like to announce that it's once again available for check-out, now on the Radiant core extension repository here: http://dev.radiantcms.org/svn/radiant/tags/rel_0-6-4/extensions/event_calendar (stable) http://dev.radiantcms.org/svn/radiant/trunk/extensions/event_calendar (in development) * I've updated the README to better get you through the trechouries of installation and updated the example code so that it actually works (nice!) :) NOTE: * This extension doesn't include any direct ability to directly manage events within Radiant but instead draws all it's events from any combination of iCal feeds (Google Calendar, .Mac, etc.) It has been carefully modeled to allow the easy addition of a direct event entry interface in Radiant, so if this is more of your requirement I encourage you to take a look / take apart the code of it as a solid starting place. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Multi-language pages with radiant?
Tonu, If there is an "official" Radiant approach it is as you detailed, with a separate root for each language using the Language Redirect extension which is available here on the "ThirdPartyExtensions" wiki page: http://wiki.radiantcms.org/Thirdparty_Extensions I have not tested it against any recent builds of Radiant, so I will assume for now it's up to date and working. In addition to this option I wrote a "Language Switch" extension recently for a client and they allowed me to share. While for most cases I am a fan of the multiple roots approach, in this case they really wanted to have a conditional tag to switch out parts of a page or layout to another language without having to manage two separate sites. It's not a particularly refined extension and it turns-off caching for all pages, but at least there is a bit of documentation in the README file :) : http://svn.fn-group.com/radiant_extensions/language_switch Finally, take a look at the mailing list archive for another recent discussion of this topic: http://lists.radiantcms.org/pipermail/radiant/2007-September/thread.html#6356 Good luck! Loren www.hellovenado.com On Nov 27, 2007, at 2:20 AM, Tõnu Runnel wrote: > Hi > > I didn't find an answer to my question through Google, maybe I didn't > know how to look. Anyway -- how do you make a multi-language website > with radiant? > > Is it so that you make your site structure under Radiant's "PAGES"-tab > like this: > > Home (redirects) > en (home) >Services >People >Contacts > de (home) >Dienste >Leute >Kontakte > > ... or is there a better practice? And if there isn't, how do you > redirect? Is there an "official" Radiant solution or I need the > language > redirect extension? > > Thanks! > Tõnu > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Multi-language pages with radiant?
Tonu, If there is an "official" Radiant approach it is as you detailed, with a separate root for each language using the Language Redirect extension which is available here on the "ThirdPartyExtensions" wiki page: http://wiki.radiantcms.org/Thirdparty_Extensions I have not tested it against any recent builds of Radiant, so I will assume for now it's up to date and working. In addition to this option I wrote a "Language Switch" extension recently for a client and they allowed me to share. While for most cases I am a fan of the multiple roots approach, in this case they really wanted to have a conditional tag to switch out parts of a page or layout to another language without having to manage two separate sites. It's not a particularly refined extension and it turns-off caching for all pages, but at least there is a bit of documentation in the README file :) : http://svn.fn-group.com/radiant_extensions/language_switch Finally, take a look at the mailing list archive for another recent discussion of this topic: http://lists.radiantcms.org/pipermail/radiant/2007-September/thread.html#6356 Good luck! Loren www.hellovenado.com On Nov 27, 2007, at 2:20 AM, Tõnu Runnel wrote: > Hi > > I didn't find an answer to my question through Google, maybe I didn't > know how to look. Anyway -- how do you make a multi-language website > with radiant? > > Is it so that you make your site structure under Radiant's "PAGES"-tab > like this: > > Home (redirects) > en (home) > Services > People > Contacts > de (home) > Dienste > Leute > Kontakte > > ... or is there a better practice? And if there isn't, how do you > redirect? Is there an "official" Radiant solution or I need the > language > redirect extension? > > Thanks! > Tõnu > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to Integrate Radiant To an Rails Application
I've recently also had good success creating widget outputs from my other Rails app and then have Radiant consume them via Net::HTTP and the backdoor plugin, it's a hack but may be a pattern I bother making a "Widgets" extension to facilitate in the future. On Nov 22, 2007, at 9:44 AM, Maged Makled wrote: > Gnana Prasad wrote: >> Hi All, >> >> I am trying to integrate radiant with rails application , >> I tried googling a lot .But could not find a way to my problem. >> It would be great help to me , if you could give me a suitable >> direction to integrate rails application with radiant.. >> >> >> >> Thanks in Advance >> Gnana Prasad > > try radiant extension rails support it is made for that purpose. It > will > allow you create a rails application with MVC that you are used to > with > rails along the radiant cms. You could find info about that > extension as > well as an example at > > http://code.google.com/p/radiant-rails-support/ > > > > Thanks > > Maged > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Asset Manager Extension patch for use with 0.6.4
Keith, The future plans sound good. I personally have to cast my vote for you keeping a backward compatible file system version around for a bit as I've got several sites currently using the extension and I doubt I'll move all the images to the db side in those cases. Either way, I've attached the patch for the current version to work with Shards. If you're comfortable tying it to that you'll see it's a very tidy way to go, probably easier than copying and hackifying the views anyway. Cheers, Loren On Nov 20, 2007, at 11:12 AM, Keith Bingman wrote: Hey Loren, nice to see that someone is using this. I have totally refactored this, now it is not compatible with the old version, mostly because I am caching the images and storing them in the database. This lets me store one size and resize as needed. I have also switched the tagging around to use has_many_polymorphs, which seems to be working quite nicely. While it doesn't run on Shards (yet?), it is running using facets- light, the previous system that Sean built into radiant for his own page_attachments extension. So it should run with Shards without too much trouble. My current plan is to make to versions, one database backed, with the nifty resizing and a backward compatible version (which I need for an old site I have with 200+ images...). Slowly, it looks like I may have some time, too. Thanks again for the patch. Keith On Nov 20, 2007, at 6:40 PM, Loren Johnson wrote: Attached is a patch to make the Asset Manager Extension work with the current Radiant 0.6.4 release. The only change is to app/views/ admin/page/edit.rhtml which is just a copy of the 0.6.4 edit.rhtml with the Asset manager stylesheet and bucket inserts. Also, Keith's most recent blog entry indicates that he may be refactoring this extension soon (http://keithbingman.com). Personally I would like to see this become a Shards extension as it seems that is quickly becoming the standard recipe for inserting into admin views. Keith -- if you're listening, what are your plans for your Asset Manager update? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Assets Extension diff for use with Shards
Finally, here is a diff for the Assets extension tested (in the loose sense of the term) to work with the Shards extension. The only note is to make sure you have Shards #1 in the extension load order. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Handling multiple languages
Peter, I'm glad this looks like something you can use. Let me know how it goes. The extension was developed for a client whose translated site has not yet been put into production so this extension is somewhat untested. It works and hopefully your purposes won't reveal any dark/ sharp corners. Good Luck, Loren On Oct 10, 2007, at 6:20 AM, Peter Berkenbosch wrote: > I guess I mist this when posted, but this is really cool. Thanks ! > > On 9/13/07, Loren Johnson <[EMAIL PROTECTED]> wrote: >> >> >> I'm a little late to the discussion, but here is the solution I >> recently implemented for a client based on similar needs: >> >> http://svn.fn-group.com/radiant_extensions/language_switch >> >> I think it may be useful as-is but at least should be worth >> referencing. There is some hackery involved with using the cookies to >> store the current language preference and a set of tags for allowing >> the user to switch. The default is the browser language...the README >> reads thus: >> >> = Language Switch >> >> This extension creates a set of tags and page routing which responds > > -- > met vriendelijke groet, > > Peter Berkenbosch > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Displaying a month calendar "grid" and using non-ical events?
Shawn, I have never tried to make a grid using my EventCalendar extension. I do think it's possible but might not be a lot of fun figuring out how and could necessitate adding one or two month grid display oriented tags (total days in month, etc). If I were you I'd tackle it as a new extension. I do plan on adding direct event entry to the extension in the near future, but whatever helpers you need to get the month grid and navigation controls it implies to work are things which you'd still have to add. The extension was originally built for this page: http:// www.diopa.org/calendars/master/all/month The extension can be found here: http://svn.fn-group.com/ radiant_extensions/event_calendar Good luck, Loren On Sep 27, 2007, at 11:40 PM, Shawn Oster wrote: > I've just finished my latest Radiant-based site (http:// > callpipecam.com) and > I'm onto my next one and have hit a snag. The new one needs an event > calendar that actually looks like a month-by-month calendar and the > current > iCal-based calendar extension seems to do a list of events vs. an > actual > classic calendar. Does anyone know if this is even possible with this > extension and perhaps someone would be kind enough to share a > sample if so? > I'd search the mailing list but the search page seems to be dead > right now. > I get a vague sense that it might have something to do with the > periods and > period properties but I'm not making the translation in my head > from that to > a standard month "grid". > > A related question is has anyone modified this extension to work > with a > local events table vs. having to pull from an iCal feed? While the > client > is OK with using Google Calendar they're not 100% happy with it and > would > really like the events to be local. I'm of mixed mind and this > isn't as > important but thought I'd ask. > > Thanks! > Shawn Oster > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 12,000 articles in a Radiant site?
Yes, this is all very good news. I'm quiet happy to not have to make any caching or lookup improvements and it makes all the more sense to base this project on Radiant. Daniel, thanks very much for explaining this and doing the original benchmarks. I hope that once this project is done it can serve as an example of this sort of performance in practice. As for page depth, the current content organization is pretty abnormal / chaotic, reminiscient of 12 years of static file maintenance. I have some 400 page nodes which will be 200+ pages down the tree, currently with around 400 pages at the root level. So for now, other than the file import routine, I'll focus my energies on a "SiteGrande" Admin interface extension which will, among other things: * Visually compress the page tree (restyle the current page tree getting dropping the page icons and the variation in font-size between node levels, reduce the row height, etc.) * Add an "Edit from this root" link which would filter the page view to that node inward with a "back" link of some sort * Search / Live Search capacity in some form Thanks much for the comments so far, Loren Ps. Anybody who wants work and has experience batch processing legacy HTML should contact me :) On Sep 14, 2007, at 7:24 AM, Sean Cribbs wrote: > See, this is why it's awesome to have a performance guru on the core > team. Thank you for clearing up some misunderstandings of mine. > > Loren, if we assume that 500,000 unique visitors in a month and every > one of them requested only 1 page, that would still only be 0.19 > requests per second. It would take each of them requesting 1000 pages > per visit to even reach the benchmark Daniel cites. So, I think > Daniel > may be right in the 100 req/sec vs. 600 req/sec debate. The only > issue > then is to make sure that any extensions you add or create don't slow > things down or make them too unstable. > > Like Daniel suggested, your issue may then be the admin UI, which will > take a long time to render if your structure is really flat. One > thing > we may do for Digital Pulp (even though their estimated site size is > around 300 pages) is to add a live-search box to the site map so pages > can be quickly found. > > Cheers! > > Sean > > Daniel Sheppard wrote: >> >> >>> I seem to remember this in another caching discussion: what about >>> response headers? From what I recall, browsers won't allow you >>> to use >>> meta tags for evey header, so simply caching the html won't >>> necessarily fill every need. >>> >>> Could the caching scheme be extended to store and transmit cached >>> headers as well? >>> >> >> The current system already does. If people start talking about >> handing >> off the caching to the web server instead, there's not really any way >> to do that without customising your web server to some extent. >> >> If somebody finds radiant's caching performance inadequate, the next >> logical step that I can see is to implement the caching as it >> currently >> functions in the webserver. >> >> That would either be in the form of an apache module or a custom >> handler >> for mongrel (I'd say the later would be the best first step). >> >> If you've got the sort of traffic where this matters to you (very few >> people will), your choices are: >> >> a) develop an apache module / mongrel handler to handle caching >> b) pay someone (me? I like money) to do that for you >> c) rethink your business model so that you have the money for a) >> or b) >> >> Dan. >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> >> > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 12,000 articles in a Radiant site?
Ok, so nobody said crazy... That's good. I guess there are three things that seem absolutely necessary to address then: 1. Entirely revisit Radiant's page caching -- possibly getting out of any proxy to ruby situation entirely to let Apache (or Nginx, or...) do their simple magic. Possibly simply using Radiant as a static site generator? 2. Depending on how the caching happens (static generation or not), implementing a core change to Page to store it's own full path and Page.find_by_url to remove the currently necessary recursion there. Sean -- why would we still need to keep it as a fall back? 3. New page admin interface So, this doesn't sound like a rewrite of Radiant yet, hence maybe I get something worthwhile by using Radiant as the starting point. Are there any changes to caching that we could consider for core which would also help make sense at this scale? Are there any changes to the Admin page interface ""? L On Sep 13, 2007, at 2:44 PM, Sean Cribbs wrote: > Now, I imagine one of the largest slowdowns on your site is going > to be > Page.find_by_url because it is recursive. Radiant could really be > sped > up by caching the URL in the database, which would reduce lookup time > for most pages, and having the recursive method as a fallback. If you > want, we can hash over the design of this optimization together > (perhaps > with John and Daniel) and apply it to the core. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] 12,000 articles in a Radiant site?
I've been enlisted to take a 12,000+ article site (static .html pages!) with 500k unique visitors a month and convert it to a dynamic site where the owner of the site can more readily flow advertising, among other things alongside the content. The HTML (not XHTML) is mostly all old bad stuff, the clean-up and conversion of which is a separate task and discussion entirely. My question for the other members of the core team and the community at large is: 1. Am I crazy to be considering Radiant as the starting point for this project? I know I will need to section-up and somewhat re-invent the admin page tree, at minimum, but despite the size and popularity of the site, there are not a lot of unique CMS features needed. It's definitely an option to go custom from ground-up and their may be just enough in their budget to accommodate the custom route, however because of the unique situation of this client (the site is soon to be sold) time is of the essence and for this reason starting with Radiant could be a valuable jump start. The questions in my mind now are about caching and the core performance of Radiant under what could be significant load. I don't have peak number of pages served per second or minute right now, but will have those numbers shortly. 2. Is there any precedence for such a thing. I seem to remember a discussion a while back about relative site size and thought I remembered seeing that someone is managing a 1-2k page site in it currently. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Handling multiple languages
I'm a little late to the discussion, but here is the solution I recently implemented for a client based on similar needs: http://svn.fn-group.com/radiant_extensions/language_switch I think it may be useful as-is but at least should be worth referencing. There is some hackery involved with using the cookies to store the current language preference and a set of tags for allowing the user to switch. The default is the browser language...the README reads thus: = Language Switch This extension creates a set of tags and page routing which responds to a cookie stored language variable that is settable and resettable through the "language" query parameters (e.g. http://yoursite.com/your_page?language=en). When this parameter isn't present the language selected will be based upon the current cookie value for language, or if this value is also blank then the default acceptable languages in the client's browser will be responded to. = Full text sample/text code (no, there is no Bulgarian sample content... that's to show that the default work :) Language Switcher English | Spanish | French | German | Bulgarian | Reset Content Español Diez soldados estadounidenses murieron a causa de bombas en carreteras y al estrellarse un helicóptero en Irak, mientras cinco británicos fueron secuestrados en el Ministerio de Hacienda iraquí, dijeron el martes las autoridades. Français Ces dernières semaines, le Brésil s’est d’ailleurs souvenu de la répression qui avait enrayé une vague de violence, il y a un an à Sao Paulo, avec un très lourd bilan : 493 morts en à peine six jours. Entre les 12 et 19 mai 2006, le Premier commando de la capitale (PCC), l’un des gangs mafieux les plus puissants d’Amérique latine, avait orchestré une série d’attaques contre les forces de l’ordre, semant la terreur parmi les 11 millions d’habitants de la ville. Deutsche Die Innenminister von Bund und Laendern beraten heute und morgen ueber den Poli zeieinsatz waehrend des G8-Gipfels in der kommenden Woche in Heiligendamm. Bis zu 16.400 Polizisten sollen waehrend des Treffens der Staats- und Regie rungschefs der fuehrenden Industriena tionen zum Einsatz kommen. Wie nah Glo balisierungsgegner dem Tagungsort kom men duerfen, ist noch unklar. Gestern wurde der zwoelf Kilometer lange Zaun um das Gelaende geschlossen. Fuer eine Woche duerfen nur die Bewohner und besonders Berechtigte in das Gebiet. English (default) Is new software a key component to growth or essential to your new business idea? Rapid prototyping and constant evaluation can insure you only build exactly what need; nothing more, nothing less. Browser Languages Thanks, Loren Johnson www.hellovenado.com On Sep 11, 2007, at 2:29 AM, Aitor Garay-Romero wrote: >For this idea we also need "parts" for layouts and snippets, > since they > must be translated too. > >/AITOR > > On 9/10/07, Sylvestre Mergulhão <[EMAIL PROTECTED]> wrote: >> >> On 9/10/07, Aitor Garay-Romero <[EMAIL PROTECTED]> wrote: >> >>> - define different page parts for the language versions. For >> example, >>> have the parts "body_en", "body_fr" and "body_es". Or just "body", >> "fr", >>> "es". They could be "special parts" or not. >> >> I agree with this, some weeks ago I spent some time thinking about >> it. >> >> The dafult language could be the browsers one, or other after >> selected >> by the user. >> >> -- >> Sylvestre Mergulhão - Free Software Development >> - >> -- >> http://mergulhao.info >> http://www.euemeu.com >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Event Calendar extension : which url?
Joel, > 1.- which of these urls should I set in the Admin -> Event > calendars - my_calendar (I suspect the webcal://)? Whatever address spits out a .ics file is correct, however, i suspect the "webcal://" prefix is going to cause Ruby net/http to hiccup. Have you tried: http://ical.mac.com//.ics As long as .Mac allows that, it should work. > 2.- should I change something else in configuration files or any > calendar document? As long as you went through the steps in the README installing the VPIM gem and creating / setting the requisite ical directory under public then you should be good to go. Good luck, let me know how it goes. Feel free to contact me directly, Loren AIM: NL7XF ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Header Image
I'm not sure why what you describe doesn't work, but you might consider using a CSS content part and just override the header CSS there. You do this by placing within a block in the header of your document below any other CSS. . . Loren On Jul 17, 2007, at 9:22 AM, Mark Fischer wrote: > Has anyone found a way to work with a CSS background image where it > can be inherited site wide, unless overwritten. I am using the > page_attachment extension, created a content part named image_header, > where I only have the URL code for the header image for that page. I > then pull that into the CSS file. In theory, I was hoping that every > page would inherit the home page's URL (which it does), however, when > I try and make a sub section header change, it does not take. Does > anyone have any other ideas or know why this might be? I need the > image to be in the CSS for formatting reasons. Otherwise it would be > downright easy. > -Mark > > > > > > > On Jul 17, 2007, at 8:01 AM, Sean Cribbs wrote: > >> Michael, >> >> No, but I did something similar for KCKCC with the LDAP extension. >> All >> contact information was stored in the campus-wide LDAP directory. >> >> Sean >> >> Michael Pyschny wrote: >>> Hello Radiant Developers >>> >>> Has somebody already written or heard of a contact data extension >>> with >>> all the wonderful (required) tags? >>> >>> Cheers >>> Michael >>> ___ >>> Radiant mailing list >>> Post: Radiant@lists.radiantcms.org >>> Search: http://radiantcms.org/mailing-list/search/ >>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >>> >>> >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] contact data extension
Michael, I've written a "Business Directory" extension which is used here: http://www.diopa.org/church-finder. It's not what you're looking for exactly but it might be a useful example or starting point. You can check it out here: http://svn.fn-group.com/radiant_extensions/directory/trunk (you might also look at the NHBA branch, there may be a more helpful stuff there) Good luck, Loren On Jul 17, 2007, at 12:17 AM, Michael Pyschny wrote: > Hello Radiant Developers > > Has somebody already written or heard of a contact data extension with > all the wonderful (required) tags? > > Cheers > Michael > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.2 - Jewel Carver Release (Minor Update)
>> a separate announcement list for new releases, updates and other >> "official" information. I think this is a great idea. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] ISO Bao Tran
Same here, I got an invite from him. I'm easy, I just accepted. :-/ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Event Calendar (iCal) Extension
For anyone who has tried using the Event Calendar extension since I announced it a few days ago please run and svn update or check it out again. I caught an important bug fix today which was causing any page with the Event Calendar type to be the default when the url was unknown. Also, I've cleaned-up the tag descriptions significantly. If you're interested in trying out the extension it can be found here. The README includes everything you'll need to know to get it going: http://svn.fn-group.com/radiant_extensions/event_calendar/ Your questions or comments are welcome. Thanks, Loren ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RadiantOnRails extension
Jed, Thanks for checking. I actually gave the project several hours this week and made some progress. I had a long conversation with Sean and reviewed with him the issues I've ran into so far and the changes big and small that may be required to make it work. Feel free to email me directly and I'll fill you in and see if we might work together on any part of it. I'm not really ready to publish my "findings" to the entire list quiet yet, though I'd like to do just that shortly... Loren [EMAIL PROTECTED] On Jun 8, 2007, at 11:17 AM, Jed Hurt wrote: > Loren Johnson wrote: >> I'll put some more time into playing with Radiant installed as a >> plugin this week and see what trouble I find. Looks like you've >> gotten a good start on the right questions for me Sean and Matt. I'll >> report back on how far I get later this week. >> >> Loren > > Any luck, Loren? > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] events calendar extension
I don't know what's causing that but this could be related, and is a very important note (which I've added to my README just now). You need to install a gem called VPIM in order for the calendar to work. gem install vpim Let me know if this fixes it for you, Loren On Jun 8, 2007, at 2:51 PM, John Furfey wrote: > Thanks Loren, > > Getting the following error when trying to add a new calendar: > > LoadError in CalendarsController#new > > Expected /Users/jfurfey/Sites/wfl/vendor/extensions/event_calendar/ > app/models/ical.rb to define Ical > > RAILS_ROOT: script/../config/.. > > > > On Jun 8, 2007, at 1:33 PM, Loren Johnson wrote: > >> >> Event Calendar (iCal) extension >> >> http://svn.fn-group.com/radiant_extensions/event_calendar >> >> It's pretty much ready to go as-is, I've recently made several clean- >> ups to it to make it simpler to install and more cleanly designed in >> terms of objects. >> >> We are using this on 4 sites currently and in each case our customer >> is happy to be entering stuff using Google Calendars (which supplies >> us an iCal feed address). The big advantage of this approach is that >> you can have several authors feeding individual calendars up to the >> website without having to support them as Radiant users. >> >> However, it would be relatively simple to adapt it to handle both the >> current iCal subscriptions way of populating events alongside manual >> direct event entry and I won't be surprised if I'll need to add this >> ability at some later point. >> >> The calendar operates either as an on-page event list queried via >> tag attributes (all the tags are setup as global) or >> as a dedicated virtual page which uses the path parameters below it's >> own root to determine the period and set of events you wish to >> display. >> >> A few of disclaimers : >> >> 1. Read the README. You'll need to run "rake db:migrate:extensions" >> and create a directory under public to store the ical files that get >> pulled in. >> >> 2. I always setup a script/runner cron job to keep the calendars >> refreshed from the subscriptions every hour. There are no >> instructions for this in the README but it's simply done if you have >> linux admin chops. >> >> 3. The documentation under the "Help!" link may not be up to date, >> also the tag documentation is there but the formatting isn't very >> nice. I'll be fixing this shortly. >> >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > John Furfey > Digital Systems and Services Coordinator > MBLWHOI Library > Woods Hole MA 02543 USA > PHONE: 508-289-7435 > EMAIL: [EMAIL PROTECTED] > http://www.mblwhoilibrary.org > > > > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] events calendar extension
Event Calendar (iCal) extension http://svn.fn-group.com/radiant_extensions/event_calendar It's pretty much ready to go as-is, I've recently made several clean- ups to it to make it simpler to install and more cleanly designed in terms of objects. We are using this on 4 sites currently and in each case our customer is happy to be entering stuff using Google Calendars (which supplies us an iCal feed address). The big advantage of this approach is that you can have several authors feeding individual calendars up to the website without having to support them as Radiant users. However, it would be relatively simple to adapt it to handle both the current iCal subscriptions way of populating events alongside manual direct event entry and I won't be surprised if I'll need to add this ability at some later point. The calendar operates either as an on-page event list queried via tag attributes (all the tags are setup as global) or as a dedicated virtual page which uses the path parameters below it's own root to determine the period and set of events you wish to display. A few of disclaimers : 1. Read the README. You'll need to run "rake db:migrate:extensions" and create a directory under public to store the ical files that get pulled in. 2. I always setup a script/runner cron job to keep the calendars refreshed from the subscriptions every hour. There are no instructions for this in the README but it's simply done if you have linux admin chops. 3. The documentation under the "Help!" link may not be up to date, also the tag documentation is there but the formatting isn't very nice. I'll be fixing this shortly. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RadiantOnRails extension
Two things from my perspective with regard to what's been said so far: 1. In my understanding the standard plugin architecture as suggested by John gives us dead-simple Radiant plugin-ability to any forming or existing Rails app. This is probably the primary objective for my cases despite my whining about wanting to reuse my layouts, that and calling snippets / page parts in Rails views is a second priority for me. 2. I don't think we have to make the choice between "tight integration" of Radiant content into Rails views and simplicity of installation. They are different issues both with their own significant challenges, so it doesn't make sense to try and achieve both in the same release. So, I think addressing the plugin architecture issues first is good. From that basis we can then work- out integration issues (snippet helpers, layout reuse, etc.) I figure if we go that route we'll have more people using Radiant as a component of a larger Rails app sooner and therefore more input, effort and ideas being contributed to making the content integration stuff work as well and completely as possible. 3. I've used Comatose in a few projects and each of those cases I'd rather have used a plugged-in version of Radiant instead. It's a great project but I'd sure like to be leveraging my Radiant work and skills when I integrate. This also makes the transition with my clients from "we'll start with a simple content site" to "now let's build a custom app" less expense and painful. This is a common enough scenario for me. I'll put some more time into playing with Radiant installed as a plugin this week and see what trouble I find. Looks like you've gotten a good start on the right questions for me Sean and Matt. I'll report back on how far I get later this week. Loren On Jun 2, 2007, at 10:16 AM, Jed Hurt wrote: > Sean Cribbs wrote: >> I think Matt and Loren's cases are more about a tighter integration >> between Radiant and the host application, including reusing Radiant >> pages, layouts, and snippets in Rails. If you just want to add some >> content management to an existing Rails application, there's >> always the >> Comatose plugin, which has been around for a while and is probably >> better suited to that scenario. >> >> Sean > > I spent a little bit of time with Comatose this week. It's a cool > project, but a little bit too basic for my needs. I think we would > agree > that Radiant is—in many ways—an unparalleled CMS. > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Current tab in navigation
No they're not ;) On Jun 1, 2007, at 11:28 AM, Adam Williams wrote: > On Jun 1, 2007, at 1:21 PM, Loren Johnson wrote: > >>>> Also note that if you're NOT using >>>> 0.6.1 (you should be :) then you'll find that the url separator >>>> character is ... not a pipe (|). > > Double negatives are hard outside of code, too, I see. > > Ha! adam > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant Core Dev: Page Controller
Jacob,
Your patch adding the level tag in is quiet tidy. In
my own Swiss Army tag library extension which I dump into nearly
every Radiant site I put up I have a similar tag . Your version is cleaner. My tag gets use in combined with
an tag which returns the current depth/level in the tree.
Speaking to the bigger picture of core changes to the
tag I think that Sean is right to suggest a more drastic refactoring
of the tag is in order. If I understand right Sean's been playing
with some of these more drastic revisions himself.
Sean, do I have you wrong? Can we have a peek?
Loren
On Jun 1, 2007, at 9:30 AM, Jacob Burkhart wrote:
> Thanks Sean.
>
> Looks like posting on the mailing list gets a much faster reply that
> posting on Trac.
>
> So then a follow-up question would be, what's wrong with these
> patches, why havn't they been replied-to?
> http://dev.radiantcms.org/radiant/ticket/504
> http://dev.radiantcms.org/radiant/ticket/502
>
> Jacob
>
> On 6/1/07, Sean Cribbs <[EMAIL PROTECTED]> wrote:
>> We would love a patch, of course! This will also help in a future
>> refactoring toward REST which is on the horizon.
>>
>> Sean
>>
>> Jacob Burkhart wrote:
>>> Hey,
>>>
>>> I just read this post:
>>> http://www.therailsway.com/2007/6/1/railsconf-recap-skinny-
>>> controllers
>>>
>>> And it made me think immediately of the old
>>> handle_new_or_edit_post in
>>> page_controller
>>> http://dev.radiantcms.org/radiant/browser/trunk/radiant/app/
>>> controllers/admin/page_controller.rb?rev=57
>>>
>>>
>>> But now I go and look at the latest version, and I see it's been
>>> cleaned up a bit, and there a new AbstractModelController seperating
>>> the logic a bit.
>>>
>>> http://dev.radiantcms.org/radiant/browser/trunk/radiant/app/
>>> controllers/admin/page_controller.rb
>>> and
>>> http://dev.radiantcms.org/radiant/browser/trunk/radiant/app/
>>> controllers/admin/abstract_model_controller.rb
>>>
>>>
>>> But still... you have a lot of logic in the controllers. And a
>>> lot of
>>> that logic, if moved to the model, would be a lot easier to override
>>> and modify in extensions.
>>>
>>> For instance, I'd like to see all the part-creating/arranging logic
>>> moved into the Page model.
>>>
>>> 96 parts_to_update = {}
>>> 97 (params[:part]||{}).each {|k,v| parts_to_update[v
>>> [:name]] = v }
>>> 98
>>> 99 parts_to_remove = []
>>> 100 @page.parts.each do |part|
>>> 101 if(attrs = parts_to_update.delete(part.name))
>>> 102 part.attributes = part.attributes.merge(attrs)
>>> 103 else
>>> 104 parts_to_remove << part
>>> 105 end
>>> 106 end
>>> 107 parts_to_update.values.each do |attrs|
>>> 108 @page.parts.build(attrs)
>>> 109 end
>>> 110 if result = @page.save
>>> 111 new_parts = @page.parts - parts_to_remove
>>> 112 new_parts.each { |part| part.save }
>>> 113 @page.parts = new_parts
>>> 114 end
>>>
>>> So, my question to the core devs is... how open would you be to
>>> patch
>>> coming from me, that addresses some of these things.
>>>
>>> I must admit, my agenda is based on making my own extensions more
>>> elegantly integrated with Radiant. But I'm hoping to appeal to any
>>> skinny-controller philosophy-followers as well.
>>>
>>> thoughts?
>>>
>>> Jacob
>>> ___
>>> Radiant mailing list
>>> Post: Radiant@lists.radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>>>
>>
>> ___
>> Radiant mailing list
>> Post: Radiant@lists.radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post: Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Current tab in navigation
But.. but... the point is to YES USE THE PIPE IN 0.6.1 earlier versions NO It's getting funnier all the time ;) On Jun 1, 2007, at 11:05 AM, Jonathan Métillon wrote: > On 6/1/07, Loren Johnson <[EMAIL PROTECTED]> wrote: >> Jonathan, >> >> Take a look at the documentation for the > 0.6.1 (you should be :) then you'll find that the url separator >> character is a semi-colon (;) not a pipe (|). >> >> Good luck > > Again, that's just what I needed. And yes, I run 0.6.1, and I will NOT > not use the pipe :-p > > Radiant and its community rock. Love it. > > Thanks a lot. > > J. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Current tab in navigation
But that's what I said ;) On Jun 1, 2007, at 7:04 AM, John W. Long wrote: > Loren Johnson wrote: >> "Available Tags" reference link. Also note that if you're NOT using >> 0.6.1 (you should be :) then you'll find that the url separator >> character is a semi-colon (;) not a pipe (|). > > Actually, on 0.6.1 it's a pipe not a simi-colon. > > -- > John Long > http://wiseheartdesign.com > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Current tab in navigation
Jonathan, Take a look at the documentation for the Renders a list of links specified in the urls attribute according to three states: * normal specifies the normal state for the link * here specifies the state of the link when the url matches the current page’s URL * selected specifies the state of the link when the current page matches is a child of the specified url The between tag specifies what sould be inserted in between each of the links. Usage: | On Jun 1, 2007, at 2:29 AM, Jonathan Métillon wrote: > Hi, > > I have a snippet where I store my navigation bar. It's a bullet list, > and I use CSS to make it looks like a bar, with each link as a button. > > Is there a way to have this bar dynamic, where the correct button > while be attached a "current" CSS class appropriately? > > Thank you all. > > J. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RadiantOnRails extension
You're absolutely right, sorry I hadn't looked closely enough. You could gem install Radiant and generate an instance and then merge the necessary bits from the environment.rb it generates into your existing app. If I get a chance I'll try and determine what those necessary bits are later today and email back what I learn. Loren On Jun 1, 2007, at 2:21 AM, Meekish wrote: > Loren Johnson wrote: >> Read through the Readme in the extension now posted on RubyForge (see >> Matt's original post for address, etc) and you'll find that the >> "installation" is very straight forward and will be the same whether >> it's with a fresh Rails app or an existing one. >> >> Give it a shot... > > I read the README before posting, but it seemed to me like it was > explaining how to modify an existing Radiant app, rather than an > existing Rails app: > > == > 1. Edit RAILS_ROOT/config/environment.rb and change the following line > > config.view_path = File.join(RADIANT_ROOT, 'app', 'views') > > to > > config.view_paths << File.join(RAILS_ROOT, 'app', 'views') > config.view_paths << File.join(RADIANT_ROOT, 'app', 'views') > == > > The environment.rb file (RAILS_ROOT/config/environment.rb) in a stock > Rails app wouldn't have any mention of 'RADIANT_ROOT' > > Am I misunderstanding the directions? > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RadiantOnRails extension
Read through the Readme in the extension now posted on RubyForge (see Matt's original post for address, etc) and you'll find that the "installation" is very straight forward and will be the same whether it's with a fresh Rails app or an existing one. Give it a shot... On May 31, 2007, at 10:56 PM, Meekish wrote: > Matt Parrish wrote: >> The RadiantOnRails extension is now live on RubyForge at http:// >> www.rubyforge.org/projects/radiantonrails. This extension allows for >> Radiant to co-exist with a Rails application. You can checkout the >> code with the following command: >> >> svn checkout svn://rubyforge.org/var/svn/radiantonrails/trunk >> >> Or, to install the extension, follow the instructions from the >> Radiant website (http://dev.radiantcms.org/radiant/wiki/Extensions) >> using the name 'radiant_on_rails' for the extension_name. >> >> Matt Parrish >> http://www.pearware.org > > I already have a Rails app and would like to retrofit it with Radiant > using this extension. How would the process differ from starting > with a > Radiant app and building it out into a Rails app? > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant integration with another Rails app?
Did you consider wrapping it up as a plugin? Off the top of my head that seems like it could be the cleanest way to go, but I say that without seeing how you have it setup now. What is a basic sketch of the install process as it is? Some way to embed in a straight Rails app is in my view a key piece of the puzzle that is Radiant's future. I have frequent applications now that would use Radiant in this embedded way if an easy and unobtrusive way to do so was already established. So as for going in the Radiant SVN I think it belongs there and I'm willing to pitch-in on the development effort if you want/need that. There are "in development" pieces in there already, so I think it's a fine place for it. -- But that just "like my opinion, dude". :) Loren On May 30, 2007, at 10:54 AM, Matt Parrish wrote: > John, > > Are you suggesting that I develop from the Radiant SVN repository? > Or are you saying that you'd be happy to host a copy of stable > releases? > > Also, the name I settled on was Radiant on Rails and it is a Radiant > Extension. > > Thanks, > Matt > > On May 30, 2007, at 11:16 AM, John W. Long wrote: > >> Matt Parrish wrote: >>> I'm working right now to get a project created on RubyForge and >>> trying to come up with a reasonable name for the extension. How >>> does >>> 'RadiantFromRails' sound? >>> >>> I'm up for getting together with you and Sean on IRC. I'd really >>> like to hear Sean's thoughts about how he might approach the >>> issue of >>> layouts as I haven't really spent any time thinking about the >>> implementation yet. >> >> If you get a plugin going, I'd be happy for it to live in the Radiant >> SVN repository. >> >> -- >> John Long >> http://wiseheartdesign.com >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] url regexp question
Francesco, It will help if you can post the code snippet with the nested http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant integration with another Rails app?
Matt, RadiantFromRails sounds good to me. Let me know when you get it set up, I'm anxious to give it a spin. Once I am sitting down to do that I'll feed my experience back to you on how it goes. Do you have a client use case for the integration? I think you said you did, but it'd be good to know your requirements as it seems that a completely general purpose integration method could be a stretch... Feel free to AIM, call or email me if you'd like to bat any part of the implementation details around with someone. Loren ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Internationalization examples
I'm being hired to write a new Extension for handling some basic site internationalization needs (admin text won't be addressed). We've went over a couple of options and for managability we've decided on creating separate default page parts for each language and then overriding find_page_by_url in our extension to select the right content to render based upon the browser language type. I talked with John and Sean both about this approach while at RailsConf and they concurred that it would work fine, but it's not going to deliver the right pages with caching on. For the site I'm helping on having caching off won't be detrimental, but I probably could also override some of the Radiant caching stuff within the extension and have it also working. John implemented Ruby Language site with internationalization using multiple roots under the root (home/english, home/spanish, etc.) This approach is cleaner in a couple of ways but is less manageable (depending on your use case--if you have different editors for each language it would be more manageable). Has anybody already done a similar thing? Any other approaches worth considering? Does anybody wish to pitch-in on the effort? We will be releasing an open sourced version of the resulting extension when I'm done with it later this week. Thanks, Loren www.hellovenado.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant integration with another Rails app?
Hey Matt, Funny -- I knew I talked to someone about this at RailsConf and I just couldn't remember who... Now I remember our discussion well. Yes, I'd very much like to help out in whatever way I can. I really want to see this happen and end-up with something that makes the integration dead simple to accomplish. Love to see what you've got so far and talk more. It'd be especially nice to see how you're using it in your existing app. I still have your card here, I'll give you a shout later today or tomorrow to talk approaches and see in what way I might be able to pitch-in, etc. Maybe it'd be nice to set a date and time for you, Sean and myself (and anyone else interested) to meet-up in #radiantcms IRC on this topic... Glad there is something already happening on this front! Loren On May 28, 2007, at 10:13 AM, Matt Parrish wrote: > Hi Loren, > > Nice to talk to you again! ;) > > I'm working on the same thing right now. I currently have a Radiant > extension that allows Radiant to live in /vendor while having a Rails > app at it's current location with only a slight modification required > for config/routes.rb to work properly. > > It also has the ability to insert a snippet using a helper as you > suggested, although I don't know how robust it is depending on what > radius tags are in that snippet. And yes, as you mentioned, it > creates a Page object to do this. > > I'm also very interested in allowing Rails pages to leverage Radiant > layouts, and that is the next thing I plan to work on. Let me know > if you're interested in seeing the extension I have so far. I plan > on creating a Rubyforge project for it, but I haven't gotten around > to that yet. Perhaps we can work together to get this done. I also > think that Sean was working on the layout problem, too. So maybe he > already has made some progress in that area. > > Thanks, > Matt > > > On May 28, 2007, at 12:03 PM, Loren Johnson wrote: > >> >> Does anyone have a successful example out there of putting Radiant in >> the vendor directory of an existing full-scale Rails app and having >> it play nicely? >> >> I've tried unsuccessfully in the past, however with the final polish >> on 0.6 (and now 0.61) I'm ready to give it another shot. >> >> I have an app I would like to do this with that I'll be working on in >> a week or two. >> >> For my use here are the two main issues that I know of are: >> >> 1. Routes... I can load my app's routes first I essentially override >> everything but the final Radiant default "page not found" route. >> >> 2. Rendering of snippets or page parts with Radius tags in them >> straight in to my Rails app view... In particular, I imagine making a >> helper in my app for calling the Radiant content. Is there a way to >> render the snippet or part directly without creating a new >> PageContext every time it goes to render (I'd be doing this all >> through a Rails helper method I imagine...) >> >> 3. Less important to me, but interesting... the reuse of Layouts. Can >> I pull a layout as a Rails layout, ERB render and then do a final >> Radius render? Anyone tried this? >> >> Anybody doing any of this yet? >> >> Thanks, >> >> Loren >> www.hellovenado.com >> >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant integration with another Rails app?
Does anyone have a successful example out there of putting Radiant in the vendor directory of an existing full-scale Rails app and having it play nicely? I've tried unsuccessfully in the past, however with the final polish on 0.6 (and now 0.61) I'm ready to give it another shot. I have an app I would like to do this with that I'll be working on in a week or two. For my use here are the two main issues that I know of are: 1. Routes... I can load my app's routes first I essentially override everything but the final Radiant default "page not found" route. 2. Rendering of snippets or page parts with Radius tags in them straight in to my Rails app view... In particular, I imagine making a helper in my app for calling the Radiant content. Is there a way to render the snippet or part directly without creating a new PageContext every time it goes to render (I'd be doing this all through a Rails helper method I imagine...) 3. Less important to me, but interesting... the reuse of Layouts. Can I pull a layout as a Rails layout, ERB render and then do a final Radius render? Anyone tried this? Anybody doing any of this yet? Thanks, Loren www.hellovenado.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] extension question
Bill, I've written a Event Calendar extension which pulls events from an ical subscription and populates them into calendars which each have an associated "category" and "slug". I then access the different calendars through a virtual page root node like this: http:// yoursite.com/calendar/category/slug (or more concretely http:// yoursite.com/main/youth). This is very similar to how the ArchivePage behavior in the core code works. Take a look at that if you haven't already. I'm releasing a tidied-up version of this EventCalendar extension here on the list within a day or two so you can use it as another example then... Actually though, pretty much everything you need is here between the EventCalendar page type which overrides find_by_url to, essentially shutting-down further Radiant processing of child pages, and the I'm developing another radiant extension that I basically want to > be able to > display a catalog of categories, sub-categories, and items with. I > don't > want to have to create a page for every one of those, I want it to be > dynamic based on what someone can set up through an admin > interface. I also > don't want to lose the power of radiant and its tagging system > (like not > being able to use r:title, r:snippet, r:content etc. etc.) by > having the > extension be its own application outside of the CMS. Another > requirement is > the ability to have pretty urls like /catalog/department/shoes/ > instead of > having query string variables muddying things up. > > Has anyone tried to do something like this and had some success > that they > could share? I've given this a bit of thought and haven't really > come up > with a solution I like. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RailsConf MeetUp
For what it's worth I can vouch for the Doug Fir, the best of Portland hip. It's a fun place and not a long ways from the conference center, though a drive. That's my vote. We'll all have lots of quiet rooms later in the conference so I'm all forward a little commotion to kick things off. Look forward to putting faces to names. Loren On Mar 21, 2007, at 5:01 PM, Michael Jones wrote: > I live in Portland and look forward to meeting folks. > > The Doug Fir is always a fun place to meet, it's a bar on Burnside and > close/easy to find. > > Would that work or are we looking for a quite place? > ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RailsConf MeetUp
It's my home town, though I haven't lived there for awhile... I could identify a place if nobody else has a really good idea? On Mar 21, 2007, at 3:13 PM, Sean Cribbs wrote: > I created the gathering. I wish there were an easy way to RSVP for > them... until then we can get an informal count from the list. I'm > also not familiar with Portland; any recommendations for where to > meet? > > Sean > > On 3/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> I saw there's a RadiantCMS user meetup set for 7PM on Thursday of >> RailsConf 2007. I'd be very interested in meeting up with the rest >> of you. >> >> Any idea on how many might show? >> >> Chris >> >> ___ >> Radiant mailing list >> Post: Radiant@lists.radiantcms.org >> Search: http://radiantcms.org/mailing-list/search/ >> Site: http://lists.radiantcms.org/mailman/listinfo/radiant >> > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RailsConf MeetUp
+1 I'll be there... Was just about to ask if such a thing existed. On Mar 21, 2007, at 3:10 PM, [EMAIL PROTECTED] wrote: > I saw there's a RadiantCMS user meetup set for 7PM on Thursday of > RailsConf 2007. I'd be very interested in meeting up with the rest > of you. > > Any idea on how many might show? > > Chris > > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] ANN: Reordering of Pages
Hoorah! hoorah! Thank you, thank you and thank you! to John and Adam. This is going to make several things better for our particular use of Radiant. Loren ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Adding methods to Page from an extension
> class Page < ActiveRecord::Base Should be: YourPageClassName < Page On Feb 3, 2007, at 4:10 PM, Jacob Burkhart wrote: > Hey I feel like I'm missing something obvious, > > I created an extension that adds some columns to the pages table, and > now I want to add some methods to the Page class. > > I put this at the bottom of my Extension class > > class Page < ActiveRecord::Base > > def test_new_method > "hi" > end > > end > > > And now I'm getting errors like: > > undefined method `children' for # > undefined method `parts' for # > > > Which leads me to believe that my version of Page is being loaded, and > the original version is not. > > How do I get them both to load? what's really going on here? > > > > Also, can somebody tell why "logger" is not defined from my Extension > class > How can I access the logger? > > > thanks, > Jacob > > -- > Posted via http://www.ruby-forum.com/. > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mailer Extension, again
Finally, I manually re-arranged the plain and HTML parts in a test message and opened it up directly in Mac Mail. Yep... that definitely fixes it. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mailer Extension, again
Thanks and np, I forget, "this is the day" :) Honestly I don't think changing the order of the parts will fix my problem anyway, though it does look like it should happen anyway. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mailer Extension, again
Oops, actually easier said then done... I'm checking out the Mailer Extension via svn:externals to Mental and will have to detach from the mothership to test this which I'll do depending on your answer. The change of ordering that parts is a really straight forward swap at lines 256-262 of mailer_page.rb I don't know if it'll solve my problem but if it needs to happen anyway... When do you think you'll get to that? L ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mailer Extension, again
That makes sense however it still doesn't answer why the html version isn't being preferred by Mac Mail (not checked with any other clients yet). . . I'll rearrange the order of the parts and re-send to see that magically fixes it. L On Feb 3, 2007, at 9:43 AM, Sean Cribbs wrote: Loren, From those references it seems I have it backwards; the plaintext version should go first. But you're right, it doesn't explain why your 'email' or 'email_plain' doesn't render. Sean On 2/3/07, Loren Johnson <[EMAIL PROTECTED]> wrote: Sean, Yeah since I wrote that message I'd done some looking around: http://www.wilsonweb.com/wmt5/html-email-multi.htm http://www.freesoft.org/CIE/RFC/1521/18.htm And will look into it more this afternooon. I need to follow through the code and my page to see why my the plain text version is blank, as on first glance in the code it looks like it'd have a default list of the fields at least. Then I'll look into why Mac Mail isn't choosing the HTML version as it did in a multipart/mixed message... If I see any reason to change things in the code I'll write-back with my suggestion. Right now as far as I can see the raw multipart/ alternative message looks correct except the missing plain/text content. Thanks, Loren On Feb 3, 2007, at 7:01 AM, Sean Cribbs wrote: > Loren, > > That was my change. Back last March when I was developing a Rails > application that needed to send email, I dissected various > gracefully-degrading emails that I got in my inbox. I found that, for > most email clients, the multipart/alternative type with a text/ > plain and > a text/html part seemed to be the most compatible. I'm willing to > change that assumption, however, and the code, if you have a better > solution. I searched a lot and didn't find any reliable reference for > how they should be formatted, so I reverse-engineered it. > > Sean > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mailer Extension, again
Sean, Yeah since I wrote that message I'd done some looking around: http://www.wilsonweb.com/wmt5/html-email-multi.htm http://www.freesoft.org/CIE/RFC/1521/18.htm And will look into it more this afternooon. I need to follow through the code and my page to see why my the plain text version is blank, as on first glance in the code it looks like it'd have a default list of the fields at least. Then I'll look into why Mac Mail isn't choosing the HTML version as it did in a multipart/mixed message... If I see any reason to change things in the code I'll write-back with my suggestion. Right now as far as I can see the raw multipart/ alternative message looks correct except the missing plain/text content. Thanks, Loren On Feb 3, 2007, at 7:01 AM, Sean Cribbs wrote: > Loren, > > That was my change. Back last March when I was developing a Rails > application that needed to send email, I dissected various > gracefully-degrading emails that I got in my inbox. I found that, for > most email clients, the multipart/alternative type with a text/ > plain and > a text/html part seemed to be the most compatible. I'm willing to > change that assumption, however, and the code, if you have a better > solution. I searched a lot and didn't find any reliable reference for > how they should be formatted, so I reverse-engineered it. > > Sean > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Mailer Extension, again
I've been actively ignoring all the traffic about recent problems with the Mailer Extension until today. I had done preliminary testing and nothing was throwing errors so I figured all was well before I released our converted site live. Now I've got a real and configured mail server behind the site to test against I discovered a problem. Though my forms return "email_html" page parts and don't also have an "email" part or anything like that, the email that I get in response is encapsulated in "text/plain" and won't display at all in my email client unless I got to view Raw Source of message. The content of these forms and output email_html parts have not been touched through this conversion. The below two emails are generated by each version of the Mailer thing respectively -- Mailer Extension email in Pastie which shows-up as a blank message in my email client unless I look at the Raw Content of the message then I see this (* note line 41): http://pastie.caboo.se/37563 Line 41: Content-Type: multipart/alternative; boundary=mimepart_45c3ba4744994_eb9..fdbb90756334 From the older Email Behavior which does display as expected in my email client (* note line 33): http://pastie.caboo.se/37567 Line 33: Content-Type: multipart/mixed; boundary=mimepart_4581bf35ab0e3_657..fdbbd21a01862 I started digging into the Mailer Extension code but thought I'd ask around to see if anyone knows enough about email formats or the code in the extension to give me a hand. This sure seems like a bug to me. Any help is appreciated. Yey! We're finally have everything converted-over to mental (just in- time to miss the first RC ;) Loren Johnson www.fn-group.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant::Config
Amen and amen. Scaffold-up an extension for managing config values and call it good until this next release is out then it can be thought about again once a larger set of Extensions (and hence real requirements) start to appear. I'm excited to just ad a config tab right into my Calendar extension which filters on it's config parameters only. That'll be great. > Sometimes it is appropriate to let things go for a while when you > aren't > sure about the best approach. > > It would be trivial to implement an editing interface with an > extension. > > -- > John Long ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] svn:externals, capistrano and extensions
Looks like http://radiantcms.org/blog/2007/01/23/how-to-getting-mental/ answers my question. Thanks once again to Sean for this! Loren ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] svn:externals, capistrano and extensions
Before I go on the long search in my svn book does anyone have any
insight into how to deploy Radiant (mental) as an svn:externals
blended with a few extensions in my own repository?
The goal is simply to not have to strip Radiant of it's own version
control (the ol' "find . -type d -name .svn -exec rm -rf {} \;") as I
do now, but to leave it in it's own world while injecting my own
version controlled extensions... All accessible as one checkout for
my capistrano recipe.
Is this something I gonna be able to accomplish or should I give-up
before trying?
Anybody?
Thanks,
Loren Johnson
www.fn-group.com
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant::Config
Cool, that sounds great. Makes plenty of sense to me. Is their anything to say about the convention extensions.extension_name.key? Thanks! L > One of my tasks this week is to remove support for the 'config' > page part. Any extension that wants to use it will need to load it > manually. After I complete that, I will be moving the Mailer > extension over to using Radiant::Config (with an importation > script, of course). The LDAP extension already uses Radiant::Config. > > Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant::Config
Is there any reason to not be storing configuration values for my Extension via the Radiant::Config class? I have been making the keys like "extensions.extension_name.setting_name" Am I off-track or on-target? Loren ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ordering of pages
John, This looks good to me. I may have preferred to not going to a separate screen but don't really have any objection to it either -- this works for me. I'm very happy to see the default sort order priority beginning with position. Thanks for putting this out there, it's great to see this coming together, or at least beginning :) Great! Loren On Jan 30, 2007, at 3:41 PM, John W. Long wrote: > John W. Long wrote: >> Loren Johnson wrote: >>> I don't currently feel qualified to work-up a new patch nor improve >>> the existing one, but I've got $$$ (seriously) for the first one to >>> do it well enough to get it included in a core release. >> >> I have a client who wants to help foot the bill for this. Contact me >> directly if you want to help. > > Here's the first pass after a day's work (works with mental): > > http://dev.radiantcms.org/radiant/attachment/ticket/45/ > sortable_pages.mental.diff > > The patch doesn't address the reparenting issue. I'm going to have > a go > at that as well, but am working on this this in iterations. > > Please have a look if you have a moment. > > -- > John Long > http://wiseheartdesign.com > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ordering of pages
Does anyone else appreciate the ability to re-parent nodes as a great asset for Radiant as a site planning tool (http:// www.sparrowstyle.com/blog/comments/radiant_as_a_site_planning_tool -- not my article, but I agree). I had used the patch initially and got so annoyed with the cumbersome icons and the unsatisfying "up 1", "down 1" metaphor. It's a set along the way and I'm sure many have put-up with it as-is to do thing with their sites otherwise not possible, but what's next? What's the best way to do this and get it in a release? My vote is for: A subtle drag handle/icon next to every node. A confirmation on the move if it's a reparenting otherwise on a reorder it just does it, maybe with a little highlight effect feedback... Skip "auto expand" as you drag around to re-parent unless it's easy and isn't jumpy (auto expanding can be annoying). * It sounds to me like the ability to turn-off these options, especially re-parenting, would be desirable. But I don't know how to approach that without talking about roles and permissions. If the target for the CMS remains to be a small team of trusted individuals then I think implementing the reparenting scheme such that it's not easy/impossible to do by mistake is good enough security. On Jan 30, 2007, at 12:17 PM, Tom von Schwerdtner wrote: I personally think re-parenting is bad (breaks URL's.. if you are careful with your site you shouldn't really need to do it.. in a perfect world). ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ordering of pages
While I agree 100% that it's mock-up time, I must comment that your scenario below seems more likely a proprietary requirement than the inverse Just a thought. I'd be pretty disappointed to not have the ability to re-parent pages in admin. I think the Comatose solution of putting a "hidden" drop down where you specify the parent of the page provides some of what you need as it makes reparenting a little bit obscure and out of the path of the ordinary content creator / editor. As for "too many pages", yes this probably needs to be addressed. The www.diopa.org site has quiet a few pages and things are still feeling ok to us. I've played-around with taking-out the page icon and shrinking the row height to make the listing shorter and more "all business". This helped a lot. But as for the "right way" to do this... hmmm... I don't follow your scenario too well personally I'd love to see any mock-ups. I like thinking about a future Radiant would have a standard way of filling the page with just one node and all it's children down ... especially if it related in someway to a permissions system or build-in hooks for such a thing to be more easily extended in On Jan 30, 2007, at 11:16 AM, Jacob Burkhart wrote: I'm a little worried, because I want my radiant users to be able to re-order things, but not to re-parent things. And having re-parenting through the same mechanism as re-ordering could make it more difficult to re-order, and could also make it a hassle to somehow permission things so that only re-ordering is allowed for certain user types... ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ordering of pages
With all due respect, I agree with Jacob. Everything discussed so far sounds like a hack. Let's bat around what the right solution is a little longer before worrying about how it's going to be done. Here are the possible ways I see, in order of preference (see that's an arbitrary ordering right there ;) Option 1 My opinion on how to do this "right" would be to have the nodes within the tree draggable. Ideally I could even drag between parents, auto-expanding of collapsed nodes as you drag the page over them. If that were fully implemented I can't see that being confusing to anyone, it's pretty standard GUI stuff these days. However, I can see this being a volatile setup if the drag timings and indicators weren't crystal clear and really worked-out. Even then, free dragging and dropping can easily create a messy accident. This could be solved with a confirmation popup a la "do you really want to delete this page part?" but with a more lengthy message something like: - Do you really want to move the Page and all it's children: Parent > Child > Child with a very Long Title > Child to Parent > Child > Another page ? --- Option 2 An alternative would be just a free drag within a set of children and then an explicit "Move Page Tree" link for re-parenting such that when it was clicked a flash message would appear up top saying "Select the new location of this Page (and it's children)." ... I'd prefer this solution but I don't like the idea of having another link on every item on the tree or having to come-up with a whole small set of feedback indicators for "selecting the new location" (see how picky I am, jeesh!). Working through a mock-up of this second option might reveal how to simplify it further. Option 3 Finally, it should be mentioned that in Matt Mcray's Comatose CMS Plugin which resembles Radiant much there is just a "Parent" drop down box revealed once you click the link on a page to reveal the slug, etc. The drop down has a text indented version of the page tree within it. Just select your new parent and save. Reordering is handled by drag and drop after clicking a "reorder children" link on the parent node. The combination of these two things works for me too. It's simple and uncluttered and definately nothing is going to happen by accident. On Jan 30, 2007, at 7:32 AM, Jacob wrote: Your proposals so far all sound like hacks to me. There's nothing wrong with a Hack. But if we want to solve this problem for good and check it in to Mental/Trunk. We should solve it the right way. And the only thing that makes sense to me is to add an "order" column to the "pages" table. This column should be the default order of everything, and should be auto-populated as you create new pages. All of this is simple and straightforward. The real question in my mind is how it should look from an interface perspective. Should you be able to drag and drop pages from within the tree view? Sounds complicated and potentially confusing, but perhaps it could be done... So, I think there would need to be a seperate page for ordering. Where somehow you say "I want to order all the children of this page". And you go to a screen where you can drag-drop re-order them. So, where should the magic "I want to order all the children of this page" button be? Should it be somewhere in the tree view, somewhere on the edit page screen? What should it look like? What should it be called? Thoughts people? I could totally implement this... John Long, what's your client's budget for this feature? : ) Would he want it added to Mental or to Trunk? -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Include a CSS style sheet in an extension?
Copy it to public as part of the activate method and the inverse in deactive? I have been keeping my stylesheets and related js files in /public/ extensions/name_of_extension/stylesheets and --/scripts. This makes sense to me. The more cumbersome part is making sure that the future user knows to add the stylesheet to their layout as part of the installation of the extension. Now if you're asking about stylesheets within the admin area purely, take a look at the head of the application layout (/app/views/layouts/ application.rhtml)... It seems you may be able to inject stylesheet references by adding them somehow to the @stylesheets array. Sean Cribbs in a recent response to my question also insinuated that there is provision for doing this though I've not yet looked any further into it. Hope that's of some help, Loren Johnson www.fn-group.com On Jan 27, 2007, at 6:16 PM, Kaleb Walton wrote: > Is there any way to include a CSS style sheet in an extension? If not, > what is the preferred way of styling elements in an extension? > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ordering of pages
This has got my fervent vote. I'll try and not go on and on... but... For every of the 5 or 6 sites I've now put up in Radiant sorting was a requirement that I have had to work around not having. It seems like it'd be a very natural addition to what Radiant is. Mostly the workarounds have entailed manually maintain navigation schemes where I otherwise would have just done a http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Inserting a javascript file reference from an extension
Well, that sorta answers the question. I need to look web standards and js a bit. I definately want to manage the js file as a file and not as a page or snippet. I also think I'll really need it to load within but that's a web standards question. If it still works and validates and I can load the file in as body then that's great. The file loads everything-up on window.onload anyhow so it won't even try to load until after the HTML is done. I did see those methods as part of the Admin template and setup earlier and will be using themt (sorry don't have it to refer at my fingertips right now either) for cleaning-up 2nd level navigation within a couple of admin applets. Ramble ramble. Thanks, I'll see what I find out about .js file loading in the . Loren Johnson www.fn-group.com On Jan 25, 2007, at 12:16 PM, Sean Cribbs wrote: Well, depends on whether you're talking about a Radiant layout or a Rails layout (i.e. in the views/layouts directory). I might suggest when your extension activates, do some creation of the appropriate javascript files (if they don't exist), either in the public directory or as pages in Radiant. I have an idea brewing in the back of my head about copying extension assets on installation or on demand, but I'll probably want to talk it over with the rest of the team. Now if you're just talking about the admin interface, you can write Javascript code directly into the layout with the content_for block (I forget exactly what the section is, but look at app/views/admin/ page/page.rhtml for an idea.) If you don't want it in your template, just put it in a partial where it's easier to update and render that partial inside the block. Did that answer your question? Sean On 1/25/07, Loren Johnson <[EMAIL PROTECTED] > wrote: (Sean re. extension/lib autoloads -- thanks, that makes perfect sense though I'm still not sure I'm not crazy :) Is there any magic way to add a javascript file reference to the header of my site pages without doing the obvious and just dropping it in my Layout? I'm currently writing a large extension which will be js heavy and I'd like to make it as clean as possible. Install and go. I walked through the site_controller through parsing code this morning again and don't see anything there, so, I guess I'd like to just confirm that I didn't miss something. Thanks, Loren Johnson www.fn-group.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Inserting a javascript file reference from an extension
(Sean re. extension/lib autoloads -- thanks, that makes perfect sense though I'm still not sure I'm not crazy :) Is there any magic way to add a javascript file reference to the header of my site pages without doing the obvious and just dropping it in my Layout? I'm currently writing a large extension which will be js heavy and I'd like to make it as clean as possible. Install and go. I walked through the site_controller through parsing code this morning again and don't see anything there, so, I guess I'd like to just confirm that I didn't miss something. Thanks, Loren Johnson www.fn-group.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Requiring classes stored in my_extension/lib directory doesn't work
Getting FeedParser for Ruby to work out of the extension/lib
directory for the RSS extension proved all but impossible as far as I
could tell. All the same stands true for the Akismet library in
commentable too. I just don't think that the my_extension/lib is in
the path though I know it was in the plugins/behavior world and
thought it worked earlier when playing with extensions:
e.g.
For RssReader the FeedParser module was setup such that it had a
there is a file at lib/feedparser.rb and also a directory including
some of it's depedencies which it explicitely references using paths
relative from the lib directory (e.g. require 'feedparser/
textconverters').
I tried this setup as well as moving the supporting files out of the
feedparser directory and directly into lib themselves (changing the
relative paths in the require statements).
After trying any number of tricks including giving the requires
absolute paths from Radiant's root (a la "vendor/extensions/
rss_reader/lib/feedparser')
Everything I tried always got me the same error from mongrel on
starting the server:
/Applications/Locomotive2/Bundles/standardRailsSept2006.locobundle/
powerpc/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require': no such file to load -- feedparser
(MissingSourceFile)
...
Any Page types I've put in lib do get loaded so this is fishy to me.
I hope I'm missing something, but as far as I can tell files in
extension/lib are not reliably getting loaded?
extension_loader.rb has this:
def discover_extensions
config.extension_paths.map do |path|
Dir.glob("#{path}/*").sort.select { |f| File.directory?
(f) }.map do |ext_path|
load_paths = %w(lib app/models app/controllers app/
helpers).map { |p| "#{ext_path}/#{p}" }
load_paths << ext_path
load_paths.each { |p| config.load_paths << p }
config.controller_paths << "#{ext_path}/app/controllers"
config.view_paths << "#{ext_path}/app/views"
@extension_roots << ext_path
end
end.flatten
end
Which looks to me like it should be setting-up the necessary load
paths to make things go...
Am I crazy?
Loren Johnson
www.fn-group.com
On Jan 25, 2007, at 8:22 AM, Sean Cribbs wrote:
> A statement in general about extensions: If your extension has any
> dependencies, it's best to include them in the lib/ directory of
> the extension. That way you can avoid any 'dependency hell'. The
> exception, of course, is gems and other libraries like RMagick that
> are potentially system-specific ( i.e. binary) or require
> installation. The thing I liked about acts_as_attachment is that
> it still works even if you don't have RMagick.
>
> Sean
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Comments Behavior port to an Page Type / Extension
Well color me corrected. So perhaps this is worth revisiting later but still before the official Radiant Blog functionality gets worked- out (which could be quiet a while I'd guess). I think the pages as grand children is helpful for now as keeping it in the page tree has a certain poetry to it and keeps the management of the comments inherently simple. An admin tab would have to start from scratch, but by all means I can imagine a better way . . . Have you ever done a rough mocked-up of how it might work ? If 0.7 comes-out with more a more full set of blogging features do you imagine commenting would in fact be "integrated" or as an Extension? Mostly curious in terms of future architecture plans... ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Comments Behavior port to an Page Type / Extension
Oops... A zip of the ported commentable extension code can be found here: http://www.fn-group.com/assets/code/commentable.zip Sorry about the attachment for those of you who received it that way. Loren Johnson www.fn-group.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] How to convert a Behavior to a Page Type in a Radiant Extension package (Mental)
ROUGH STEPS TO CONVERTING A BEHAVIOR TO A PAGE TYPE PACKAGED AS A
RADIANT EXTENSION
I've ported all my own behaviors to Page Types packaged in Extensions
within the last day so my mind is fresh on the topic, however this is
by no means a comprehensive or even wholly accurate guide.
Use at your own risk (SEE ALSO NOTE AT BOTTOM).:
1. Rename the folder of your Behavior and DON'T name it end with
Extension then move the folder from plugins to extensions so:
# move
/vendor/plugins/comments_behavior
# to
/vendor/extensions/comments
2. Delete the init.rb file and create a new file called
"your_extension_name_extension.rb" and fill it with this general:
class CommentableExtension < Radiant::Extension
version "0.1"
description "Blah blah blah which will appear as the description
of this Extension under the Extensions list in the Mental / new
Radiant."
url "http://www.fn-group.com/";
# Happens when the enabled checkbox is check and saved in the
admin Extensions list
def activate
# These are Page type classes which were converted from
behaviors as detailed below
CommentBucket
Commentable
end
# The opposite
def deactivate
end
end
3. Classes already in the lib directory are auto-loaded and no longer
need to be explicitly required. In fact the explicit requiring of the
classes in the lib directory seems to break things, but no need to
worry they're already available.
4. Rename your class appropriately, at least taking off "Behavior"
from the end of name if it's there, then inherit from Page not
Behavior::Base, so:
class CommentableBehavior < Behavior::Base # becomes
class Commentable < Page # Isn't that neat. We're just adding right
onto the page.
5. Comment out or delete the register line, this is no longer
needed in a Page type and will in fact break things if it's not removed:
register "Commentable" # becomes
# register "Commentable"
6. Remove the "define_tags do ... end" enclosure. It's no longer
needed. Nifty Page types will know what to do with all those "tag ""
do |tag|"s
7. If you have disabled the page caching in your behavior change:
def cache_page?
false
end
#to
def cache?
false
end
8. Search and replace "@page" with "self" ...
9. Encapsulate existing comments in "desc %{ what your tag does
here ... }" headers on the line above a tag definition to get a
description to show-up in the new "Available Tags" link in the Admin
interface.
10. Restart the web server for your Radiant app, look for errors in
log/mongrel.log (or later in log/production.log) -- repeat.
NOTE
If you were creating an Extension from scratch you get this framework
by using "script/generate extension YourExtensionName" ...)
This guide in no way demonstrates the power or architecture of the
new Radiant Extensions which go beyond the scope of behavior and can
include, among other things an admin interface, custom models, views
and routes
Loren Johnson
www.fn-group.com
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Access to params within extension
No, I get that. Here is my custom route:
map.connect 'event-
calendars/:calendar_group/:calendar/:period', :controller =>
'site', :action => 'show_page', :url => 'calendar'
So I'm forward the control back to the Radiant Site controller.
My question is within the Page type which I attach to the real
Radiant page found at "/calendar" how can I cleanly access the url
params ? This is how I solved it for now, but it's ugly and inflexible:
class EventCalendar < Page
tag "calendar" do |tag|
path = @request.request_uri.split("/")
p = Hash[:calendar_group => path[2], :calendar => path
[3], :period => path[4]]
...
end
end
Just hoping to find a better way.
Thanks,
On Jan 21, 2007, at 11:52 PM, Daniel Sheppard wrote:
If you've made a custom route, then that route will be handled by a
regular rails controller, not a page object.
Loren Johnson
[EMAIL PROTECTED]
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Access to params within extension
Can someone give me a leg up? I'm finding it difficult to find the request.params array anywhere within the Page context. I have setup a custom route as part of my extension (not for the admin area, but for the main site) and in that route I have mapped some custom params I really want to access. Any ideas... I tried tag.local.parms[], tag.page.param[], @request.param[], etc. Looking through the models/page.rb and taggable I don't see any place I'd get this from, but I'm hoping I'm missing something. Thanks, Loren Johnson [EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] mental extension development help
BJ and I worked through the issues on this over IRC today and cleaned everything up into an acceptable port to extension. He'll be doing officially announcing and offering it up on the group today or tomorrow. On Jan 21, 2007, at 6:11 PM, Daniel Sheppard wrote: I'm trying to port the rss behavior to an extension for use in mental. I can't find anything talking about how to develop extensions, so I'm baseing this off looking at hello_tag example. What, if anything is happening? Put some print statements into your rss_reader_extension file to show if it's being loaded. Have you put your extensions files under vendor/extensions/ rss_reader ? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant Loren Johnson [EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] mental extension development help
BJ, If we can meet on IRC today or tomorrow we could maybe work on this together. I was planning on porting the RSS behavior this week anyway so I can convert one of our sites that needs it but also needs to go Mental. I'll get on the #radiantcms IRC channel at 2:30 PM MST and hang-out there until 5ish. Let me know if you want to setup something for tomorrow instead. Loren On Jan 20, 2007, at 6:06 PM, BJ Clark wrote: > Sorry, accidentally hit send (I've gone brain dead looking for stuff > on extensions). > > Anyway, this is obviously not working, but I have no idea where to > go from here. > Can anyone jump in and help here? I'm not sure what has changed from > the old system to the new, so I have no idea what I need to change. > > Thanks, > BJ Clark > > > > On 1/20/07, BJ Clark <[EMAIL PROTECTED]> wrote: >> I'm trying to port the rss behavior to an extension for use in >> mental. >> I can't find anything talking about how to develop extensions, so I'm >> baseing this off looking at hello_tag example. >> I've created two files: >> rss_reader_extension.rb that looks like this: >> http://pastie.caboo.se/34525 >> >> and lib/rss_reader.lib: >> http://pastie.caboo.se/34529 >> > ___ > Radiant mailing list > Post: Radiant@lists.radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Blog Commenting
That sounds right, sound great. I will hack it in as-is (if I can do it in an hour or two stumbling around) as I need something right now and don't want to backup to 0.52 at this point in our release. L On Jan 16, 2007, at 8:43 AM, Sean Cribbs wrote: Loren, Yeah, somehow I borked the SVN repo while trying to switch my website over to Mongrel. It's still there, just not accessible. I'm going to submit another ticket and see what the TxD gurus can do. However, I am considering a complete rewrite. Since we can easily have custom models and controllers now, we could circumvent the need to have the two-page redirect circle and grandchild pages and just postback to a controller instead. I'd also like to have a nice admin interface where you can sift through comments, both accepted and spam, and either mark as 'ham' or as 'spam' so Akismet can get better at catching them. Anyway, full-featured blogging support is on the roadmap for 0.7, so I'm sure there will be contributions from the rest of the core team as well. Sean Loren Johnson wrote: Sean -- I grabbed commentable the other day from the repo without issue but needed to grab it again today and it seems the repository is down? As for porting the behavior to a page type I'm probably going to do just that today once I can check-out the code again. I had started on it last week but got waylaid. Have you made any more progress on this front? Do you have time to work together on it? If not I can just get it as far as I need and then send you a diff to look over. L On Dec 31, 2006, at 12:19 PM, Sean Cribbs wrote: If you're using 0.5.2, you can use my comments behaviors: http:// seancribbs.com/svn/rails/plugins/comments_behaviors . They have basic commenting functionality, store the comments as child pages, and can use Akismet for spam filtering. If you want to use the mental branch, I intend to port them over "soon". Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Blog Commenting
Sean -- I grabbed commentable the other day from the repo without issue but needed to grab it again today and it seems the repository is down? As for porting the behavior to a page type I'm probably going to do just that today once I can check-out the code again. I had started on it last week but got waylaid. Have you made any more progress on this front? Do you have time to work together on it? If not I can just get it as far as I need and then send you a diff to look over. L On Dec 31, 2006, at 12:19 PM, Sean Cribbs wrote: If you're using 0.5.2, you can use my comments behaviors: http:// seancribbs.com/svn/rails/plugins/comments_behaviors . They have basic commenting functionality, store the comments as child pages, and can use Akismet for spam filtering. If you want to use the mental branch, I intend to port them over "soon". Sean ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] POLL: Upgrading Unpacked Radiant Applications
> 1. Did you install Radiant from source or use the gem? Source > 2. If you installed Radiant using the gem, did you use the --unpack > flag > with the radiant command? > 3. Would you mind if we dropped support for upgrading unpacked Radiant > applications (apps installed using the --unpack flag) if it > means that Radiant releases can occur more frequently? Not at all. More frequent releases would be great. I think it's entirely sensible to drop the --unpack luxury if it's at all costly to keep. Loren Johnson FN Group www.fn-group.com ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Solved: Extensions and authentication
Todd,
Thanks for this, I had already given-up on the possibility of an
extension doing anything other than packaging-up an admin interface
for functionality which would have to happen through Radius tags. As
it is this is much more powerful, especially if I can figure-out how
to flow the output of my views into a Radiant layout.
However, when I apply the technique you describe I still get sent to
the login screen. What am I doing wrong in-order to bypass the admin
login requirement. Here is my Radiant::Extension class declaration
including the "no_login_required" flag:
class StaffListingExtension < Radiant::Extension
version "1.0"
description "An extension for a staff listing"
url "http://fn-group.com";
no_login_required
define_routes do |map|
# map.connect 'admin/staff_listing/:action', :controller => 'staff'
map.connect 'directory/:action', :controller => 'staff'
end
def activate
# admin.tabs.add "Staff Listing", "/admin/staff_listing", :after
=> "Layouts", :visibility => [:all]
end
def deactivate
# admin.tabs.remove "Staff Listing"
end
end
?
Thanks,
Loren Johnson
On Jan 7, 2007, at 6:04 PM, Todd McGrath wrote:
> Hey Todd,
>
> Add "no_login_required" after the class declaration.
>
> Your buddy,
> Todd
>
> Quoting Todd McGrath <[EMAIL PROTECTED]>:
>
>>
>> I'm missing something obvious about extensions and authentication
>> requirements?
>>
>> Background
>> I setup an extension hoping to be able to process forms from the
>> _public_
>> side
>> of the site.
>>
>> * using Mental Branch
>> * run ruby script\generate extension mailertest
>> * update mailertest_extension.rb:
>>
>>define_routes do |map|
>> map.connect 'mailertest/:action', :controller => 'mailertest'
>>end
>>
>> * in mailertest controller add method to make sure the new
>> controller is
>> used:
>>
>> def index
>> logger.info("if I'm not back in 5 minutes, wait longer")
>> end
>>
>> * access http://localhost:3000/mailertest
>> where I'm promptly redirected to the /admin/ login screen.
>>
>> log:
>> Redirected to http://localhost:3000/admin/login
>> Filter chain halted as
>> [#> @filter=:authenticate>] returned false.
>> Filter chain halted as [:authenticate] did not yield.
>>
>> --/--
>> I'm missing something obvious aren't I? Is there a way to specify
>> that an
>> extension shouldn't require authentication?
>>
>>
>> Actually, maybe I'm on the wrong track all together - I want to be
>> able to
>> process forms submitted from the public side of the site. I don't
>> need any
>> tags that will create the forms and inputs. Perhaps, easier if I
>> add a
>> route
>> in routes.rb to /mailertest and put the controller alongside
>> Radiant code?
>>
>> Any insight appreciated!
>>
>> Todd M
>> ___
>> Radiant mailing list
>> Post: Radiant@lists.radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>
>
> ___
> Radiant mailing list
> Post: Radiant@lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
___
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Blog Commenting
Does anyone have a good example of a commenting implementation currently working in Radiant? I would love to see an example or two understanding that right now, until something to do it is included in core, commenting is going to be a hack. Thanks, Loren Johnson [EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Mental Branch "Extensions" Notes
Keith,I just want to second this, the extensions are very well thought out and pretty easy to use even in their very raw state. I have a very simple assets management system (based on acts_as_attachment) that took maybe a few hours to set up. Most of that was making sure that the views integrated nicely into Radiant. Are you using this mental branch install in "production" i.e. as a live site? Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Mental Branch "Extensions" Notes
I've been playing with the Mental branch this weekend to test-out the work being done on the new Radiant Extensions concept. I thought I just put down a quick narrative of my experience with it to give those who've not had a chance to check it out recently a preview of what's to come. There is some work still to do here, but as far as I can see a lot of work has been done in the last few weeks. Everything is working pretty well... I can generate and extension "script/generate extension calendar" and modify the necessary lines in the extension activate method to make it show-up as an admin tab. Then I was able to dump a bunch of pre-existing models and migrations from the Calendar application I want to integrate with ease. Understanding that this is very much a work in progress, I did want to make one note of interest: When I created the Calendar extension and then ran my migrations I found out quickly that it doesn't work well to have a model named the same as the Extension (I had a Calendar model as well). I renamed my Calendar model, reversed the migrations by hand and everything migrated up fine the second time around. Then in my calendar controller I dumped a scaffold :event_calendar and voila! I had a nifty interface for adding and removing calendars right within Radiant admin. I know I for one see the maturation of these extensions as an important turning-point for Radiant as a project. IMHO this robust and Rails friendly way of extending Radiant is key to allowing it to remain spartan. Though I might still prefer the CMS to be the plugin a la Comatose, this level (and method) of extensibility will mean the best of both worlds for most of those who just have CMS needs + a little something else. So, John, with crystal ball in hand, what do you see as a likely timeframe for an official release which includes both Extensions and Page Types? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problems with search_behavior
Our search form is embedded in the masthead of the site and hence shows-up on every page. I believe the tag is implemented as a behavior tag so we'd have to make every page part have the Search behavior if we wanted to use it.Loren On Nov 8, 2006, at 7:50 AM, [EMAIL PROTECTED] wrote:Loren,Thanks for your help. I got it working fine as you've suggested in themasthead of the site, and I've also tested in the sidebar.Why are you using the html form action instead of the tag?Jo.se. Jose,I implemented my search as a search box in the masthead of my sitelike this:type="text" id="q" name="q" value="" size="15" />value="Search" />Where "/search-results" is the only page with the Search behaviorselected and that page looks like this: No match. Search Results: You said below "Does this mean that gallery_behavior wasn't installedsuccesfully?" Assuming you meant search_behavior, you might doublecheck that you've selected the Search Behavior from the list. If youhadn't, that's the problem, if you had then I'll bump this to thenext person... I've no idea.Hope that helps.Good luck,LorenOn Nov 2, 2006, at 8:30 AM, [EMAIL PROTECTED] wrote: Hi,I've just installed Oliver's search_behavior via svn. However, I don'tunderstand how to implement it. Can somebody please provide a clearerexample on how to do this. I've copied and pasted Oliver's examplein anew page title search. No match. Results: by However, when I navigate to that url I getundefined tag `search’undefined tag `search’undefined tag `search’Does this mean that gallery_behavior wasn't installed succesfully?Jose.___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant Loren Johnson[EMAIL PROTECTED]___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problems with search_behavior
Jose,I implemented my search as a search box in the masthead of my site like this:Where "/search-results" is the only page with the Search behavior selected and that page looks like this: No match. Search Results: You said below "Does this mean that gallery_behavior wasn't installed succesfully?" Assuming you meant search_behavior, you might double check that you've selected the Search Behavior from the list. If you hadn't, that's the problem, if you had then I'll bump this to the next person... I've no idea.Hope that helps.Good luck,LorenOn Nov 2, 2006, at 8:30 AM, [EMAIL PROTECTED] wrote:Hi,I've just installed Oliver's search_behavior via svn. However, I don'tunderstand how to implement it. Can somebody please provide a clearerexample on how to do this. I've copied and pasted Oliver's example in anew page title search. No match. Results: by However, when I navigate to that url I getundefined tag `search’undefined tag `search’undefined tag `search’Does this mean that gallery_behavior wasn't installed succesfully?Jose.___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Our first site in Radiant, finally
Thanks Tino,I did know about the breadcrumb failure up top... That's one of the reasons I'll be re-writing my Calendar behavior to work properly through virtual_pages... I assume you ran into the problem with the calendar URLs.Good luck on your site!On Nov 1, 2006, at 11:43 AM, Tino Breddin wrote:Just in case you did't notice it yet, some links provided in the navigation bar above the header point to non existing parts of your site. Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Our first site in Radiant, finally
Our first site in Radiant is up and runningOur first site in Radiant is up and running. We've got lots of work still to do, but we're happy with the manageability of things in Radiant even after a chaotic and compressed release schedule:http://www.diopa.orgThe CMS we used before this for this site was ModX (php) which had a few very good things going for it: 1) feature rich and, 2) dead simple to implement exactly the visual design we wanted, 3) mature. However where it lacked and what ultimately pushed us over to Radiant, despite it's relative lack of features: 1) More enjoyable / simpler to use, 2) Ruby, 3) Rails. We hope to be building applications in Rails all next year and didn't want to be dragged down by a PHP legacy app.Available Behaviors UtilizedMailer Behavior, Search Behavior, RSS Feed Behavior, Redirect Behavior (just a code snippet grabbed from Sean here off the list)MUCH GRATITUDE TO EVERYONE WHO SET OFFERED THESE BEHAVIORS TO THE OPEN. We couldn't have gotten the site done in Radiant without at least this much of a jump start.Custom Behaviors / Global Tags CreatedCustom global tagsIn the course of getting what we needed out of Radiant for this release I hack-in the following custom tags They're all a little obscure and nothing genius going on so I won't bother explaining them -- if someone is interested in any more detail just ask: iCal fed Calendar DisplayI also created a custom behavior called "calendar" including a set of tags and virtual pages for displaying a grouping of calendars fed from Google Calendar feeds. The Event and Calendar models are created and administered in another Rails app and database. If you go to: http://www.diopa.org/calendar/master/all you'll see it in action. This behavior needs to be revisited and implemented using page_virtual and such (for now I override find_page_by_url and manually parse the path to get parameters...), but hopefully I'll get a chance to clean it up into something self contained and worth sharing.Mods of anything outside the Vendor, Log and Public directoriesBeing the first attempt to seriously use Radiant much of my energy in this project was diverted to finding ways to stay out of the app directory. I want us to stay on track with Radiant as new releases are formulated. The only change I had to make was in /app/views/page/new.rhtml where I added a row in the more... and included the published_at date such that it could be modified to reflect the correct date on content converted from the previous site.Wish List1. A new plugin system / page types (same thing, right?). How much I'd love to be able to be free to build madly and freely on top of Radiant without feeling like I was branching or going to need to create an auxiliary Rails app.2. Page reordering and re-parenting so that I can 3. A more sophisticated navigation generation tag or tags which has options for dynamically generating navigation based on the tree which would go hand and hand with arbitrary ordering of pages and probably a new page attribute or status to indicate whether an article should show-up in navigation or not. Thanks to everyone for the bits of help throughout. I hope that through continuing to improve this site we'll have some help and code to offer back to the community. Loren JohnsonFN Group[EMAIL PROTECTED]AIM: NL7XF ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Mailer Behavior - File Attachments
Has Matt or anyone else made any progress on making file attachments work with the Mailer Behavior.I'll hack in an implementation for my purposes if need be, but would much prefer to go off something already thought through. Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Quick and easy question
I'm now 3 days into pulling my hair out trying to get a custom calendar/events behavior to do what I need it to.Two questions:1. I can't seem to deduce from the code the purpose of page.virtual (or page_virtual within the behavior context). How is it used? How might the use of it help me in creating a behavior which generates it's own, well, virtual pages a little like the Archive Behavior. 2. I'm overriding find_page_by_url and taking all the paths above the page with the behavior as parameters to that behavior then outputting the page again... so my find_page_by_url looks simply like this in the behavior: def find_page_by_url(url, live = true, clean = false) @page endHaving went around the routes and everything else in this manner I'm not surprised that my here or selected on these link even though the url's are a match... Is there a way to trick Radiant back into seeing my "virtual pages" as real pages in the proper context so that, well, I can use 3. Am I thinking of this all wrong? I've studied the search and the archive behaviors to get this far but I'm going into uncharted area. What I'm doing currently feels like a bit of a hack but I got here by trying to take Radiant with me instead of diving straight into the routes.rb and doing everything (including managing a separate set of layouts) in another app Maybe I should have just done that?Any help is greatly appreciated. I've really struggled with this and have to release it tomorrow. I never did feel like I found just the right implementation. However, when I am done I will attempt to clean it up a bit, refactor as necessary and offer it to anyone here who might have use for an iCal subscription based event calendar/tags for Radiant. Thanks,Loren Johnson___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Dynamic Attributes in a Snippet Tag?
We do currently use a Summary page part and a ArticleSummary snippet. In the following scenario it allows us to flow-in article summaries with 3 lines of markup instead of 6. Big deal... but it would allow us to build-up a CMS vocabulary and more viably bring a client directly into the content management themselves. I do understand that this sort of simplified Content Management workflow stuff begins to fall out of the scope of Radiant as so far articulated. I digress.LorenOn Oct 27, 2006, at 6:26 PM, Sean Cribbs wrote: Loren, It sounds like you need page parts, but if I'm understanding you correctly, you need at least one snippet so it can be evaluated in the template or in multiple pages. A page part would contain the summary, which would be accessed and formatted by the snippet. Sean Loren Johnson wrote: Sean and Mislav thanks for the responses -- For what it's worth, below is the use case for dynamic attributes in Snippets. There are things that I'd like to see added to a Radiant release more and before than this without question (page reordering and reparenting please), but at least here is a use case for the record of what I think could be an easy, useful and possibly in-scope extension to Snippets. An Article Summary Template I work with a designer for most everything I do. His HTML/CSS skills are poor. We are just finishing-up a site (http://diopa.grimedesign.com) and in that site on several pages we pull-in the summary part of an article and attached a nice little header which spits out the name of the Section and the date the Article was posted before the title. This summary pattern repeats many times and is always the same except that we like to customized the link text which goes to the full article. Everything else is dynamic. So I say to Paul, no problem I'll just through that little set of tags into a snippet such that he can do a This means that he doesn't have to copy and paste a format for this summary over and over as he populates the site with content. It also of course means we don't have to change it in all those spots if we want to change something global outside the scope of the CSS in this summary format. We had considered using another page part called "linkText' to accomplish the same end, however we have situations where the same article is posted in multiple places on the site in different contexts and the link text changes accordingly. Without any of these options working we're left with the acceptable, though less than preferable solution of: Read more about this on ECS News... Cheers, Loren Johnson [EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Dynamic Attributes in a Snippet Tag?
Sean and Mislav thanks for the responses --For what it's worth, below is the use case for dynamic attributes in Snippets. There are things that I'd like to see added to a Radiant release more and before than this without question (page reordering and reparenting please), but at least here is a use case for the record of what I think could be an easy, useful and possibly in-scope extension to Snippets.An Article Summary TemplateI work with a designer for most everything I do. His HTML/CSS skills are poor. We are just finishing-up a site (http://diopa.grimedesign.com) and in that site on several pages we pull-in the summary part of an article and attached a nice little header which spits out the name of the Section and the date the Article was posted before the title. This summary pattern repeats many times and is always the same except that we like to customized the link text which goes to the full article. Everything else is dynamic.So I say to Paul, no problem I'll just through that little set of tags into a snippet such that he can do a This means that he doesn't have to copy and paste a format for this summary over and over as he populates the site with content. It also of course means we don't have to change it in all those spots if we want to change something global outside the scope of the CSS in this summary format.We had considered using another page part called "linkText' to accomplish the same end, however we have situations where the same article is posted in multiple places on the site in different contexts and the link text changes accordingly.Without any of these options working we're left with the acceptable, though less than preferable solution of: Read more about this on ECS News...Cheers, Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Dynamic Attributes in a Snippet Tag?
Has anyone ever thought about adding an attribute to a Snippet call e.g. and then having a way of pulling that attribute in the Snippet all using Radius tags?: e.g. Snippet content more Snippet content This is one of those things which could lead to all "misuse" of Radiant I suppose, but it would sure be an easy implemenation that would enable a number of useful and potentially in-scope applications. I have a particular use-case if there is any interest. Thanks, Loren Johnson AIM: NL7XF [EMAIL PROTECTED] -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] News headline (RSS summary) behavior
Can someone point me in the right direction for a FeedParser gem or repository. I missed where to get it from and Google hasn't yielded anything useful yet. BTW, I downloaded the plugin off the ThirdPartyBehaviors page and it looked like it was already properly setup as a plugin so I didn't see why I would need to generate a plugin for it as described above. * It is however crashing my install at the moment and rake says it doesn't know where to go to get feedparser. Loren -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] basic newbie questions: Updating radiant and installing
> svn co http://dev.radiantcms.org/svn/radiant/tags/rel_0-5-2/ ~/ > radiant > ~/radiant/radiant/bin/radiant ~/web/ > ... > The second line in the command I'm not really sure... > did It save the actual radiant app in the radiant folder ( ~/radiant/ > radiant/bin/radiant ) and then create an instance in the web > directory? ( ~/web/ ) so that my website is running in instance > mode? Or did I just download the full source of radiant and then made > another copy for the web directory? I believe you generated a copy of Radiant in instance mode. You would have to use the --unpack option on the radiant command to get a full app. However in ~/radiant you should have a full install. > I'm going to have to install oliver's gallery and search behaviors > and I'm confused as to where I have to do this or if its even > possible on Textdrive. Do I install the plugin into my ( ~/web/ ) > directory or the ( ~/radiant/radiant/bin/radiant ) directory? You probably want to create another instance of Radiant with the --unpack parameter: ~/radiant/radiant/bin/radiant ~/web_full --unpack Then copy the behaviors you mention into the ~/web_full/vendor/plugins directory. > In the future when I want to upgrade radiant to 1.0, etc. Do I svn > another copy to my ( ~/radiant/radiant/bin/radiant ) directory and > then do an --upgrade from my ( ~/web/ ) directory? Or will have i > have to copy all the files over to ( ~/web/ ) again and import the > DB? You shouldn't need to import the DB, you can always point your database.yml to your existing/previous db and then when you upgrade let the migrations take care of any "upgrading". I too find it confusing how to manage a clean upgrade path with Radiant (or any full-scale Rails app which I also want to extend). My backup plan is to 1) install a new release fresh, 2) point the database.yml to the existing database name, 3) then run a "rake db:migrate" to catch it up with any structural changes, and finally, 4) copy in any of my own or other behavior plugins from my old install to the new vendor/plugins directory. Hope that helps. Loren -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] children:each vs. navigation
Jim Herring wrote: > Hi, > > I'm building a site in radiant that has a section with a long > subnavigation > menu. Initially I built it like this: > > > > > > > > > > > That works fine, except that I need selected behaviour like r:navigation > has > so that I can add another class to the div class=entry to highlight the > sub > page the user is on. > > I've tried using a big & nasty r:navigation tag (its a long list), but > the > problem in that case are the r:link & r:content bits referring to the > current page rather than the page I'm creating a link. > > Is there any way to accomplish this with the basic tag set in radiant? I > can > imagine a few ways to modify the r:navigation or r:children:each tag > definitions, but that doesn't really seem like a great way to go to me. > Am I > missing something obvious here? > > Thanks, > Jim Jim, I've read your message a couple times and don't fully understand your question. This part in particualr is where I'm losing you: > the problem in that case are the r:link & r:content bits referring to > the current page rather than the page I'm creating a link. Can you clarify this part and I might be able to help. I'm currently implementing a site in Radiant which is requiring plent of http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Sorting and reparenting patch
Tom von Schwerdtner wrote: > On 10/18/06, Loren Johnson <[EMAIL PROTECTED]> wrote: >> After a bit of looking around I see this patch: >> >> I appreciate all the help. I'm a RoR, Radiant and SVN nuby (it's been a busy >> few weeks). > > The patch is waiting for someone to clean it up to the point where it > can be accepted. I tried my hand at it but while I can get it to > apply cleanly to trunk, I don't know squat about Rails internals and > for all I know it's an ugly hack. > > I did locally apply the re-ordering portion of the patch and it's been > working fine, however I wouldn't recommend this unless you want to > deal with upgrading a patched tree or don't plan on upgrading at all. > > -Tom For the record, and I don't have time to explore why this was happening properly, but somehow magically (in the bad way) this patch seemed to break the automatic (javascript) populating of the Slug and Breadcrumbs from the Title on a new article. I started over from a fresh 0.5.2 install and everything started working again. Other than that the patch looked to be working great. Yes, the icons are ugly and the labels for moving and reparenting were far less than intuitive, but all the functionality was there. I'd sure love to see this cleaned-up and into a release but don't quiet feel qualified yet to do that work. Maybe in a month or two I'll come back around to it if nobody else does. Loren -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Sorting and reparenting patch
I'm within a week of deploying a major website release for a client using Radiant. I've worked hard to not modify any of the Radiant core directly (made a few plugin behaviors, etc.) so that I could keep on-track with future updates. However, I really could use manual page sorting and the ability to move pages around in the tree.After a bit of looking around I see this patch:http://dev.radiantcms.org/radiant/ticket/179Can someone give me a hint as to how I would apply this patch or other patches (I'm currently installed from gem with --unpack) without forever fouling my current radiant install? Or if that is exactly what it would do, when is a new official release likely that might include this functionality? I appreciate all the help. I'm a RoR, Radiant and SVN nuby (it's been a busy few weeks).Thanks,Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Modestly Extending Radiant and Forms
For a couple of weeks I've been hunting for the absolute best way to extend Radiant to handle the presentation of an event calendar. After much going back and forth I finally settled on implementing it as a series of new global tags in a plugin a la: http://radiantcms.org/blog/2006/09/14/how-to-create-global-tags-in-a-plugin. I've copied my needed Event models into this plugin as well. This has gotten me pretty far. I've got my 1. I've created attributes to select a set of event based on a date range, a number of days, etc. This will allow me to create separate pages for different date time periods. However, I'd much prefer to have a form which allow users to select the date range or categories of events to display. Is there a way to access form get parameters from within the Behavior::Base.define_tags? Has anyone came-up with an elegant way to handle this sort of thing? 2. Currently I'm handling migrations on my own models by just generating them directly in the Radiant app. I figure I'll have to do some migration re-numbering when a new Radiant release includes it's own migrations. Anybody have a better solution for handling migrations of custom models from within a plugin or without interfering with the Radiant installation?*** I'm implementing this Calendar into Radiant in this hodge-podge manner now with the educated assumption that I'll eventually be able to re-factor it and have it directly "plug-in" to Radiant (on the admin tab) and that the incorporation of a custom data model will be accomodated in some manner. Notice I didn't ask for a custom view or controler (yet). Am I assuming too much? Thoughts and solutions embraced,Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Assets Behavior
Guido,I'm trying to access the Assets Behaviour (Behavior ;) you created and am having trouble. This link: http://sohne.net/assets/assets_behavior-0.0.1.tar.gz doesn't seem to work anymore and the SVN repository is still not anonymously accessible.Is there a chance I could get ahold of this plugin, I need to index and link to a bunch of PDFs on the site I'm working on and think your plugin would be the best place for me start.Thanks, Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to make
Ok, I've been doing too many things at once. The "Bryan, thanks for the response before. On Oct 9, 2006, at 8:41 AM, Loren Johnson wrote:Yes I'm currently employing the selected tag under navigation, here is my current navigation code: This works fine if I a page is simply a child of a listed url, however if a page is a grandchild, great-grandchild, etc. then the parent/grandparent link is no longer in a selected state (I should have made that clearer). See this link for a screenshot which shows the News "tab" currently selected:http://www.fn-group.com/clients/diopa/diopa_news.jpgOn this page tag/page you'll see a series of links under the heading "Bishop's Column" (November Article, December Article, etc.) If you were to click on December Article for instance the breadcrumb would read "Home > News > Bishop's Column > December Article" and the News "tab" should still be currently selected (though right now it wouldn't be).I think I've looked at the code for the navigation tag closely enough to now know that this isn't an option as-is. Are any additional options within the navigation control currently on the table? I would think that building-in some sort of option such as "selected_if_grandchild" could have universal application. If not, what would be my next best option? Has anyone else dealt with this sort of nav scheme in Radiant yet? Thanks,Loren On Oct 8, 2006, at 6:04 PM, Bryan wrote:Loren Johnson wrote: Does anyone have an idea on how to create a navigation menu usingstandard Radiant/Radius tags in which the parent item keeps a "here"class as long as any child, grandchild, great-grandchild, etc. is thecurrent page? Have you tried using "selected" within the navigation tag?http://radiantcms.org/blog/2006/06/15/tag-primer-2/Thanks,Bryan-- Posted via http://www.ruby-forum.com/.___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant Loren Johnson[EMAIL PROTECTED] ___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to make
Yes I'm currently employing the selected tag under navigation, here is my current navigation code: This works fine if I a page is simply a child of a listed url, however if a page is a grandchild, great-grandchild, etc. then the parent/grandparent link is no longer in a selected state (I should have made that clearer). See this link for a screenshot which shows the News "tab" currently selected:http://www.fn-group.com/clients/diopa/diopa_news.jpgOn this page tag/page you'll see a series of links under the heading "Bishop's Column" (November Article, December Article, etc.) If you were to click on December Article for instance the breadcrumb would read "Home > News > Bishop's Column > December Article" and the News "tab" should still be currently selected (though right now it wouldn't be).I think I've looked at the code for the navigation tag closely enough to now know that this isn't an option as-is. Are any additional options within the navigation control currently on the table? I would think that building-in some sort of option such as "selected_if_grandchild" could have universal application. If not, what would be my next best option? Has anyone else dealt with this sort of nav scheme in Radiant yet? Thanks,Loren On Oct 8, 2006, at 6:04 PM, Bryan wrote:Loren Johnson wrote: Does anyone have an idea on how to create a navigation menu usingstandard Radiant/Radius tags in which the parent item keeps a "here"class as long as any child, grandchild, great-grandchild, etc. is thecurrent page? Have you tried using "selected" within the navigation tag?http://radiantcms.org/blog/2006/06/15/tag-primer-2/Thanks,Bryan-- Posted via http://www.ruby-forum.com/.___Radiant mailing listPost: Radiant@lists.radiantcms.orgSearch: http://radiantcms.org/mailing-list/search/Site: http://lists.radiantcms.org/mailman/listinfo/radiant Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] How to make
Does anyone have an idea on how to create a navigation menu using standard Radiant/Radius tags in which the parent item keeps a "here" class as long as any child, grandchild, great-grandchild, etc. is the current page? Currently the I guess I could override and extend that tag, create my own, or perhaps accomplish this with just an iteration through the page tree using a combination of more elemental Radius tags?Has anyone already addressed this situation. It should be common enough. Thanks, Loren Johnson[EMAIL PROTECTED]___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] undefined method `find' for Status:Class
Great tip, that fixes it for now and I too would like to know why it's not working under Mongrel. HmmmCheers to you,LorenOn Oct 2, 2006, at 9:12 PM, Michael Roper wrote:I have also had a similar problem since upgrading Locomotive over theweekend...I'm not sure what the exact problem is, but it seems to have somethingto do with the default server in Locomotive being changed to Mongrelinstead of Lighttpd...I got around the problem by putting 'server: lighttpd' in theconfig/locomotive.yml (?) file, making it use Lighttpd instead ofMongrel...if anyone can shed some light on why the error is occurring in thefirst place, I would also be grateful... Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] undefined method `find' for Status:Class
I'm getting a "undefined method `find' for Status:Class" whenever I install Radiant (either through the gem or an svn co) and then launch through Locomotive.This happens when loading the "home page" of the Simple Blog or the Empty website. If I launch the server directly without Locomotive running everything works as expected. Any ideas? I did see messages about this error in July but never saw a resolution nor did it appear at that time to be related to Locomotive (http://lists.radiantcms.org/pipermail/radiant/2006-July/000881.html)I've confirm the presence of models/status.rb, etc. It seems to be some sort of path issue related to the Radiant configuration and Locomotive settings...Help? Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
