Re: [Radiant] [ANN] Radiant 0.9.0 RC1

[John W . Long]

On Oct 12, 2009, at 1:26 PM, Anton Aylward wrote:

Ah.  about 50 pages more than I wanted.


learn.github.com looks like your ticket:

  http://learn.github.com/p/intro.html
  http://learn.github.com/p/setup.html
  http://learn.github.com/p/normal.html
  http://learn.github.com/p/branching.html

Also check out:

  http://www.gitready.com/

For additional tips and tricks:

  http://www.gitready.com/beginner/2009/01/27/installing-git.html
  http://www.gitready.com/intermediate/2009/01/24/sharing-your-changes.html
  http://www.gitready.com/beginner/2009/01/21/pushing-and-pulling.html
  http://www.gitready.com/beginner/2009/01/18/the-staging-area.html

--
John Long
http://wiseheartdesign.com
http://recursivecreative.com
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: Git Confusion - thread detour from "[Radiant] [ANN] Radiant 0.9.0 RC1"

[Nate Turnage]

On Mon, Oct 12, 2009 at 3:35 PM, john muhl  wrote:


> i've found the following to be pretty easy to use once it's setup.
>
> - clone the latest radiant source to somewhere in your home directory;
> i use ~/.radiant
>
> git clone git://github.com/radiant/radiant.git ~/.radiant
>
> - add aliases to your ~/.bashrc file (or ~/.profile or whatever) such as:
>



That's insanely cool if you don't use the gem. I might switch to doing it
that way. If you don't mind, I may use that in my tutes.


~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: Git Confusion - thread detour from "[Radiant] [ANN] Radiant 0.9.0 RC1"

[john muhl]

oh and once you've created a radiant from an older version (or edge)
you probably want to freeze it with `rake radiant:freeze:edge
TAG=0.7.1` or whatever

