Re: [Radiant] Main Menu/Content available to logged-in members only

2011-06-21 Thread Wesley Gamble
There is a fragment_cacher extension that works quite well. Wes Sent from my iPhone On Jun 21, 2011, at 6:25 PM, "gibbererfly...@yahoo.com" wrote: > Hello, I am currently trying to add in some functionality to a Radiant > based site and am having no luck. Essentially, on the public side, if >

[Radiant] Re: Howto integrate Radiant in existing application

2011-06-21 Thread Cleverlemming
> Maybe there is a way to have such custom tags containing content from > the existing app when I try to set up solution 2) ? Anything's possible in Rails: http://www.paultastic.com/showpage/Grabbing-Data-From-Foreign-Database-Using-Rails http://railsforum.com/viewtopic.php?id=24338 (just the fi

[Radiant] Re: Main Menu/Content available to logged-in members only

2011-06-21 Thread Mel
To get around the caching issue we use javascript to insert Members only content on Radiant pages, it's not always ideal to be inserting content with javascript but it works and if we want a fallback for non js users we might have a link to a member area (that the js insert replaces) which will red

[Radiant] Main Menu/Content available to logged-in members only

2011-06-21 Thread gibbererfly...@yahoo.com
Hello, I am currently trying to add in some functionality to a Radiant based site and am having no luck. Essentially, on the public side, if a member logs in, they should have content displayed just for them (so, for example, the main menu would display members only links). I have the login workin

[Radiant] Re: Howto integrate Radiant in existing application

2011-06-21 Thread Abder Rachman
Hello Jim (and all), thank you for the answers. I also would like to go your 4th way. But I am afraid I have to choose 1) or 2) as I need to get this run within the next few days. What details would you like to know? There is for example a list of persons that needs to be displayed inside radiant

Re: [Radiant] Upgrade Path

