Re: [Radiant] Customizing Radiant's command line behaviour
On Sat, Jan 31, 2009 at 3:13 PM, Andrew Neil wrote: > I wonder if rails templates could be used for setting up a fresh Radiant > site to taste: > >http://m.onkey.org/2008/12/4/rails-templates > > That would be very nice. If I read correctly, this feature would become available in rails 2.3 (so it's not available 'yet')? But it might be very interesting to use indeed. Jeroen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Customizing Radiant's command line behaviour
On Sat, Jan 31, 2009 at 7:48 AM, Adam van den Hoven wrote: > I was talking about editing radiant directly and bending to my will but > writing a script to handle it is probably smarter. > > Sigh I do hate it when lofty ideas are shot down. :) > > Now if I could only bypass the interactive portions of the bootstrap. Well, assuming you're on something 'unix' like, you can probably 'pipe-in' the answers to the questions with "<". i.e make a file containing the answers to all the questions: "y 3 " (or something similar) and then do "rake db:bootstrap < answers.txt" (not tested though). Else it might be a good idea to make a 'non interactive' option to rake db:bootstrap. Jeroen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Extenision help for a newbie
On Thu, Jan 29, 2009 at 6:49 PM, Chaim Kirby wrote: > I'm trying to get a clear view in my head of what happens when > extensions are deployed to a server, and the process that I can use to > deploy them. I have noticed some extensions come with deployment > directions and others don't. Is there some standard set of commands I > should be using to deploy an extension? I searched through the > documentation, but did not find an authoritative guide. I think there are two rake tasks related to extensions that you might be interested in: rake db:migrate:extensions rake radiant:extensions:update_all These rake tasks will perform actions as specified by an extension. (i.e. run the database migration, install any public assets from the extensions). Best regards, Jeroen Janssen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Abstract and Resource controllers
On Thu, Jan 29, 2009 at 2:36 PM, Andrew Neil wrote: > I'm pleased that you have a working link_roll extension, at the end of it. > That was my main concern. If you could update the errors you've pointed out > too, that would be a great help. I've updated the wiki with some of the items I found. I have not updated the screenshots though (I don't have a mac, so we would get windows / linux screenshots instead). > It's hard to keep a consistent tone of voice on a wiki. Please feel free to > edit the style of prose however you see fit. I know, for now I left it as-is until I can figure out how to let it sound better. > I think that when the default (commented out) routes are generated, it is > not possible to know how the controllers in your extension will be named. > All that is known is the name of the extension itself. It could be useful, > though, to make the default route resourceful, as a pointer for extension > developers. Sean already merged http://github.com/radiant/radiant/commit/efcee1767370ae84e0713a70113614ffac882227 so that should put developers in the right direction. > Another point about the generated output, is that the "deactivate" action > could probably be left out, now that it does nothing (I think). I don't know about it's history (and future), so I can't comment on that, but it's easily removed from the template if needed. Jeroen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Abstract and Resource controllers
On Thu, Jan 29, 2009 at 1:13 AM, Andrew Neil wrote: > I would appreciate if anyone can take the time to step through the latest > version of the tutorial, using Radiant 0.7 (edge, not rc2), and let me know > if everything works as it should. I'm rereading the tutorial atm, and the first thing I've noticed is that the text uses "I" and "my" in several places in the first paragraph. I think it is written from the 'radiant author' perspective? Maybe a couple of "we" instead of "I" will make it a little 'easier' to read (but opinions may differ). The first screenshot showing the "Extensions" link does not match the 'current' one (the Archive extension is present by default aswell). And as a result the text below (about the two default extensions isn't correct anymore). When generating a new model, the migration file is generated based upon the UTC date/time (this is new in rails 2.1). I don't know if we want to mention that, but as a result the migration file will not be called "001*". The erb files at the end of part1: * Edit view is for link_roll/app/views/admin/links/edit.html.erb (edit instead of new) * Form view (partial) is missing filename (should be link_roll/app/views/admin/links/_form.html.erb ) Apart from these small items, everything looks ok and I got a working link roll extension at the end of the walkthrough. What I can see from the "generated" output is that so far only the 'route' section is out of date (in the generator). I'll make a small patch to the generator template to use the rest routing by default (commented out ofcourse). Jeroen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] How to check out the 0.6.9 branch?
Hi Simon, "git clone" will clone the radiant repository, and put you in the current 'master' (0.7.0) tree. "git checkout -b" will actually create a new branch based upon your current working tree (so you actually created a 'new' branch there) instead of checking out the 0.6.9 'tag'. Jeroen On Wed, Jan 28, 2009 at 3:54 PM, Simon Rönnqvist wrote: > Hi! > > I'm installing a new Rails site, and since I need the multi-site extension > I'm unable to use 0.7.0 yet. I tried checking out the 0.6.9 branch by doing > this: > > git clone git://github.com/radiant/radiant.git > git checkout -b 0.6.9 > > But once Radiant is up 'n running it says "This site was made with Ruby and > is powered by Radiant CMS version 0.7.0." in the footer. How do I check out > the 0.6.9 branch? > > cheers, Simon > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Abstract and Resource controllers
On Tue, Jan 27, 2009 at 11:15 PM, Andrew Neil wrote: > I've forked the link_roll extension, and made it play with Radiant 0.7.0. Fantastic! > An alternative would be to create a new page for the tutorial. My preference > would be to update the current article for 0.7, then create a new page > called "Creating Radiant Extensions (pre-0.7)", and copy the current state > of the tutorial into that one. The existing tutorial has quite a lot of > links pointing at it, and I think it would be better to keep the article at > that URL the most current. > > Any thoughts on the issue? I think it would be good to have a "0.7" section on the wiki, so people can actually see what (documentation) has been updated and checked to be working with 0.7. Else they might start using 'pre-0.7' documentation and finding all sorts of things not working (and that might be confusing). Maybe also a 'migration guide' / 'howto' on what you need to change in your pre 0.7 extension to get it working with 0.7 would be cool (since you figured out how to do that now ;) On a side note, I'll have a try and update the radiant/lib/generators/extension* code to match the 0.7 behaviour (i.e. use admin.resources in the define_resources section of generate extension, etc). Jeroen Janssen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant edge doesn't load admin section?
On Tue, Jan 27, 2009 at 5:52 AM, Sean Cribbs wrote: > I've pushed some changes that should alleviate this issue. Thanks to Jeroen > for getting the ball rolling on the integration specs. Hi Sean, Thank you for solving this issue (I can confirm it works on IE now aswell) Jeroen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can we still take a look at the admin side of the Roasters theme?
The roasters website is up at http://contest2.radiantcms.org The admin site should be http://contest2.radiantcms.org/admin , but I can't remember the login information. On Mon, Jan 26, 2009 at 9:00 PM, Nate Turnage wrote: > I need to do some work with google maps and the Roasters theme, according to > the theme contest winner post, apparently had used them. I'd like to take a > look at how that was accomplished. On the blog it says "Feel free to peruse > both the front-end and the admin sections of each site via the links in the > top frame..." but I did not see any links to even look at the sites. > > Can anybody tell me how I can view that Roasters site that was being judged? > > > > Thanks, > > ~Nate > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] tags extension
Hi, I think the extension needs to be installed in the "vendor/extensions/tags" directory if I understand correctly. Best regards, Jeroen Janssen On Mon, Jan 19, 2009 at 11:03 PM, Steven Southard wrote: > I tried installing Jomz's tags extension using: > > git clone git://github.com/jomz/radiant-tags-extension.git > vendor/extensions/tag > rake production radiant:extensions:tags:install > > and it seemed to install fine except I get: > > `tag_field' default partial not found! on any page > > I was wondering if I should change the tag_field.html.erb file name, maybe? > > Am I missing something else? > > > > Steven > > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] freeze:edge, github & http urls?
Hi, I just noticed that rake radiant:freeze:edge uses the git:// url syntax rather then a http:// git url syntax. As a result of this, when you're behind a corporate firewall that only allows http, git won't be able to fetch a repository. I can check out 'http' based git repositories without any problems I manually changed the radiant/lib/tasks/framework.rake "radiant_git" variable to "http://github.com/radiant/radiant.git";, but I was wondering if there was a generic way to deal with this. Best regards, Jeroen Janssen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] So how did things go this weekend?
On Tue, Oct 28, 2008 at 5:53 AM, Sean Cribbs <[EMAIL PROTECTED]> wrote: > The primary goal I had for this weekend was to make headway on a > refactoring of the admin interface toward a conventional RESTful design. > These changes will be rolled into the 0.6.10 release to give time for > developers to update their extensions before 0.7. Hi, I was wondering what items are still remaining left for a 0.6.10 release (i.e. is it the list at http://radiant.lighthouseapp.com/projects/11883-radiant/milestones/current?) I'm about to setup a new radiantcms based project and was wondering what would be my best 'starting' point. Should I stick with the 0.6.9 release for now? Best regards, Jeroen Janssen ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Page Event Extension Alpha release
Hey, This looks very cool indeed... I will definitely have a look at using this for my band website. Best regards, Jeroen Janssen On Sun, May 4, 2008 at 7:08 AM, Marty Haught <[EMAIL PROTECTED]> wrote: > Hi everyone, > > I have finally got the initial release of my page event extension > together. This extension has been on the drawing board for quite some > time and it seemed that other things kept popping up pulling my > attention away from finishing the extension. > > So what is this extension? In a nutshell, it allows someone to set an > event date and time to a page. It comes with a monthly calendar tag > that will display all events for the given month. Thus if you create > pages that represent some event on your site (like user group > meetings), you can now have the date and time be expressed in its > native format as well as have them all show up on a site-wide > calendar. > > You can find the extension on github: > > http://github.com/mghaught/radiant-page-event/tree/master > > I made a post on my blog that contains more details, installation and > usage notes on the extension so instead of typing it all over again, > just go over and read up if you're interested: > > http://martyhaught.com/articles/2008/05/03/page-event-extension-released > > This is an alpha release so who knows what sort of bugs or missing > features are lurking about. I will be using it on at least two sites > so it should become decently tested in the next month as I get more > use out of it. Feedback welcome. > > Cheers, > Marty Haught > ___ > Radiant mailing list > Post: Radiant@radiantcms.org > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