On Mon, Oct 12, 2009 at 3:35 PM, john muhl  wrote:
> On Mon, Oct 12, 2009 at 3:02 PM, Nate Turnage  wrote:
>> On Mon, Oct 12, 2009 at 2:45 PM, Dayne Broderson 
>> wrote:
>>> [dbrod...@beef ~]$ gem environment
>>> ...
>>> [dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0.
>>> radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/
>>> [dbrod...@beef ~]$
>>> /usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant
>>
>> That's pretty easy? :^O
>>
>> I guess it's not that difficult, but I could have sworn there was an easier
>> way. Something like this:
>> radiant -v=0.7.1 --database [mysql] project
>>
>> That of course doesn't work, but I thought there was something easy like
>> that. I could be wrong, probably am.
>
> i've found the following to be pretty easy to use once it's setup.
>
> - clone the latest radiant source to somewhere in your home directory;
> i use ~/.radiant
>
> git clone git://github.com/radiant/radiant.git ~/.radiant
>
> - add aliases to your ~/.bashrc file (or ~/.profile or whatever) such as:
>
> alias radiant-0.6.8="PWD=`pwd` && cd ~/.radiant && git checkout -q
> 0.6.8 && cd $PWD && ~/.radiant/bin/radiant"
> alias radiant-0.6.9="PWD=`pwd` && cd ~/.radiant && git checkout -q
> 0.6.9 && cd $PWD && ~/.radiant/bin/radiant"
> alias radiant-0.7.0="PWD=`pwd` && cd ~/.radiant && git checkout -q
> 0.7.0 && cd $PWD && ~/.radiant/bin/radiant"
> alias radiant-0.7.1="PWD=`pwd` && cd ~/.radiant && git checkout -q
> 0.7.1 && cd $PWD && ~/.radiant/bin/radiant"
> alias radiant-0.8.0="PWD=`pwd` && cd ~/.radiant && git checkout -q
> 0.8.0 && cd $PWD && ~/.radiant/bin/radiant"
> alias radiant-0.8.1="PWD=`pwd` && cd ~/.radiant && git checkout -q
> 0.8.1 && cd $PWD && ~/.radiant/bin/radiant"
> alias radiant-edge="PWD=`pwd` && cd ~/.radiant && git checkout -q
> master && cd $PWD && ~/.radiant/bin/radiant"
>
> (http://gist.github.com/208708 in case the mailing list mangles the
> line endings)
>
> - reload your .bashrc (or .profile or whatever you edited); i.e.
> `source ~/.bashrc`
>
> you can test them by running commands like `radiant-0.7.1 --version`
> and `radiant-0.8.1 --version`
>
> you may see errors having to do with submodules but those are harmless
> for the use of simply being able to generate new sites from any
> version of radiant.
>
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: Git Confusion - thread detour from "[Radiant] [ANN] Radiant 0.9.0 RC1"

[john muhl]

On Mon, Oct 12, 2009 at 3:02 PM, Nate Turnage  wrote:
> On Mon, Oct 12, 2009 at 2:45 PM, Dayne Broderson wrote:
>> [dbrod...@beef ~]$ gem environment
>> ...
>> [dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0.
>> radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/
>> [dbrod...@beef ~]$
>> /usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant
>
> That's pretty easy? :^O
>
> I guess it's not that difficult, but I could have sworn there was an easier
> way. Something like this:
> radiant -v=0.7.1 --database [mysql] project
>
> That of course doesn't work, but I thought there was something easy like
> that. I could be wrong, probably am.

i've found the following to be pretty easy to use once it's setup.

- clone the latest radiant source to somewhere in your home directory;
i use ~/.radiant

git clone git://github.com/radiant/radiant.git ~/.radiant

- add aliases to your ~/.bashrc file (or ~/.profile or whatever) such as:

alias radiant-0.6.8="PWD=`pwd` && cd ~/.radiant && git checkout -q
0.6.8 && cd $PWD && ~/.radiant/bin/radiant"
alias radiant-0.6.9="PWD=`pwd` && cd ~/.radiant && git checkout -q
0.6.9 && cd $PWD && ~/.radiant/bin/radiant"
alias radiant-0.7.0="PWD=`pwd` && cd ~/.radiant && git checkout -q
0.7.0 && cd $PWD && ~/.radiant/bin/radiant"
alias radiant-0.7.1="PWD=`pwd` && cd ~/.radiant && git checkout -q
0.7.1 && cd $PWD && ~/.radiant/bin/radiant"
alias radiant-0.8.0="PWD=`pwd` && cd ~/.radiant && git checkout -q
0.8.0 && cd $PWD && ~/.radiant/bin/radiant"
alias radiant-0.8.1="PWD=`pwd` && cd ~/.radiant && git checkout -q
0.8.1 && cd $PWD && ~/.radiant/bin/radiant"
alias radiant-edge="PWD=`pwd` && cd ~/.radiant && git checkout -q
master && cd $PWD && ~/.radiant/bin/radiant"

(http://gist.github.com/208708 in case the mailing list mangles the
line endings)

- reload your .bashrc (or .profile or whatever you edited); i.e.
`source ~/.bashrc`

you can test them by running commands like `radiant-0.7.1 --version`
and `radiant-0.8.1 --version`

you may see errors having to do with submodules but those are harmless
for the use of simply being able to generate new sites from any
version of radiant.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: Git Confusion - thread detour from "[Radiant] [ANN] Radiant 0.9.0 RC1"

[Nate Turnage]

On Mon, Oct 12, 2009 at 2:45 PM, Dayne Broderson wrote:

>
> Ahh, that is actually pretty easy.  Just ask gem where you're gems are
> installed.  You can find that from 'gem environment' and looking at
> GEM_PATHS.   Mine is typically /usr/local/lib/ruby/gems/1.8.   In that
> directory is another gems directory with inside that each of your installed
> gems.  If you have a few radiants installed they will be hanging out there.
> Use the explicit path to the version of radiant you want.  Pasted below is
> the series of commands from my box if I were interested in a 0.7.1 install:
>
> [dbrod...@beef ~]$ gem environment
> RubyGems Environment:
>  - RUBYGEMS VERSION: 1.3.5
>  - RUBY VERSION: 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]
>  - INSTALLATION DIRECTORY: /home/dbroders/usr/gems
>  - RUBY EXECUTABLE: /usr/local//bin/ruby
>  - EXECUTABLE DIRECTORY: /home/dbroders/usr/gems/bin
>  - RUBYGEMS PLATFORMS:
>- ruby
>- x86_64-linux
>  - GEM PATHS:
> *- /usr/local/lib/ruby/gems/1.8*
>  - GEM CONFIGURATION:
> - :update_sources => true
> - :verbose => true
> - :benchmark => false
> - :backtrace => false
> - :bulk_threshold => 1000
>  - REMOTE SOURCES:
> - http://gems.rubyforge.org/
> [dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0.
> radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/
> [dbrod...@beef ~]$
> /usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant
>
>
That's pretty easy? :^O

I guess it's not that difficult, but I could have sworn there was an easier
way. Something like this:
radiant -v=0.7.1 --database [mysql] project

That of course doesn't work, but I thought there was something easy like
that. I could be wrong, probably am.


~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: Git Confusion - thread detour from "[Radiant] [ANN] Radiant 0.9.0 RC1"

[Dayne Broderson]

On Mon, Oct 12, 2009 at 10:19 AM, Nate Turnage  wrote:

>
> 

>
> What I am not certain on is how you *create* a Radiant project using a
> specific version of the gem. If anyone could chime in here it would be
> great. I didn't see it mentioned in the wiki either.
>
> 

>
> ~Nate


Ahh, that is actually pretty easy.  Just ask gem where you're gems are
installed.  You can find that from 'gem environment' and looking at
GEM_PATHS.   Mine is typically /usr/local/lib/ruby/gems/1.8.   In that
directory is another gems directory with inside that each of your installed
gems.  If you have a few radiants installed they will be hanging out there.
Use the explicit path to the version of radiant you want.  Pasted below is
the series of commands from my box if I were interested in a 0.7.1 install:

[dbrod...@beef ~]$ gem environment
RubyGems Environment:
  - RUBYGEMS VERSION: 1.3.5
  - RUBY VERSION: 1.8.7 (2008-05-31 patchlevel 0) [x86_64-linux]
  - INSTALLATION DIRECTORY: /home/dbroders/usr/gems
  - RUBY EXECUTABLE: /usr/local//bin/ruby
  - EXECUTABLE DIRECTORY: /home/dbroders/usr/gems/bin
  - RUBYGEMS PLATFORMS:
- ruby
- x86_64-linux
  - GEM PATHS:
 *- /usr/local/lib/ruby/gems/1.8*
  - GEM CONFIGURATION:
 - :update_sources => true
 - :verbose => true
 - :benchmark => false
 - :backtrace => false
 - :bulk_threshold => 1000
  - REMOTE SOURCES:
 - http://gems.rubyforge.org/
[dbrod...@beef ~]$ /usr/local/lib/ruby/gems/1.8/gems/radiant-0.
radiant-0.6.9/ radiant-0.7.0/ radiant-0.7.1/ radiant-0.8.1/
[dbrod...@beef ~]$
/usr/local//ib/ruby/gems/1.8/gems/radiant-0.7.1/bin/radiant


-dayne
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Question about Radiant_Rbiz extension

[nx]

Nate,

I just posted up my rbiz_donations plugin that allows you to make
donations through Rbiz. Its in what I would call an infantile stage,
but it works. If you want to try it out see the README at:
http://github.com/nuex/radiant_rbiz_donations.

I also just finished a pledge system so customers can donate in the
name of an existing cause or create a new one. Its at
http://github.com/nuex/radiant_rbiz_donations_pledge_system and
requires rbiz_donations and rbiz_donations_pledge_system.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Git Confusion - thread detour from "[Radiant] [ANN] Radiant 0.9.0 RC1"

[Nate Turnage]

On Mon, Oct 12, 2009 at 12:26 PM, Anton Aylward wrote:

> Arthur Gunn said the following on 10/12/2009 08:24 AM:
> >> Perhaps, then, you can suggest a source of "How To" for GIT for
> >> non-developers.
> >
> > There are no end of resources out there, my personal recommendation
> > though:
> >   
> > http://www-cs-students.stanford.edu/~blynn/gitmagic/
>
> Ah.  about 50 pages more than I wanted.
> Telling me all the things that as a non-developer I don't need to know
> about, and not answering fundamental questions like "when do I have to
> worry about a 'module' or 'submodule'" and "how can I keep from geting
> an update from 0.9 when I've got a 0.6.9 based application" or vice
> versa, and "what if I'm using 0.9 and I try to ... clone? ... an
> extension that hasn't a 0.9 revision now but will have in the future"?
>
> I'm sure I'm not the only person on this list who has questions like that.
>


I can assure you that you are not. I am also come from a 'non-developer'
background (wishing I had gotten that CS degree, though) and I blazed the
git trail myself back in January when I moved a project from 0.6.9 to 0.7.0.
There is a lot to learn, especially if you haven't worked with source
control before.

I tell ya what, I have been meaning to resurrect/rebuild my long dormant
blog and I'll make that the first topic. If you can give me a few days I'll
compile a short "Newbies guide to Git and Radiant" describing my whole
development process. It's something I promised to do a long time ago and
never had the time.

In the meantime, if you have any specific questions about the process,
please ask them. So far I see the git-related questions are:
- What are submodules? Which is really a question about how to install
extensions when your project is managed with git and is related to using
Ray.
- How can I make sure the extension I am using will work with my project
running v.X.X.X?

This isn't a git question that I intend to cover because I think it is in
the wiki already, but I'll answer it here:
- How can I install newer gem versions of Radiant but stay with 0.6.9 on
this project?

By default, Radiant will try and use the latest version of the gem that you
have installed. To use a specific version of Radiant, go into environment
file (config/environment.rb) and add this line under the "require 'radius'"
line (substitute your version for 0.8.1):
RADIANT_GEM_VERSION = '0.8.1'
Then save the file and restart the server.

What I am not certain on is how you *create* a Radiant project using a
specific version of the gem. If anyone could chime in here it would be
great. I didn't see it mentioned in the wiki either.

I hope that clears up some part of your confusion, Arthur. Like I said, I'll
get to the git 'splaining shortly. I know what it's like to have a developer
point you to a source of info chock-full of stuff that you don't understand
when you ask what seems like a simple question.



~Nate
___
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] Radiant 0.9.0 RC1

[Anton Aylward]

Arthur Gunn said the following on 10/12/2009 08:24 AM:
>> Perhaps, then, you can suggest a source of "How To" for GIT for
>> non-developers.
> 
> There are no end of resources out there, my personal recommendation  
> though:
>   http://www-cs-students.stanford.edu/~blynn/gitmagic/

Ah.  about 50 pages more than I wanted.
Telling me all the things that as a non-developer I don't need to know
about, and not answering fundamental questions like "when do I have to
worry about a 'module' or 'submodule'" and "how can I keep from geting
an update from 0.9 when I've got a 0.6.9 based application" or vice
versa, and "what if I'm using 0.9 and I try to ... clone? ... an
extension that hasn't a 0.9 revision now but will have in the future"?

I'm sure I'm not the only person on this list who has questions like that.

-- 
The state is made for man, not man for the state That is to say the
state should be our servant and not we its slaves.
--Albert Einstein
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Restricting access to select pages

[Nate Turnage]

On Mon, Oct 12, 2009 at 11:44 AM, James Britt  wrote:

> Hey all.
>
> I'm setting up a Radiant site, and in addition to having to add some custom
> behavior, I need to be able to restrict access to specific pages for
> different users.
>
> I've started trying p8's Restricted Access extension (
> http://github.com/p8/radiant-restricted-access-extension) but wondered if
> there was something else folks would recommend.
>
>
That extension looks awesome. I had no idea that something like this existed
for Radiant.


~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] Restricting access to select pages

[James Britt]

Hey all.

I'm setting up a Radiant site, and in addition to having to add some 
custom behavior, I need to be able to restrict access to specific pages 
for different users.


I've started trying p8's Restricted Access extension 
(http://github.com/p8/radiant-restricted-access-extension) but wondered 
if there was something else folks would recommend.


Thanks,


James Britt



--

Neurogami - Smart application development

http://www.neurogami.com

ja...@neurogami.com




___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Fwd: Re: [Radiant] the error on rake command]

[Nate Turnage]

On Mon, Oct 12, 2009 at 10:09 AM, fredmann wonder wrote:

>
>
> of course i have installed the cucumber gem.
>


Well then. I dunno. I just installed the gem, and bootstrapped a mysql db
without any problem.

Do you have the 0.8.1 gem installed? I got a bunch of gem dependencies
installed when I upgraded to v0.8.x.

On OSX.5.x.




~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Fwd: [Fwd: Re: [Radiant] the error on rake command]

[fredmann wonder]

fredmann wonder wrote:
> hi!
>
> After I installed the RC1 of 0.9.0 version, I build a new project, but
when
> i run "rake production db:bootstrap" command , their comeout the error
> message:
>
> "rake aborted!
> undefined method `feature_pattern=' for #
> /home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:13
>
/home/fredmann/.gem/ruby/1.8/gems/cucumber-0.4.0/lib/cucumber/rake/task.rb:127:in
> `initialize'
>
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:7:in
> `new'
> /home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:7
>
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
> `load_without_new_constant_marking'
>
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
> `load'
>
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in
> `new_constants_in'
>
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
> `load'
> /home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10
> /home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10:in `each'
> /home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1620:in `load'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1620:in `load'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2451:in `load_imports'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2390:in
> `raw_load_rakefile'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2017:in `load_rakefile'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2000:in `run'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
> /usr/local/bin/rake:31
> "
> I find that 0.9.0 have a new plugin "cucumber" in /vendor/plugins, but i
do
> not know why, so , can you help me?
>
> fredmannsz
>
> 2009-09-12
> __


Do you have the cucumber gem installed?


~Nate


of course i have installed the cucumber gem.

fredmann
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] the error on rake command