2011-06-21 Thread Wes Gamble
You use bundler with Rails 2.3.x (http://gembundler.com/rails23.html), if you're just worried about bundler stuff. In Rails 2.3.11, you don't need to modify boot.rb as per the instructions above, just add the config/preinitializer.rb file and you should be good to go. It'll be ok. Wes O

[Radiant] Ace extension

2011-06-21 Thread Tom Brooke
I tried the Ace editor extension - in 1.0 rc2 and it installs fine and appears to work with layouts but I couldn't get it to work with anything else - Anyone tried this?

[Radiant] Upgrade Path

2011-06-21 Thread Walter Lee Davis
If I start a project today with the current stable (0.9.x) version, what would my upgrade path look like when 1.0 is released for real? In Rails 3, I would just update my bundle, but with 2.3.x, it's not nearly that clean in my limited experience. Can anyone pat me on the shoulder and say -

[Radiant] Re: Gems, migrations, and updates

2011-06-21 Thread Michael Stalker
Sorry for that last post appearing twice. I'm not sure why it did that... On Jun 21, 11:37 am, Michael Stalker wrote: > Ah, it's possible that the gemified extension I was looking at hadn't > added the extra rake task that does the copying. rake -T hadn't shown > any rake tasks for that gem. I co

[Radiant] Re: Gems, migrations, and updates

2011-06-21 Thread Michael Stalker
Ah, it's possible that the gemified extension I was looking at hadn't added the extra rake task that does the copying. rake -T hadn't shown any rake tasks for that gem. I could have missed them, I suppose. Thanks, Benny! -Michael On Jun 21, 11:08 am, Benny Degezelle wrote: > Gemified extensions

Re: [Radiant] Page Reordering

2011-06-21 Thread Jim Gay
On Tue, Jun 21, 2011 at 11:02 AM, Bob Sleys wrote: > not a problem. works great now. > One thing I did notice is when reordering from the root page there is a page > listed as css that isn't part of the normal tree view.  I guess it's a > hidden page that normally gets filtered out on the page tre

Re: [Radiant] Re: Gems, migrations, and updates

2011-06-21 Thread Joel Oliveira
This is a recent development with the extensions moving into gems. I've found that the common way to take care of this is to run the following tasks: $ rake radiant:extensions:update_all $ rake db:migrate:extensions That'll run them all. - Joel On Tue, Jun 21, 2011 at 11:08 AM, Benny Degezelle

[Radiant] Re: Gems, migrations, and updates

2011-06-21 Thread Michael Stalker
Ah, it's possible that the gemified extension I was looking at hadn't added the extra rake task that does the copying. rake -T hadn't shown any rake tasks for that gem. I could have missed them, I suppose. Thanks, Benny! -Michael On Jun 21, 11:08 am, Benny Degezelle wrote: > Gemified extensions

Re: [Radiant] Re: Gems, migrations, and updates

2011-06-21 Thread Benny Degezelle
Gemified extensions should have an extra rake task that copies their rake tasks to the project's lib/tasks/. So; - add an extension gem to config/environment.rb - run rake radiant:extensions:update_all - run rake db:migrate:extensions or rake radiant:gemmified_extension:migrate (the rake task will

Re: [Radiant] Page Reordering

2011-06-21 Thread Bob Sleys
not a problem. works great now. One thing I did notice is when reordering from the root page there is a page listed as css that isn't part of the normal tree view. I guess it's a hidden page that normally gets filtered out on the page tree view. Not a big deal IMHO. Both extensions work perf

Re: [Radiant] Page Reordering

2011-06-21 Thread Benny Degezelle
gah! sorry.. the "migrate_from" will only run on Radiant edge I'm afraid. If you could, just comment that line, see https://github.com/jomz/radiant-reorder_children-extension/commit/578645d81718665267e6976986f46a2ae7ee7bfd 2011/6/21 Bob Sleys > getting an error running the migration for the reo

Re: [Radiant] Page Reordering

2011-06-21 Thread Bob Sleys
getting an error running the migration for the reorder_children extension. rake radiant:extensions:reorder_children:migrate --trace (in /home/bsleys/projects/ooo-web) ** Invoke radiant:extensions:reorder_children:migrate (first_time) ** Invoke environment (first_time) ** Execute environment Could

[Radiant] Re: Gems, migrations, and updates

2011-06-21 Thread Michael Stalker
I've been copying my local JavaScript and CSS and pasting it in the remote site when I set up a Radiant site. That's not exactly automated, I know, but it doesn't take long for me. When I deploy a Radiant site, I've already done my asset updates and migrations locally, so all that work get deploye

[Radiant] Re: Mailer extension error when submitting form

2011-06-21 Thread JT
Through a process of elimination, I've narrowed this down to two issues. The "undefined method..." error seems to be related purely with the form validation functionality. If I leave any of the required fields blank when submitting the form, the error appears when the page reloads. For now I've ju

Re: [Radiant] errors with clean install of radiant 1.0.0.RC2

2011-06-21 Thread Bob Sleys
Thanks guys adding the require statements fixed it for now. Bob

Re: [Radiant] Page Reordering

2011-06-21 Thread Bob Sleys
Very nice. I took a quick look through the code and missed that. Thanks Bob

Re: [Radiant] Gems, migrations, and updates

2011-06-21 Thread tom . brooke
I am working with deploying Radiant now and I am also curious in this area. I noticed in the extension registry a capistrano extension aimed at updating assets etc. that might be an answer. I would appreciate suggestions re deployment. I am concerned about workflow since I want to develop m

Re: [Radiant] Page Reordering

2011-06-21 Thread Benny Degezelle
in fact, you can add a 'no-map' part to a page to exclude it. When I find the time, I'll also make it look for a no-map page-field, that'd be cleaner.. 2011/6/21 Bob Sleys > Thanks, > > I'll give those a try. The navagation_tags looks very nice, though I think > I'll have to tweak it to add an

Re: [Radiant] errors with clean install of radiant 1.0.0.RC2

2011-06-21 Thread Joel Oliveira
Hey Bob - I ran into this as well. For some reason the gems pulled in via config.gem aren't getting required for the RC2 release (which is super weird) The quickest way to fix this, in my experience, was to just add the following to a file in config/initializers/ require 'acts_as_list' require

Re: [Radiant] errors with clean install of radiant 1.0.0.RC2

2011-06-21 Thread William Ross
Hi Bob, Thanks for the report. This is a curious and intermittent problem that has a github issue in the clipped extension. I think it's fixed now that we're offloading nearly everything into gems, but that work is in progress at the moment so I can't quite tell yet. I may well vendor acts_as_

[Radiant] errors with clean install of radiant 1.0.0.RC2

2011-06-21 Thread Bob Sleys
I've installed radiant 1.0.0.rc2 into a clean RVM setup with an empty gemset running ruby 1.8.7. Installing radaint (gem install radiant --prerelease) yielded the following installed gems *** LOCAL GEMS *** activemodel (3.0.9) activerecord (3.0.9) activesupport (3.0.9) acts_as_list (0.1.3) are

[Radiant] Gems, migrations, and updates

2011-06-21 Thread Michael Stalker
It seems like some people are gemifying their Radiant extensions, but it's not clear to me what is the best way to run their migrations and asset updates. Is there a standard way to handle that? I could install the extension, run the migrations and updates, uninstall the extension, and then use the

Re: [Radiant] Page Reordering

2011-06-21 Thread Bob Sleys
Thanks, I'll give those a try. The navagation_tags looks very nice, though I think I'll have to tweak it to add an option to ignore certain pages. Say if the page has a page part of no-nav ignore it and it's children. But otherwise it looks to be exactly what I end up building via 2 snippets

Re: [Radiant] Page Reordering

2011-06-21 Thread Benny Degezelle
hi Bob, I recently re-packaged the "old" reorder extension; the one where you have a reorder button for every page with children; https://github.com/jomz/radiant-reorder_children-extension This works well with edge, and is also available as a gem. About automatic menu generation; I dò agree with