[Nate]

fredmann wonder wrote:

hi!

After I installed the RC1 of 0.9.0 version, I build a new project, but when
i run "rake production db:bootstrap" command , their comeout the error
message:

"rake aborted!
undefined method `feature_pattern=' for #
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:13
/home/fredmann/.gem/ruby/1.8/gems/cucumber-0.4.0/lib/cucumber/rake/task.rb:127:in
`initialize'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:7:in
`new'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:7
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
`load_without_new_constant_marking'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
`load'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in
`new_constants_in'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
`load'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10:in `each'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1620:in `load'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1620:in `load'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2451:in `load_imports'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2390:in
`raw_load_rakefile'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2017:in `load_rakefile'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2000:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/usr/local/bin/rake:31
"
I find that 0.9.0 have a new plugin "cucumber" in /vendor/plugins, but i do
not know why, so , can you help me?

fredmannsz

2009-09-12
__



Do you have the cucumber gem installed?


~Nate
___
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 0.9.0 RC1 & Extensions

[Nate]

Sharon Clift wrote:

We use the old version of page attachments.  How do we go about
upgrading page attachments to the newest version without losing all of
the images on our site?  


I couldn't find any documentation on how to upgrade the attachments and
I assume our version will break with 0.9.0?
  


As it is an RC1 release it probably shouldn't be used on a production 
site. If you haven't upgraded to 0.8.1 I suggest doing that first. I 
have a feeling it will be a little while before the extension 
maintainers will get all the useful extensions upgraded for 0.9.


The upgrade path for extensions is different for different people, as 
well. Is your project managed with any kind of source control mechanism 
(subversion, git, etc.)? Since I manage my projects with git, with all 
my extensions added as submodules, it goes something like this for me:



> cd vendor/extensions/page_attachments

> git pull

> cd ../../..

> git submodule init && git submodule update

> rake radiant:extensions:page_attachments:migrate

> rake radiant:extensions:page_attachments:update

> git add *

> git commit -m "..."

> git push

> cap deploy


Then ssh into the server and migrate the extension there. Or depending 
on the situation (major update vs. minor one) I'll export the mysql db 
and import the development db into my production one. Not sure it's 
exactly "best practice" to do it that way, but that's how I do it now.




~Nate
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] Radiant 0.9.0 RC1 & Extensions

[Sharon Clift]

We use the old version of page attachments.  How do we go about
upgrading page attachments to the newest version without losing all of
the images on our site?  

I couldn't find any documentation on how to upgrade the attachments and
I assume our version will break with 0.9.0?

Many thanks for any assistance 

Sharon 

--

Message: 1
Date: Sun, 11 Oct 2009 18:09:36 -0400
From: "John W. Long" 
Subject: Re: [Radiant] [ANN] Radiant 0.9.0 RC1
To: radiant@radiantcms.org
Message-ID: 
Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes

On Oct 11, 2009, at 7:23 AM, Anton Aylward wrote:
> John W. Long said the following on 10/09/2009 10:21 PM:
>> [...] We want to
>> encourage all extension developers to update their extensions to work
>> with 0.9.0 as the interface changes in this release are significant
>> and will break existing extensions.
>
> Which leads to my first question.
> What testing with extension did you do in order to come up with that
> observation?  You obviously know some extensions break, but which  
> ones?
> And which ones DO work?

A lot of extensions depend on Javascript and CSS that is no longer  
present in 0.9. This is where I expect most breakage will occur. I  
upgraded the page attachments extension recently and discovered this.

Also, since there are now two levels of tabs, extensions that add tabs  
should rethink where they belong in the interface.

--
John Long
http://wiseheartdesign.com
http://recursivecreative.com



This e-mail has been scanned for all viruses by MessageLabs.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] the error on rake command

[fredmann wonder]

hi!

After I installed the RC1 of 0.9.0 version, I build a new project, but when
i run "rake production db:bootstrap" command , their comeout the error
message:

"rake aborted!
undefined method `feature_pattern=' for #
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:13
/home/fredmann/.gem/ruby/1.8/gems/cucumber-0.4.0/lib/cucumber/rake/task.rb:127:in
`initialize'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:7:in
`new'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/lib/tasks/cucumber.rake:7
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
`load_without_new_constant_marking'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
`load'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:521:in
`new_constants_in'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/vendor/rails/activesupport/lib/active_support/dependencies.rb:145:in
`load'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10:in `each'
/home/fredmann/.gem/ruby/1.8/gems/radiant-0.9.0/Rakefile:10
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1620:in `load'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1620:in `load'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2451:in `load_imports'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2390:in
`raw_load_rakefile'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2017:in `load_rakefile'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2016:in `load_rakefile'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2000:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
/usr/local/bin/rake:31
"
I find that 0.9.0 have a new plugin "cucumber" in /vendor/plugins, but i do
not know why, so , can you help me?

fredmannsz

2009-09-12
___
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] Radiant 0.9.0 RC1

[qutic development]

This one is pretty easy: http://progit.org/book/

Best regards
jerry

On 12.10.2009, at 14:20, Anton Aylward wrote:


Perhaps, then, you can suggest a source of "How To" for GIT for
non-developers.


___
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] Radiant 0.9.0 RC1

[Arthur Gunn]

Perhaps, then, you can suggest a source of "How To" for GIT for
non-developers.


There are no end of resources out there, my personal recommendation  
though:

http://www-cs-students.stanford.edu/~blynn/gitmagic/


-Arthur

___
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] Radiant 0.9.0 RC1

[Anton Aylward]

Nate said the following on 10/11/2009 10:38 PM:

>> Anton Aylward said the following on 10/11/2009 07:23 AM:
>>   
>>> Ah.
>>>
>>> Any suggestions for running this along side the development of other
>>> Radiant sites using earlier version?  For reasons of extension
>>> compatibility and my lack of knowledge of GIT I still run a lot of 0.6.9
>>> 
>> 'Cos I'd really like to try this for a new project I have in mind.
>>   
> 
> 
> I suggest you learn how to use git then.  ;^)  I have been looking into 
> other CMS's to use on larger projects, or projects not well suited to 
> radiant, and that's the one thing I cannot do without.

Perhaps, then, you can suggest a source of "How To" for GIT for
non-developers.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Question about Radiant_Rbiz extension

[Todd Willey]

Nate,

Actually, named_scope shouldn't be necessary any more.  Did you do git
submodule init / update from within the radiant_rbiz extension?

Thanks
-todd[1]

On Sun, Oct 11, 2009 at 1:18 AM, Nate  wrote:
> I am trying to migrate the radiant_rbiz extension but I get an error of
> "uninitialized constant RadiantRbizExtension::OfficeViewExtender" and I am
> not exactly sure I have all the parts for it to work.
>
> The radiant_rbiz extension is installed of course, and I have the
> named_scope plugin in vendor/plugins, but I am wondering if I need to clone
> the rbiz plugin as well?
>
> The task I have been given is to add the ability for people to contribute to
> a politico's campaign for office. Instead of adding a button to send the
> users to paypal, I'd like to manage it all in radiant. I am completely new
> to shopping carts and ecommerce, but this looks like the perfect way to go
> in a radiant project. Does anybody have this extension working in v0.8.1?
>
>
> Thanks,
>
> Nate
> ___
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>



-- 
CONFIDENTIALITY NOTICE:  This email is for sole use of intended
recipient(s).  Unauthorized use is prohibited.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] [ANN] Ping.fm Extension

[Haselwanter Edmund]

Hi *,

I haked a little extension inspired by the twitter extension from Sean  
(and some code thereof ;-):


http://github.com/ehaselwanter/radiant-pingfm-extension
http://edmund.haselwanter.com/en/blog/2009/10/11/simple-ping-fm-extension-for-radiant/

a sample twitter message created by saving the article:

http://twitter.com/ehaselwanter/status/4786380903

a sample delicious entry (at the moment its the first in the list)

http://delicious.com/search?p=radiantcms+ping.fm

Its the first iteration and *it works for me*

cu edi
--
DI Edmund Haselwanter, edm...@haselwanter.com, http://edmund.haselwanter.com/



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant