Re: [Radiant] Getting children a oage that is not the current page

[john muhl]

I believe you want r:find

...


On 2008/04/24, at 17:07, Alex Wayne wrote:

I have a navigation element in my layout that I want to always show
links to all children of a certain page that is nested one or 2 levels
inside my hierarchy.

I guess I need something like:


 
   
 


I can't seem to figure out how to load up a specific page like that to
operate on like that.

Thanks for helping out this radiant noob.
-Alex
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


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

[Radiant] upgrading 0.6.6+shards extension to 0.6.7

[john muhl]

UPGRADING FROM 0.6.x

1. Update the Radiant gem:

  % gem update radiant

2. Change the RADIANT_GEM_VERSION constant in config/environment.rb
  to "0.6.7".

3. Run the update rake task:

  % rake radiant:update

4. Run migrations:

  % rake db:migrate

5. Restart the server



Should an existing shards extension be removed before upgrading? Is  
removing the shards edit from environment.rb and the shards folder  
from vendor/extensions the proper way to uninstall the extension  
version?


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

Re: [Radiant] upgrading 0.6.6+shards extension to 0.6.7

[john muhl]

Thanks for the assurance.

On 2008/05/16, at 16:39, Sean Cribbs wrote:


john muhl wrote:

UPGRADING FROM 0.6.x

1. Update the Radiant gem:

 % gem update radiant

2. Change the RADIANT_GEM_VERSION constant in config/environment.rb
 to "0.6.7".

3. Run the update rake task:

 % rake radiant:update

4. Run migrations:

 % rake db:migrate

5. Restart the server



Should an existing shards extension be removed before upgrading? Is  
removing the shards edit from environment.rb and the shards folder  
from vendor/extensions the proper way to uninstall the extension  
version?


thanks.
Yes, remove the shards extension from vendor/extensions and then  
remove the :shards symbol from config.extensions in environment.rb.   
I'll update the blog post to say that.


Sean
___
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] upgrading 0.6.6+shards extension to 0.6.7

[john muhl]

nurullah,

Do you happen to have any other extensions installed that are not  
0.6.7 compatible? I think multi_site or page_attachments has problems  
with 0.6.7.



On 2008/05/17, at 09:05, nurullah wrote:


unfortunately that doesnt help at all :(



On 5/17/08, Sean Cribbs <[EMAIL PROTECTED]> wrote:


nurallah,

There is a migration in 0.6.7 that adds the 'salt' column to the User
model.  To get the migrations to run, try this:

1) Disable all extensions in environment.rb:

config.extensions = []

2) Run `rake db:migrate`.

3) Restore your extensions.

Sean

nurullah wrote:

after removing gallery extension migrate rake task successfully  
worked


but this time i get another error, here it is:

NameError (undefined local variable or method `salt' for
#):


/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/vendor/rails/ 
activerecord/lib/active_record/attribute_methods.rb:205:in

`method_missing'
/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/models/user.rb:32:in  
`sha1'

/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/models/user.rb:37:in
`authenticate'


/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/controllers/admin/ 
welcome_controller.rb:12:in

`login'
/usr/l

On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:



well, it seems update rake task doesnt work for me

production logs shows that:


ActionView::TemplateError (No such file or directory -

/var/www/nginx-default/vendor/extensions/shards/app/views/admin/ 
page/index.html.erb)

in admin/page/index.html.erb:



/usr/lib/ruby/gems/1.8/gems/radiant-0.6.6/vendor/rails/actionpack/ 
lib/action_view/base.rb:553:in

`lstat'



On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:



I couldnt upgrade to 0.6.7 and now cannot reach panel as well

it stuck in migrate step, firstly gave error because of copy_move
extension now removed it

i am using sqlite3 and what it says constantly "couldnt find table
config"







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





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


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


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

Re: [Radiant] upgrading 0.6.6+shards extension to 0.6.7

[john muhl]

Have you tried creating a blank 0.6.7 and seeing if you can get that  
working? Just to tell if it's something in your existing install or  
something more general.



On 2008/05/17, at 09:52, nurullah wrote:


i have gallery/newsletter/page_attachments installed

now removed all of them and still dont migrate

On 5/17/08, john muhl <[EMAIL PROTECTED]> wrote:


nurullah,

Do you happen to have any other extensions installed that are not  
0.6.7

compatible? I think multi_site or page_attachments has problems with
0.6.7.


On 2008/05/17, at 09:05, nurullah wrote:

unfortunately that doesnt help at all :(




On 5/17/08, Sean Cribbs <[EMAIL PROTECTED]> wrote:



nurallah,

There is a migration in 0.6.7 that adds the 'salt' column to the  
User

model.  To get the migrations to run, try this:

1) Disable all extensions in environment.rb:

config.extensions = []

2) Run `rake db:migrate`.

3) Restore your extensions.

Sean

nurullah wrote:

after removing gallery extension migrate rake task successfully  
worked


but this time i get another error, here it is:

NameError (undefined local variable or method `salt' for
#):



/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/vendor/rails/ 
activerecord/lib/active_record/attribute_methods.rb:205:in

`method_missing'
/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/models/user.rb:32:in
`sha1'
/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/models/user.rb:37:in
`authenticate'



/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/controllers/admin/ 
welcome_controller.rb:12:in

`login'
/usr/l

On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:


well, it seems update rake task doesnt work for me


production logs shows that:


ActionView::TemplateError (No such file or directory -


/var/www/nginx-default/vendor/extensions/shards/app/views/admin/ 
page/index.html.erb)

in admin/page/index.html.erb:




/usr/lib/ruby/gems/1.8/gems/radiant-0.6.6/vendor/rails/ 
actionpack/lib/action_view/base.rb:553:in

`lstat'



On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:


I couldnt upgrade to 0.6.7 and now cannot reach panel as well


it stuck in migrate step, firstly gave error because of  
copy_move

extension now removed it

i am using sqlite3 and what it says constantly "couldnt find  
table

config"






___

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





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

___

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



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


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


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

Re: [Radiant] upgrading 0.6.6+shards extension to 0.6.7

[john muhl]

You should be able to just adjust the RADIANT_GEM_VERSION in your  
config/environment.rb back to 0.6.6 and restart.


On 2008/05/17, at 13:23, nurullah wrote:


is there a way to turn back to 0.6.6?

or adding salt column to db manually?

i am just puzzled :S

On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:



but...

what i need is not that :)

coz i have many content is installed, galleries and newsletter emails

just looking for a way to rollback..
On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:



well, yes i tried that

a clean install does work
On 5/17/08, john muhl <[EMAIL PROTECTED]> wrote:


Have you tried creating a blank 0.6.7 and seeing if you can get  
that

working? Just to tell if it's something in your existing install or
something more general.


On 2008/05/17, at 09:52, nurullah wrote:

i have gallery/newsletter/page_attachments installed


now removed all of them and still dont migrate

On 5/17/08, john muhl <[EMAIL PROTECTED]> wrote:



nurullah,

Do you happen to have any other extensions installed that are  
not 0.6.7
compatible? I think multi_site or page_attachments has problems  
with

0.6.7.


On 2008/05/17, at 09:05, nurullah wrote:

unfortunately that doesnt help at all :(





On 5/17/08, Sean Cribbs <[EMAIL PROTECTED]> wrote:



nurallah,

There is a migration in 0.6.7 that adds the 'salt' column to  
the User

model.  To get the migrations to run, try this:

1) Disable all extensions in environment.rb:

config.extensions = []

2) Run `rake db:migrate`.

3) Restore your extensions.

Sean

nurullah wrote:

after removing gallery extension migrate rake task successfully
worked



but this time i get another error, here it is:

NameError (undefined local variable or method `salt' for
#):




/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/vendor/rails/ 
activerecord/lib/active_record/attribute_methods.rb:205:in

`method_missing'
/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/models/user.rb: 
32:in

`sha1'
/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/models/user.rb: 
37:in

`authenticate'




/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/controllers/ 
admin/welcome_controller.rb:12:in

`login'
/usr/l

On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:


well, it seems update rake task doesnt work for me



production logs shows that:


ActionView::TemplateError (No such file or directory -



/var/www/nginx-default/vendor/extensions/shards/app/views/ 
admin/page/index.html.erb)

in admin/page/index.html.erb:





/usr/lib/ruby/gems/1.8/gems/radiant-0.6.6/vendor/rails/ 
actionpack/lib/action_view/base.rb:553:in

`lstat'



On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:


I couldnt upgrade to 0.6.7 and now cannot reach panel as well



it stuck in migrate step, firstly gave error because of  
copy_move

extension now removed it

i am using sqlite3 and what it says constantly "couldnt  
find table

config"






___


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




___

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

___


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



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

___

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



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







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


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

Re: [Radiant] upgrading 0.6.6+shards extension to 0.6.7

[john muhl]

If you're using slicehost you may want to consider their backup  
service, that way you can simply take a snapshot, do your upgrade and  
if it fails just restore from your snapshot. Or take a snapshot of  
your current slice, boot up a new slice from the snapshot and test the  
upgrades, then apply them to your live slice and shut the new one  
down. As far as I can tell you pay by the day (or partial day) for  
slices so booting a new one whenever you need to test upgrades is  
quite economical.


On 2008/05/17, at 13:45, nurullah wrote:


hey john that saved me :)

thank you for that and your tutorial on your site (i use slicehost  
too)


but hope someone solve this problem and i will upgrade then to 0.6.7  
or

something...

have a nice days, guys

keep up the great job

On 5/17/08, john muhl <[EMAIL PROTECTED]> wrote:


You should be able to just adjust the RADIANT_GEM_VERSION in your
config/environment.rb back to 0.6.6 and restart.

On 2008/05/17, at 13:23, nurullah wrote:

is there a way to turn back to 0.6.6?


or adding salt column to db manually?

i am just puzzled :S

On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:




but...

what i need is not that :)

coz i have many content is installed, galleries and newsletter  
emails


just looking for a way to rollback..
On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:




well, yes i tried that

a clean install does work
On 5/17/08, john muhl <[EMAIL PROTECTED]> wrote:



Have you tried creating a blank 0.6.7 and seeing if you can get  
that
working? Just to tell if it's something in your existing  
install or

something more general.


On 2008/05/17, at 09:52, nurullah wrote:

i have gallery/newsletter/page_attachments installed



now removed all of them and still dont migrate

On 5/17/08, john muhl <[EMAIL PROTECTED]> wrote:



nurullah,

Do you happen to have any other extensions installed that are  
not

0.6.7
compatible? I think multi_site or page_attachments has  
problems with

0.6.7.


On 2008/05/17, at 09:05, nurullah wrote:

unfortunately that doesnt help at all :(





On 5/17/08, Sean Cribbs <[EMAIL PROTECTED]> wrote:


nurallah,


There is a migration in 0.6.7 that adds the 'salt' column  
to the

User
model.  To get the migrations to run, try this:

1) Disable all extensions in environment.rb:

config.extensions = []

2) Run `rake db:migrate`.

3) Restore your extensions.

Sean

nurullah wrote:

after removing gallery extension migrate rake task  
successfully

worked



but this time i get another error, here it is:

NameError (undefined local variable or method `salt' for
#):





/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/vendor/rails/ 
activerecord/lib/active_record/attribute_methods.rb:205:in

`method_missing'
/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/models/ 
user.rb:32:in

`sha1'
/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/models/ 
user.rb:37:in

`authenticate'





/usr/lib/ruby/gems/1.8/gems/radiant-0.6.7/app/controllers/ 
admin/welcome_controller.rb:12:in

`login'
/usr/l

On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:


well, it seems update rake task doesnt work for me



production logs shows that:


ActionView::TemplateError (No such file or directory -




/var/www/nginx-default/vendor/extensions/shards/app/views/ 
admin/page/index.html.erb)

in admin/page/index.html.erb:






/usr/lib/ruby/gems/1.8/gems/radiant-0.6.6/vendor/rails/ 
actionpack/lib/action_view/base.rb:553:in

`lstat'



On 5/17/08, nurullah <[EMAIL PROTECTED]> wrote:


I couldnt upgrade to 0.6.7 and now cannot reach panel as  
well




it stuck in migrate step, firstly gave error because of
copy_move
extension now removed it

i am using sqlite3 and what it says constantly "couldnt  
find

table
config"





___


Radiant mailing list

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




___


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

___

Radiant mailing list

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


___

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

___


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



___
Radiant mailing list
Post:   R

Re: [Radiant] Redirect function of the Mailer Extension

[john muhl]

you might try the tip suggested at the bottom of http://lists.radiantcms.org/pipermail/radiant/2008-May/008476.html 
 and see if that helps.

On 2008/06/01, at 05:41, Ulf Moehring wrote:


Hi *,

The redirect functionality of the mailer extension (redirect_to: / 
thankyou) doesn't work like I want it to. Instead of redirecting  
properly it merely displays a new page with a single line "You are  
being redirected" but nothing happens. You have to click on  
redirected in order for something to happen, which is pretty ugly.


I remember it working properly with Radiant 0.6.4 and some older  
version of the extension. I'm using Radiant 0.6.6 right now. Any  
suggestions? Since everything else is running perfectly I'd rather  
not upgrade to 0.6.7 right now...


Thanks,
Ulf
___
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] Questions about deployment

[john muhl]

On 2008/06/03, at 11:22, Casper Fabricius wrote:

If you have uploaded files using gallery, page_attachments or  
something else locally, you must also upload these manually from  
public to public.


I ran into this same issue (with page_attachments), so I just switched  
it to use Amazon S3 for storage instead of the file system. You can  
even “patch” attachement_fu to add cache and expires headers to the  
files you upload to Amazon. Works perfectly so far.


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

[Radiant] any way to dynamically populate ?

[john muhl]

I'd like to insert part of a random subpage into the sidebar and  
figured it'd be a good fit for the  tag but so far am having  
very little luck. I've tried:



  

  


and even:


  

  

  


but they both just return the title of the parent page. Am I missing  
something simple or expecting the impossible. Does anyone have any  
suggestion how to randomly grab a page part from a dynamically  
generated list of pages, besides using javascript?


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

Re: [Radiant] any way to dynamically populate ?

[john muhl]

On 2008/06/07, at 16:49, Andrew Neil wrote:


On 6 Jun 2008, at 01:01, john muhl wrote:

I'd like to insert part of a random subpage into the sidebar and  
figured it'd be a good fit for the  tag but so far am  
having very little luck. I've tried:




  




I thought of an alternative approach which might be easier to  
implement. Here is an example:



 
 
 


This doesn't work at the moment, because the order attribute can  
only be asc or desc. I think it would be pretty easy to add the  
option for random order though.


I was going to try putting together a patch to add "rand" as an order  
option, but as far as I can tell the "ASC" and "DESC" ordering is part  
of ActiveRecord and that seems like the wrong place to apply a patch  
for Radiant. Am I way off base here or are the ordering options, in  
fact, part of ActiveRecord?

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

Re: [Radiant] any way to dynamically populate ?

[john muhl]

I guess Sunday is as good a day as any to get to know rspec. Unless  
someone beats me to it I send a pull request when I think I have  
something useful.


On 2008/06/07, at 20:35, Sean Cribbs wrote:

Actually, I just answered my own question.  We should really be  
rendering the contents of  at each pass, rather than  
passing the block back.  The reason is that local context  
(tag.locals) will be potentially lost when you render the block  
after selecting the option.  However, a spec that demonstrates the  
difference would be appreciated!


Sean

Sean Cribbs wrote:
This one has always been a mystery to me, however I believe it has  
to do with tag blocks versus expands.  I imagine, however, we could  
produce a failing spec to demonstrate what is unexpected about the  
behavior.  Any takers?


Sean

john muhl wrote:

On 2008/06/07, at 16:49, Andrew Neil wrote:


On 6 Jun 2008, at 01:01, john muhl wrote:

I'd like to insert part of a random subpage into the sidebar and  
figured it'd be a good fit for the  tag but so far am  
having very little luck. I've tried:




 




I thought of an alternative approach which might be easier to  
implement. Here is an example:








This doesn't work at the moment, because the order attribute can  
only be asc or desc. I think it would be pretty easy to add the  
option for random order though.


I was going to try putting together a patch to add "rand" as an  
order option, but as far as I can tell the "ASC" and "DESC"  
ordering is part of ActiveRecord and that seems like the wrong  
place to apply a patch for Radiant. Am I way off base here or are  
the ordering options, in fact, part of ActiveRecord?

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






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


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

Re: [Radiant] any way to dynamically populate ?

[john muhl]

I have to admit that rspec is still a bit intimidating, so I'm not  
sure this is exactly the sort of spec you were looking for. Feel free  
to point out everything that's wrong here and I'll try again.


===
--- standard_tags_spec.rb
+++ standard_tags_spec.rb
@@ -383,6 +383,13 @@
   it ' should render a randomly selected contained  
' do
 page.should render(" 1  
2 3 ").matching(/ 
^(1|2|3)$/)

   end
+
+  describe "" do
+it "should render each option before returning" do
+  page(:parent)
+  page.should  
render('r:children:each>').matching(/^(Child|Child\ 2|Child\ 3)$/)

+end
+  end

   it ' should render nothing it contains' do
 page.should render('just a small r:comment>test').as('just a test')


===

The failure is:

expected "r:option>"

to render and match /^(Child|Child\ 2|Child\ 3)$/, but got "Parent"

On 2008/06/07, at 20:35, Sean Cribbs wrote:

Actually, I just answered my own question.  We should really be  
rendering the contents of  at each pass, rather than  
passing the block back.  The reason is that local context  
(tag.locals) will be potentially lost when you render the block  
after selecting the option.  However, a spec that demonstrates the  
difference would be appreciated!


Sean

Sean Cribbs wrote:
This one has always been a mystery to me, however I believe it has  
to do with tag blocks versus expands.  I imagine, however, we could  
produce a failing spec to demonstrate what is unexpected about the  
behavior.  Any takers?


Sean

john muhl wrote:

On 2008/06/07, at 16:49, Andrew Neil wrote:


On 6 Jun 2008, at 01:01, john muhl wrote:

I'd like to insert part of a random subpage into the sidebar and  
figured it'd be a good fit for the  tag but so far am  
having very little luck. I've tried:









I thought of an alternative approach which might be easier to  
implement. Here is an example:








This doesn't work at the moment, because the order attribute can  
only be asc or desc. I think it would be pretty easy to add the  
option for random order though.


I was going to try putting together a patch to add "rand" as an  
order option, but as far as I can tell the "ASC" and "DESC"  
ordering is part of ActiveRecord and that seems like the wrong  
place to apply a patch for Radiant. Am I way off base here or are  
the ordering options, in fact, part of ActiveRecord?

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






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


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

Re: [Radiant] Failure to install Page Attachments extension

[john muhl]

I think your problem might be with ruby 1.8.7, there were some changes  
to Enumerable::Enumerator that are possibly incompatible. Can you try  
going back to 1.8.6 and see if you get the same error?


On 2008/06/17, at 14:50, Matt Anderson wrote:


I'm trying to follow the instructions at
http://wiki.radiantcms.org/Installing_Extension_-_Page_Attachments.  
When

I get to this step:

rake production db:migrate:extensions

The output is:

rake aborted!
undefined method `[]' for #


From that point on, my server will no longer start up as well.


This is on Leopard, with
ruby 1.8.7 (2008-06-09 patchlevel 17) [i686-darwin9.3.0]
rails 2.1.0

Any suggestions would be appreciated!
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


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

Re: [Radiant] Bootstrapping problem

[john muhl]

I've had good results with Radiant, SQLite3 and Mac 10.5 "just  
working" so if that's a possibility it might save you some effort.


On 2008/06/23, at 10:19, aslak hellesoy wrote:


Hi again,

I just pulled the code from Github, copied config/database.sqlite.yml
to config/database.yml, cd into radiant/radiant and ran rake
development db:bootstrap

It fails with:

SQLite3::SQLException: no such table: pages: SELECT DISTINCT
class_name AS klass_name FROM pages WHERE class_name <> '' AND
class_name IS NOT NULL

I've seen similar errors mentioned in a couple of older threads, but
nothing helped me. It seems several model classes are referenced while
the db:bootstrap task is running, but I have an empty database. Seems
like a catch 22 to me. Is there a simple workaround? Here is the full
trace:

C:\scm\radiant\radiant>rake development db:bootstrap --trace
(in C:/scm/radiant/radiant)
** Invoke development (first_time)
** Execute development
** Invoke environment (first_time)
** Execute environment
rake aborted!
SQLite3::SQLException: no such table: pages: SELECT DISTINCT
class_name AS klass_name FROM pages WHERE class_name <> '' AND
class_name IS NOT NULL
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ 
connection_adapters/abstract_adapter.rb:150:in

`log'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ 
connection_adapters/sqlite_adapter.rb:132:in

`execute'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ 
connection_adapters/sqlite_adapter.rb:345:in

`catch_schema_changes'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ 
connection_adapters/sqlite_adapter.rb:132:in

`execute'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ 
connection_adapters/sqlite_adapter.rb:256:in

`select'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ 
connection_adapters/abstract/database_statements.rb:7:in

`select_all_without_query_cache
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ 
connection_adapters/abstract/query_cache.rb:55:in

`select_all'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/active_record/ 
base.rb:532:in

`find_by_sql'
C:/scm/radiant/radiant/app/models/page.rb:191:in `load_subclasses'
C:/scm/radiant/radiant/app/models/page.rb:279
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:203:in

`load_without_new_constant_marking'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:203:in

`load_file'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:342:in

`new_constants_in'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:202:in

`load_file'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:94:in

`require_or_load'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:248:in

`load_missing_constant'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:453:in

`const_missing'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:465:in

`const_missing'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:260:in

`load_missing_constant'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:469:in

`const_missing'
C:/scm/radiant/radiant/app/models/user_action_observer.rb:2
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:203:in

`load_without_new_constant_marking'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:203:in

`load_file'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:342:in

`new_constants_in'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:202:in

`load_file'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:94:in

`require_or_load'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:248:in

`load_missing_constant'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:453:in

`const_missing'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/dependencies.rb:465:in

`const_missing'
C:/scm/radiant/radiant/vendor/rails/activerecord/lib/../../ 
activesupport/lib/active_support/inflector.rb:257:in

`constantize'
C:/scm/radiant/radiant/vendor/rail

Re: [Radiant] Re: crashes with recently released ruby (1.8.6p230)

[john muhl]

Apparently the Phusion guys have backported the security fixes to  
1.8.6-p111 in their Ruby Enterprise edition. Might be worth checking  
out if you're stuck between security issues and a broken ruby.


http://blog.phusion.nl/2008/06/23/ruby-186-p230187-broke-your-app-ruby-enterprise-edition-to-the-rescue/

On 2008/06/22, at 23:58, James Blanding wrote:


Mohit Sindhwani wrote:

[...]


James,

I read on the Ruby mailing list that the new version breaks Rails.

Cheers,
Mohit.
6/23/2008 | 1:30 PM.



Ah, I see you're right.  I had thought it was Radiant-specific because
my two sites that don't run Radiant seemed to load fine.  I did not  
test

any further than the front pages, however.  Perhaps if I had clicked
around, those apps would have also gone down.

Oh well, hopefully things will be fixed soon.

Thanks,

--James
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


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

Re: [Radiant] Page_attachments, but for other pages

[john muhl]

have you tried something like:


  

  



On 2008/06/26, at 08:21, [EMAIL PROTECTED] wrote:


Hey guys,

Is there any way to access/view a page_attachment on a page where it
hadn't been added in the first place? Say I have a section of my site
called "Manufacturers" that includes a child page for each  
manufacturer

that my client works with, is there any way to access the logo I added
on each manufacturer page on a page that is the child of a different
parent?


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] Page_attachments, but for other pages

[john muhl]

You can see the available tags and descriptions of them in the tags  
file[1].
I actually had the same situation in a recent project and never did  
find a
way to do limits with attachments. With deadlines and all that, I  
finally just

used javascript/css to emulate the limit I needed.


[1]: 
http://github.com/radiant/radiant-page-attachments-extension/tree/master/app/models/page_attachment_tags.rb

On 2008/06/26, at 09:38, [EMAIL PROTECTED] wrote:


On Thu, 2008-06-26 at 08:27 -0600, john muhl wrote:

have you tried something like:


  

  




That looks like it will probably work, but I have another question.
Since the client will be uploading these files and I cannot guarantee
that the logo will always be named as such, how can I do something  
like
this to find the first item in the list of attachments for the page  
and

display it as an image:



?


~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

[Radiant] Markdown extension using RDiscount

[john muhl]

I've patched the default Markdown extension so it uses RDiscount  
instead of BlueCloth. The point was to improve the accuracy of  
Radiant's Markdown conversion; for an added bonus it's also really  
fast. Although the difference in speed diminishes as the amount of  
Markdown to convert goes down, so if you just have little bits of  
Markdown here and there, skip it, if you're publishing lengthy  
articles or pages heavy with Markdown behind the scenes then you'll  
probably notice a significant difference. See the links at the end for  
a demonstration.


The only down sides are that it requires the `rdiscount` gem to be  
installed on the server and a little change to the order extensions  
are loaded. The github page has all the details. It should be noted  
that the change to extension load order is probably becoming the  
standard order eventually -- I think unless some reason not to pops up.


If none of that's a problem for you then head over to github for the  
download and a bit more information.


There is also the `markdown` branch in my radiant fork where I am  
trying to get together something that could possibly, eventually be  
applied to the core; so if you have the `rdiscount` gem installed you  
get its Markdown filtering and if not you get the standard BlueCloth  
rendition.


Any preference between the standalone extension and getting the  
`markdown` branch into the core?



[bluecloth]: http://johnmuhl.com/test/markdown-bluecloth
[rdiscount]: http://johnmuhl.com/test/markdown-rdiscount
[github]: http://github.com/johnmuhl/radiant-markdown-extension
[radiant]: http://github.com/johnmuhl/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] Markdown extension using RDiscount

[john muhl]

On 2008/06/27, at 21:02, Jim Gay wrote:


On Jun 27, 2008, at 10:26 PM, john muhl wrote:


I've patched the default Markdown extension


Looks nice. I've been frustrated by strange parsing bugs, but never  
looked into it. A more accurate implementation of the syntax gets a  
warm welcome from me.


If you happen to have samples handy of the Markdown that caused  
trouble I'd be happy to add them to the test page.

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

Re: [Radiant] Markdown extension using RDiscount

[john muhl]

On 2008/06/29, at 21:23, Jim Gay wrote:


On Jun 28, 2008, at 2:35 PM, john muhl wrote:


On 2008/06/27, at 21:02, Jim Gay wrote:


On Jun 27, 2008, at 10:26 PM, john muhl wrote:


I've patched the default Markdown extension


Looks nice. I've been frustrated by strange parsing bugs, but  
never looked into it. A more accurate implementation of the syntax  
gets a warm welcome from me.


If you happen to have samples handy of the Markdown that caused  
trouble I'd be happy to add them to the test page.


...one particular problem I'm having is that **bold** should be  
formatted as bold but BlueCloth parses it as  
*bold*...


It was actually **12** being parsed as *12* that drove me to  
plugging in RDiscount. Now I've started documenting the deficiencies  
in the RDiscount version on the github wiki. I think they're  
insignificant so far, since there is nothing that will ever get you  
called by a client irritated about their CMS; unless your clients do  
crazy nested s in their Markdown :)


For what it's worth the Safari Web Inspector reports 10 HTML errors on  
the BlueCloth version of the test page, while it reports 1 on the  
RDiscount version (in the Advanced Inline HTML test which Markdown.pl  
itself would fail).


http://github.com/johnmuhl/radiant-markdown-extension/wikis/inconsistencies
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] page_attachments on non- page types

[john muhl]

Is there an easy way to get page_attachments working with other page  
types, like the File Not Found or Archive types?


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

Re: [Radiant] page_attachments on non- page types

[john muhl]

On 2008/07/01, at 22:33, [EMAIL PROTECTED] wrote:

On Tue, 2008-07-01 at 21:38 -0600, john muhl wrote:

Is there an easy way to get page_attachments working with other page
types, like the File Not Found or Archive types?



Or even better, be able to attach images to the home page and have  
them
available everywhere, or to the site itself. Like, have a page with  
all

the attachments for sitewide consumption where you can manage them and
be able to access them from everywhere. Maybe that's just wishful
thinking.  ;^)


What would you like to do that you can't do using the existing tags  
like,



  ...


I'm using that setup pretty successfully on a new project. There're  
just times when I need a custom page type and the client to be able to  
manage attachments on that page. For example, a mailer page where the  
client uploads their own headshot and vcard.

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

[Radiant] Re: page_attachments on non- page types

[john muhl]

The solution turns out to be just editing environment.rb

   config.extensions = [ :page_attachments, :all ]

or if you're still < 0.6.7

   config.extensions = [ :shards, :page_attachments, :all ]

and restart of course.

On 2008/07/01, at 21:38, john muhl wrote:

Is there an easy way to get page_attachments working with other page  
types, like the File Not Found or Archive types?


thanks


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

Re: [Radiant] Installing extensions

[john muhl]

For add on extensions you want the path to your running Radiant  
application, such as, "~/Sites/my app/vendor/extensions"


On 2008/07/11, at 09:49, Jan frederik Poulsen wrote:


I'm on a mac.

Radiant is located in two places on my machine:

1. As "my app" - my specific site: ~/Sites/

and

2. As "the generator" Library/Ruby/Gems/1.8/gems/radiant-0.6.7

Wher are extensions supposed to be installed? In my specifik site of  
the

"original" place?
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


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

Re: [Radiant] svn: 'vendor/extensions' is not a working copy

[john muhl]

It looks like your radiant_app directory is not in subversion, as far  
as I remember from my limited experience with subversion you need to  
have your Radiant application in svn (i.e. the directory containing  
vendor/extensions) prior to adding externals – another possibility is  
to just use svn export instead.


I believe however the core team is dropping the svn repo completely  
soon, so an svn:external pointing there is probably not the best  
longer term solution. You might want to look into git submodules, i.e.


git submodule add git://github.com/radiant/radiant-reorder- 
extension.git vendor/extensions


You can also find tar/zip files for everything on github, i.e.

wget http://github.com/radiant/radiant-reorder-extension/tarball/master


On 2008/07/13, at 10:47, Jan frederik Poulsen wrote:


Whenever I try to install an extension via subversion like this for
example:

cd /path/to/radiant

svn propset svn:externals "reorder -r881
http://svn.radiantcms.org/radiant/tags/rel_0-6-7/extensions/reorder/";
vendor/extensions/.

I get this:

svn: 'vendor/extensions' is not a working copy

What is the problem?

I have also tried to manually download and upload the extension via  
ftp,

but then the rake command fails:

rake aborted!
uninitialized constant ApplicationController

Sorry for asking this many questions, couldn't find a google- 
solution -

I would think that a lot of people just give up when trying this but I
really like Radiant, - maybe I could help a bit with the "getting up  
and

running quick" documentation, when I finally succeed?
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


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

Re: [Radiant] Re: svn: 'vendor/extensions' is not a working copy

[john muhl]

Ah, yeah that could be a problem. I bet they have at least one of wget  
or curl installed which you can use to get the tar/zip files.


1. cd /path/to/radiant_app/vendor/extensions

2. wget http://github.com/radiant/radiant-reorder-extension/tarball/master

3. tar xzvf radiant-radiant-reorder- 
extension-2295abc88438aef3c1836c24c5e8825e04ef16ef.tar.gz


4. mv radiant-radiant-reorder- 
extension-2295abc88438aef3c1836c24c5e8825e04ef16ef reorder


5. cd ../..

6. rake radiant:extensions:reorder:migrate

Or something along those lines.


On 2008/07/13, at 11:04, Jan frederik Poulsen wrote:


Thank you

yes a tried with git on my local system which worked fine, but i don't
think site5 (my hosting provider) supports git?

when i try:

git clone git://github.com/radiant/radiant-reorder-extension.git  
reorder


i get:

-bash: git: command not found

--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


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

Re: [Radiant] Page_attachment extension with Flash files?

[john muhl]

On 2008/07/12, at 12:41, Sean Cribbs wrote:

If there's a pretty standard way to insert a SWF, I'd love to see an  
implementation of  and I'd be happy to merge it  
in.


http://github.com/johnmuhl/radiant-page-attachments-extension/tree/swf

Seemed to me that  is the simplest way to  
do it. If any of the Flash gurus have a more elaborate syntax they'd  
like feel free to suggest it and I'll see what I can to do accommodate.


Usage:

 or with html attributes like
height="200" />




Sean

Casper Fabricius wrote:
I have it in the lib dir of a custom extension, in a file called  
extra_tags.rb inside a module called ExtraTags. Then, in the init  
file of the extension, I have this line:


Page.send :include, ExtraTags

You can also just add the module to the standard Radiant lib dir  
and put the line above in environment.rb.


And yes, I use it with the page_attachments extension. Just supply  
the name of the attachment to the src attribute of the tag.


/Casper



On 12/07/2008, at 18:27, Nate Turnage wrote:

On Sat, Jul 12, 2008 at 10:59 AM, Casper Fabricius <[EMAIL PROTECTED] 
>

wrote:


Hi Nate,

I use SWFObject (http://code.google.com/p/swfobject/) and have a  
custom

tag to insert flash elements:
http://pastie.org/232639



Which model do you add this to? And do you use it with the  
page_attachment

extension? Thanks for the method though. It's bril.



~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



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


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

Re: [Radiant] Page_attachment extension with Flash files?

[john muhl]

On Sun, Jul 13, 2008 at 2:24 PM, Sean Cribbs <[EMAIL PROTECTED]>  
wrote:




Is SWFObject available on Google's JS cache (like Prototype and  
jQuery)? If

so, that could be an option.



It certainly doesn't look like they have SWFObject in the caches.


On 2008/07/13, at 13:32, Nate Turnage wrote:

I don't know. I do know that SWFObject will soon become the official  
way


from Adobe to place Flash files. If Caspar's solution could get  
rolled into
into Radiant, I think it would be the best way to handle Flash  
files. I was

going to add it to my site, but I am really not ready to write my own
extension yet and I cannot add it to the Radiant lib because I am  
using the

gem.


Handling Flash files in Radiant core? I'm not going to pursue that  
route simply because I don't think it's appropriate for Radiant to be  
Flash aware out of the box. However, I will look at SWFObject and see  
about rolling it into the .swf handling part of page_attachments.




On 2008/07/13, at 13:17, Steven Southard wrote:



I think if you don't use JavaScript like that to bring in Flash  
you'll have problems with  Internet Explorer.


You just mean avoiding compatibility issues between different versions  
of the Flash player? I setup a test page with only:




test.swf is a simple AS3 file that loops through some images and it  
appears to work fine in Internet Explorer 6, 7 & 8 beta. Could you  
elaborate on what you mean by “problems with Internet Explorer”?___

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

Re: [Radiant] Re: Re: svn: 'vendor/extensions' is not a working copy

[john muhl]

On 2008/07/13, at 15:23, Jan frederik Poulsen wrote:

I finally got the extension working (however some images to the  
buttons

are missing?)


I think you probably forgot to run the update task,

cd /your/radiant_app
rake radiant:extensions:reorder:update

That will copy the necessary image and script assets to your public  
folder.



I uploaded the tar.gz-file, unpacked it, renamed it to reorder

ran:

rake production db:migrate:extensions

it returned:

(in /home/chainrea/radapp)
== 1 AddPositionToPages: migrating

-- add_column(:pages, :position, :integer)
  -> 0.0335s
-- Putting all pages in a default order...
  -> 0.4285s
== 1 AddPositionToPages: migrated (0.4623s)
===

A warning though - it takes a minute or two before the extensions  
turns
up in the admin - at first I thought it didn't work after all, but  
then
the it appeared after a short moment and a couple of manic log-outs/ 
ins.

:-) Now it seems radiant is beginning to "radiate" for me... :-)


--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


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

Re: [Radiant] Re: Re: svn: 'vendor/extensions' is not a working copy

[john muhl]

Oh and you can always, cd into your radiant app and run

rake -T

to see what tasks are available. extensions specific tasks will all be  
grouped together in that list (in the radiant:extensions namespace),  
so it's pretty easy to figure out what tasks a given extension needs  
you to run.



On 2008/07/13, at 15:26, john muhl wrote:


On 2008/07/13, at 15:23, Jan frederik Poulsen wrote:

I finally got the extension working (however some images to the  
buttons

are missing?)


I think you probably forgot to run the update task,

cd /your/radiant_app
rake radiant:extensions:reorder:update

That will copy the necessary image and script assets to your public  
folder.



I uploaded the tar.gz-file, unpacked it, renamed it to reorder

ran:

rake production db:migrate:extensions

it returned:

(in /home/chainrea/radapp)
== 1 AddPositionToPages: migrating

-- add_column(:pages, :position, :integer)
 -> 0.0335s
-- Putting all pages in a default order...
 -> 0.4285s
== 1 AddPositionToPages: migrated (0.4623s)
===

A warning though - it takes a minute or two before the extensions  
turns
up in the admin - at first I thought it didn't work after all, but  
then
the it appeared after a short moment and a couple of manic log-outs/ 
ins.

:-) Now it seems radiant is beginning to "radiate" for me... :-)


--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


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


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

[Radiant] [ANN] Ray extension

[john muhl]

Despite the dependence on GitHub there is no required dependency on  
git the program, if you don't have git installed Ray will gladly use  
wget instead. So if you had noticed the extension on GitHub already  
but thought "pfft, more 'requires git' nonsense" you might have a  
second look.


Ray is basically a collection of rake commands that let you manage  
your extensions with less typing. For example, if you currently want  
to install the Page Attachments extension you'd do something like


  gem install mini_magick
  cd /radiant/app
  git clone git://github.com/technoweenie/attachment_fu.git vendor/ 
plugins/attachment_fu
  git clone git://github.com/radiant/radiant-page-attachments- 
extension.git vendor/extensions/page_attachments

  rake radiant:extensions:page_attachments:migrate
  rake radiant:extensions:page_attachments:update
  monit -g mongrels restart all

With Ray you would run

  rake ray:extension:page_attachments lib=mini_magick  
restart=mongrel_cluster


Page Attachments is what Ray calls a “special extension,” namely that  
it's not a normal installation pattern. For all the other great  
extensions on GitHub you have a few options. For example, if you  
wanted the Mailer extension from the official repository


  rake ray:extension:install name=mailer

What if you want if want ntalbott's fork of the Mailer extension?

  rake ray:extension:install name=mailer hub=ntalbott

You can get away with only specifing the short name as long as the  
extension author has used a name for their extension like "radiant- 
extension-name-extension". So what if Bob the extension developer has  
decided on some other kind of name, like sweet-sauce_for-radiant?


  rake ray:extension:install name=sweet-sauce hub=bob fullname=sweet- 
sauce_for-radiant


Right now, Ray is sort of stupid about migrate/update tasks and just  
blindly runs them both for all extensions regardless. If an extension  
doesn't need one or both tasks run you might see some errors but  
they'll be harmless.


Once an extension is installed it can be easily disabled or enabled with

  rake ray:extension:disable name=mailer
  rake ray:extension:enable name=mailer

To install Ray either

  git clone git://github.com/johnmuhl/radiant-ray-extension.git  
vendor/extensions/ray


or unpack the tarball into vendor/extensions and rename it ray. No  
migrate or update tasks are necessary.


http://github.com/johnmuhl/radiant-ray-extension/tarball/master


---
I know if you watch the dev. list this may seem like a day late but  
that's OK – I think there's room plus Ray has other options on the  
horizon that might be neat outside the extension context.


___
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] Ray extension

[john muhl]

Thanks for catching that, the fix has been pushed up to GitHub.

On 2008/07/17, at 03:58, Keith Bingman wrote:

When I try this,  with hub and fullname, I get a repository not  
found error. I think the problem is that the repos url is getting an  
extra "/" in there between the github name and the fullname of the  
extension. Remove that in the rake task and it works great.


Keith Bingman
On Jul 17, 2008, at 2:24 AM, john muhl wrote:

rake ray:extension:install name=sweet-sauce hub=bob fullname=sweet- 
sauce_for-radiant


Right now, Ray is sort of stupid about migrate/update tasks and  
just blindly runs them both for all extensions regardless. If an  
extension doesn't need one or both tasks run you might see some  
errors but they'll be harmless.


Once an extension is installed it can be easily disabled or enabled  
with


rake ray:extension:disable name=mailer
rake ray:extension:enable name=mailer



___
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] [ANN] Ray extension

[john muhl]

Just a note that Ray is no longer “sort of stupid about migrate/update  
tasks”. Now an effort is made to determine whether there are any tasks.


If a `vendor/extensions/extension_name/lib/tasks/ 
extension_name_extension_tasks.rake` file is found, Ray takes a peek  
inside to determine whether there are migrate and update tasks and  
only runs tasks that it actually finds.


If no `vendor/extensions/extension_name/lib/tasks/ 
extension_name_extension_tasks.rake` file is found the entire post  
install process is skipped.


The changes are available on 
GitHub.___
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] Ray extension

[john muhl]

One more tiny update to point out Ray no longer depends on wget for  
fallback, instead that functionality has been replaced using the  
standard Ruby HTTP library. Hopefully it will make Ray useful in a  
wider variety of environments.

___
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] Ray extension

[john muhl]

It is possible. I'm just not sure the best way to do it.

When I started both options were considered and I guessed (possibly  
wrongly) most people aren't “scm'ing” their Radiant app. So instead of  
going around git init'ing everyone's RADIANT_ROOT for them I figured  
clones were less fuss, less muss.


So would you change the default to pull-in a submodule? Or add another  
option to switch from clone to submodule mode (i.e. `use=submodule`)?




On 2008/07/21, at 02:43, aslak hellesoy wrote:


Can Ray install extensions as Git submodules? I always use Git
submodules - I never "copy".

Aslak

On Sun, Jul 20, 2008 at 12:54 AM, john muhl <[EMAIL PROTECTED]>  
wrote:

One more tiny update to point out Ray no longer depends on wget for
fallback, instead that functionality has been replaced using the  
standard
Ruby HTTP library. Hopefully it will make Ray useful in a wider  
variety of

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


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


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

Re: [Radiant] [ANN] Ray extension

[john muhl]

On 2008/07/21, at 10:39, Sean Cribbs wrote:

In the case that the project is in git, you could manually create  
the .gitsubmodule file from the sha of the HEAD of the extension,  
since the submodules are just git repos themselves. I may support a  
switch in the script/extension installer for a scenario like this,  
but it will require some thought.


Now I'm thinking that it might be simplest to just look for  
RADIANT_ROOT/.git and if it's found switch into submodule mode,  
otherwise a clone is done.


My thinking is that if you have a .git directory at RADIANT_ROOT  
you've either decided to scm your install or someone put it there for  
you because they wanted to scm your install. In either case the best  
option is be a submodule.



On 2008/07/21, at 02:43, aslak hellesoy wrote:




Can Ray install extensions as Git submodules? I always use Git
submodules - I never "copy".



Does the above scenario sound like the behavior you were after?
___
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] Ray extension

[john muhl]

On 2008/07/21, at 12:30, Sean Cribbs wrote:


You mean RAILS_ROOT


Whoops, you're right. I must have had Radiant on the brain.

On 2008/07/21, at 13:37, Tim Gossett wrote:


I just passed over the Ray extension because I just saw "deploy with
Capistrano" and thought "deploying with git is easy enough."


and that part hasn't even been started yet :) I just removed those  
words from the github description, sorry about the confusion.


But if it automatically installs extensions as git submodules, I'd  
be much more
interested. Especially if the presence of a .git directory at the  
project's

root automatically puts it in git mode.


It doesn't do that yet, but it looks like where I'll be taking it the  
next time I have a few minutes to work on it. It's actually the  
presence of a working `git` command in your PATH that determines git  
or http mode.


How easily does this fold into an existing Radiant install? Will it  
detect

the submodules that are there already?


If you've already installed extensions as submodules and then install  
Ray you'll be able to add more extensions as submodules (they'll be  
global to your project just like the others you added), except you can  
roll it all up in to one handy command, i.e. rake  
ray:extension:install name=mailer restart=passsenger – of course it  
won't do that today but within the next day it should be working that  
way.


Pretty soon after that I'll be adding ray:update,  
ray:extension:update:all and ray:extension:update name=mailer commands  
and I'll make sure these work off submodules if you've got your  
extensions (even ray) installed that way.


Thanks for the feedback.


___
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] Ray extension

[john muhl]

On 2008/07/21, at 13:37, Tim Gossett wrote:

But if it automatically installs extensions as git submodules, I'd  
be much more
interested. Especially if the presence of a .git directory at the  
project's

root automatically puts it in git mode.


I just pushed the changes up to github to support submodules during  
installation. What happens now is ray looks for a `git` command in  
your PATH, then if that's found it checks for `.git/HEAD` in your  
RAILS_ROOT and if that's found does a `git add submodule` otherwise  
just a regular `git clone` happens.



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

Re: [Radiant] Ray extension for development-only?

[john muhl]

On 2008/07/22, at 13:35, Tim Gossett wrote:

So if the Ray extension makes it stupid-easy to install Radiant  
extensions

and can use Git to schlep the code around, does it need to be on my
production box? Can I add it as a submodule for my local repo and  
ignore it
for my remote repo? The idea is to streamline the production box so  
that it

doesn't have to load an extension that's only going to be used in
development.

Am I completely misunderstanding how Ray is to be used?


You've got it right. Install Ray locally to relieve yourself of some  
repetitive typing when in development, then ignore it in your  
deployment recipe. The only reason you'd want it on the production  
machine is to use the tasks there.


Nothing in Ray makes the extensions you install with it different than  
the ones you install normally; i.e. if you use submodules Ray will  
too, if you clone git repos into your extensions folder Ray will too,  
if you download archive files Ray will too.



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

Re: [Radiant] New RedCloth

[john muhl]

On 2008/07/24, at 07:44, Sean Cribbs wrote:

How would people feel about switching to a gem dependency on the  
latest RedCloth (instead of packaging it)?


I think it's going to have to happen at some point unless Radiant  
wants to keep using the same old text parsing libraries from  
2004/2005. Waiting for the pure ruby libraries catch back up is the  
other (wishful) option.



On 2008/07/24, at 09:31, Chris Parrish wrote:

I understood discoount to be *nix only (no Windows).  I'll have to  
look into it further.


That's right. Although there isn't anything really stopping it from  
being compiled for windows with mingw just like they did RedCloth 4;  
except of course finding people who use windows to do the work :)  
There is also PEG markdown (rpeg-markdown in ruby land) but right now  
it is completely unusable on big (huge?) spans of text and I'm not  
sure it's any easier to get running in windows. Personally, I'd rather  
have a PEG based Markdown than a Discount based one.



As far as getting a new Markdown parser into core I'd say don't even  
bother yet. As has been stated Discount doesn't (yet) run on windows,  
and PEG Markdown is crashy (and probably doesn't run on windows either).


I would definitely like to see Radiant upgrade to RedCloth 4 sometime  
soon. If no one jumps up to take it on in the next week, I'll try to  
get it running then.



p.s. I did put together a standalone Markdown filter that uses  
rdiscount, so if you can install gems and don't run windows you can  
use that until something better is in the core. I use it on live sites  
with no problems (some were even started with the standard Markdown  
filter and upgraded without issue).


http://github.com/johnmuhl/radiant-markdown-extension


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

[Radiant] what extensions do you have installed?

[john muhl]

I'd like to get some kind of idea what the most popular extensions
are. I'll start, my personal site has (minus the ones packaged with
radiant)

* Bluecloth Filter
* Default Page Parts
* Mailer
* Page Attachments
* RDiscount Markdown Filter
* Shards

I guess Shards gives away that my instance is sort of out of date.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Members Extension Won't Install Correctly

[john muhl]

On Thu, Jan 29, 2009 at 3:28 PM, Adam Farnsworth
 wrote:
> That didn't seem to work:
>
> $ cd vendor/extensions/members/
> $ git submodule init
>No submodule mapping found in .gitmodules for path
> 'vendor/plugins/file_column'
> $ git submodule update
>No submodule mapping found in .gitmodules for path
> 'vendor/plugins/file_column'

That doesn't work because the extension doesn't include a .gitmodules
file in it's repository. Trying to track down the plugin leads to 15
different repositories named "file_column" on GitHub alone. If someone
could point out the exact url of which file_column plugin is needed
that would be most helpful.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Bad Gateway Error

[john muhl]

It looks like Apache is unable to connect to whatever is behind it
serving the ruby requests. Make sure your mongrels or passenger or
whatever are still running.

On Sat, Jan 31, 2009 at 10:48 AM, Peter Soutter
 wrote:
> Hi,
>
> I'm hoping that someone might be able to help me. I run a website
> www.goodtravelcompany.com, which was created using radiant.  For someone
> unexplained reason the website is down and the following error message
> is being displayed:
>
> Bad Gateway
>
> The proxy server received an invalid response from an upstream server.
> Apache/2.0.54 Server at www.goodtravelcompany.com Port 80
>
> I have called my hosting company media temple and they say that the
> problem is in the domain, however, I have made no changes to the website
> recently.  Any idea how I can fix it?
>
> Thanks
> Peter
> --
> Posted via http://www.ruby-forum.com/.
> ___
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Sendfile headers

[john muhl]

i've been using the old x-sendfile patch on nginx and mongrel for about a
year with no blank page issues. after setting up an edge 0.7 in a virtual
machine i was able to run nginx and thin in production mode with no blank
pages in well over a million requests through ab (assuming those blank pages
would report their size differently than the page that was supposed to be
served).

On Mon, Feb 2, 2009 at 9:10 PM, Sean Cribbs  wrote:

> I got blank pages occasionally until I installed mod_xsendfile properly.
>  Then, It Just Worked(tm).
>
> Sean
>
>
> Jason Garber wrote:
>
>> And did it work in production?  When I did exactly that (probably 4 months
>> ago), I found sometimes I would get a blank page or the plain text version
>> of the cache file.  I didn't have time to figure it out, so I just turned it
>> off again.
>>
>> On Feb 2, 2009, at 4:50 PM, Sean Cribbs wrote:
>>
>>  Jason,
>>>
>>> This doesn't affect page_attachments.  For Apache, I compiled and
>>> installed mod_xsendfile, and then added these two directives to my Apache
>>> config:
>>>
>>> XSendfile on
>>> XSendFileAllowAbove on
>>>
>>> And this line to config/environment.rb, inside the after_initialize
>>> block:
>>>
>>> ResponseCache.defaults[:use_x_sendfile] = true
>>>
>>> Sean
>>>
>>> Jason Garber wrote:
>>>
 Sean, did you use my page_attachments_xsendfile extension?  If not, I'm
 curious how you set it up.

 Jason

 On Jan 30, 2009, at 1:23 PM, Sean Cribbs wrote:

  Last night at our little hack session at John's, I added the ability to
> support X-Accel-Redirect headers for nginx.  It would be great if someone
> could test this addition with nginx.  In config/environment.rb, put this
> line inside the config.after_initialize block:
>
> ResponseCache.defaults[:use_x_accel_redirect] = true
>
> Since I have seancribbs.com running the latest and hosted using
> Apache/Passenger, I decided to turn on X-Sendfile headers.  However, 
> Apache
> doesn't seem to recognize them and just serves up a blank response (with 
> the
> X-Sendfile header included in the response).  So my questions are two:
>
> 1) Is this just a side-effect of using Passenger? Would a proxy
> scenario (Mongrel, Thin, etc) work?
> 2) Is there something different Radiant should be doing with other
> headers to make it work?
>
> Additionally, if anyone could look into conditional GETs and make sure
> we're doing it right, that would be great.
>
> Sean
> ___
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>

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


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

Re: [Radiant] Counting Articles

[john muhl]

might try excluding it by url







On Tue, Feb 3, 2009 at 3:03 PM, Steven Southard
wrote:

> I was using   to keep
> track of the number of articles published.  Now I've added an archive month
> index so my count is off by one.  How do I subtract one or exclude the month
> index?
>
> 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

Re: [Radiant] Which "Ba" ?

[john muhl]

http://github.com/aslakhellesoy/ba/network
looks like while there are some other forks their either not active or get
merged with the aslakhellesoy repository regularly.

On Tue, Feb 3, 2009 at 3:06 PM, Anton Aylward wrote:

> I'd like to try out the conference/event management system 'Ba' that I
> see on GitHub.
>
> However there are 4 different copies, and one says it will blow away the
> database on installation!
>
> Can someone advise on which to use, please.
>
> --
> life, n.:
>  A whim of several billion cells to be you for a while.
>
> ___
> 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] Which "Ba" ?

[john muhl]

oops, "they're not maintained"

On Tue, Feb 3, 2009 at 6:28 PM, john muhl  wrote:

> http://github.com/aslakhellesoy/ba/network
> looks like while there are some other forks their either not active or get
> merged with the aslakhellesoy repository regularly.
>
>
> On Tue, Feb 3, 2009 at 3:06 PM, Anton Aylward wrote:
>
>> I'd like to try out the conference/event management system 'Ba' that I
>> see on GitHub.
>>
>> However there are 4 different copies, and one says it will blow away the
>> database on installation!
>>
>> Can someone advise on which to use, please.
>>
>> --
>> life, n.:
>>  A whim of several billion cells to be you for a while.
>>
>> ___
>> 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] Sendfile headers

[john muhl]

what type of system did you install mod_xsendfile on? it's completely broken
for 64bit httpd on osx.

On Tue, Feb 3, 2009 at 6:25 AM, Sean Cribbs  wrote:

> They wouldn't report a different size (all other headers are preserved),
> but the header gives the file a fast-track through the web-server and
> operating system.  Essentially, it tells the OS to stream the file to the
> socket, on OS's that support it.
>
> Sean
>
>
> john muhl wrote:
>
>> i've been using the old x-sendfile patch on nginx and mongrel for about a
>> year with no blank page issues. after setting up an edge 0.7 in a virtual
>> machine i was able to run nginx and thin in production mode with no blank
>> pages in well over a million requests through ab (assuming those blank
>> pages
>> would report their size differently than the page that was supposed to be
>> served).
>>
>> On Mon, Feb 2, 2009 at 9:10 PM, Sean Cribbs  wrote:
>>
>>
>>
>>> I got blank pages occasionally until I installed mod_xsendfile properly.
>>>  Then, It Just Worked(tm).
>>>
>>> Sean
>>>
>>>
>>> Jason Garber wrote:
>>>
>>>
>>>
>>>> And did it work in production?  When I did exactly that (probably 4
>>>> months
>>>> ago), I found sometimes I would get a blank page or the plain text
>>>> version
>>>> of the cache file.  I didn't have time to figure it out, so I just
>>>> turned it
>>>> off again.
>>>>
>>>> On Feb 2, 2009, at 4:50 PM, Sean Cribbs wrote:
>>>>
>>>>  Jason,
>>>>
>>>>
>>>>> This doesn't affect page_attachments.  For Apache, I compiled and
>>>>> installed mod_xsendfile, and then added these two directives to my
>>>>> Apache
>>>>> config:
>>>>>
>>>>> XSendfile on
>>>>> XSendFileAllowAbove on
>>>>>
>>>>> And this line to config/environment.rb, inside the after_initialize
>>>>> block:
>>>>>
>>>>> ResponseCache.defaults[:use_x_sendfile] = true
>>>>>
>>>>> Sean
>>>>>
>>>>> Jason Garber wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Sean, did you use my page_attachments_xsendfile extension?  If not,
>>>>>> I'm
>>>>>> curious how you set it up.
>>>>>>
>>>>>> Jason
>>>>>>
>>>>>> On Jan 30, 2009, at 1:23 PM, Sean Cribbs wrote:
>>>>>>
>>>>>>  Last night at our little hack session at John's, I added the ability
>>>>>> to
>>>>>>
>>>>>>
>>>>>>> support X-Accel-Redirect headers for nginx.  It would be great if
>>>>>>> someone
>>>>>>> could test this addition with nginx.  In config/environment.rb, put
>>>>>>> this
>>>>>>> line inside the config.after_initialize block:
>>>>>>>
>>>>>>> ResponseCache.defaults[:use_x_accel_redirect] = true
>>>>>>>
>>>>>>> Since I have seancribbs.com running the latest and hosted using
>>>>>>> Apache/Passenger, I decided to turn on X-Sendfile headers.  However,
>>>>>>> Apache
>>>>>>> doesn't seem to recognize them and just serves up a blank response
>>>>>>> (with the
>>>>>>> X-Sendfile header included in the response).  So my questions are
>>>>>>> two:
>>>>>>>
>>>>>>> 1) Is this just a side-effect of using Passenger? Would a proxy
>>>>>>> scenario (Mongrel, Thin, etc) work?
>>>>>>> 2) Is there something different Radiant should be doing with other
>>>>>>> headers to make it work?
>>>>>>>
>>>>>>> Additionally, if anyone could look into conditional GETs and make
>>>>>>> sure
>>>>>>> we're doing it right, that would be great.
>>>>>>>
>>>>>>> Sean
>>>>>>> ___
>>>>>>> Radiant mailing list
>>>>>>> Post:   Radiant@radiantcms.org
>>>>>>> Search: http://radiantcms.org/mailing-list/search/
>>>>>>> Site:

[Radiant] Mailer extension oddities

[john muhl]

I'm not sure if it has to do with 0.7.0 or the mailer extension in general
but I am getting odd redirects. For example, I have a contact page like this
http://gist.github.com/60672

When the form submits successfully the user ends gets redirected at
http://example.com/contact/thanks#mailer

When the form is missing some required fields the user gets redirected to
http://example.com/pages/9/mail#mailer

Is there something in my configuration causing the #mailer to get tacked on?
What is up with that url when the form is missing fields? Are these just
side effects of the mailer extension not being completely 0.7.0 compatible?
I'm using the latest commit of the mailer extension and the 0.7.0 final
release frozen in vendor/radiant.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] Re: Mailer extension oddities

[john muhl]

Nevermind I found the esoteric mailer config setting that enforces the
correct behavior. Is there any reason why the strange behavior described
above is the default one?

On Sun, Feb 8, 2009 at 10:32 PM, john muhl  wrote:

> I'm not sure if it has to do with 0.7.0 or the mailer extension in general
> but I am getting odd redirects. For example, I have a contact page like this
> http://gist.github.com/60672
>
> When the form submits successfully the user ends gets redirected at
> http://example.com/contact/thanks#mailer
>
> When the form is missing some required fields the user gets redirected to
> http://example.com/pages/9/mail#mailer
>
> Is there something in my configuration causing the #mailer to get tacked
> on? What is up with that url when the form is missing fields? Are these just
> side effects of the mailer extension not being completely 0.7.0 compatible?
> I'm using the latest commit of the mailer extension and the 0.7.0 final
> release frozen in vendor/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] So what doesn't work with 0.7?

[john muhl]

roughly...

admin_tree_structure
concurrent_draft
dynamic_grouping
exception_notification
file_based_layout
jargon
legacy_path_handler
link_roll
location
page_attachments_xsendfile
page_event
page_group_rbac_migrator
page_meta
page_review_process
page_versioning
rbac_base
rbac_page_edit
rbac_snippets
reorder
snippet_trees
sns
sns_file_system
sns_minifier
sns_sass_filter
subscriber_lists
tags_multi_site
templates
textile_toolbar
top_level_page
translator
twitter


On Mon, Feb 9, 2009 at 2:30 PM, N. Turnage  wrote:

> Since this question is going to be asked a number of times as people begin
> to move their sites to v0.7 I thought I would begin the thread. What
> extensions are known not to work with v0.7?
> ___
> 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] Is there an extension for rotating or random images?

[john muhl]

On Wed, May 13, 2009 at 8:07 AM, N. Turnage  wrote:
> I could have sworn that I had seen an extension that would either load a
> random image or rotate images banner-style, but I cannot find it. I need to
> to be able to set a random background image for a div each time the page is
> loaded/re-loaded. Does anybody know what I am talking about? I thought I had
> seen an extension that would do this one time, but with the serious lack of
> sleep I am experiencing I cannot find it.

not sure about any particular extension but the random/options radius
tags are a part of radiant core.


  a
  b
  c


and since 0.6.9 (i think) the options can be dynamic so if you had
page_attachments installed and a bunch of images attached to a banner
page you could do something like:


  

  

  

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

Re: [Radiant] Problem with Extensions

[john muhl]

http://wiki.github.com/radiant/radiant/installing-extensions

On Thu, May 14, 2009 at 9:02 AM, Mohit Sindhwani  wrote:
> Emanuel Vinzent wrote:
>>
>> thank's!
>>
>> with the underscores in the directiories will should be work ;-)
>>
>
> With the advent of git, we need a FAQ that explains how to rename extension
> directories after the extension is cloned to vendor/extensions.  I guess
> there's a clean way to guess the directory name by looking at the
> _extension.rb in the newly created directory?
>
> Examples:
> * when it's blog_tags_extension.rb -> the directory should be blog_tags;
> * similarly, it's page_attachments when the file is called
> page_attachments_extension.rb
> * and simply enough, gallery when the file is gallery_extension.rb
>
> This should be foolproof, isn't it?  Are there any known extensions that
> tend to use CamelCase (guess not!) or dashed-names (theoretically possible,
> but I haven't seen any).
>
> Cheers,
> Mohit.
> 5/14/2009 | 11:02 PM.
>
>
> ___
> 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] Is there an extension that makes pages from xml?

[john muhl]

http://github.com/seancribbs/radiant-atom-import-extension might be a
place to look for inspiration; as i understand it, you point that
extension at an atom file and it puts the contents into radiant pages.

On Wed, May 20, 2009 at 9:50 AM, Chaim Kirby
 wrote:
> I am working on an academic webpage, and there is a desire to list
> publications. No one wants to retype all of the publications for the
> department.
>
> Ideally I would like a workflow of: 1)Export xml from EndNote 2)Click
> "Make Pages" button in radiant 3)Paste xml
> 4)End up with how ever many pages in radiant as there were records in
> the xml.
>
> I am already using the page_parts extension for the parent of these
> pages, so I think that the ruby side would be
> 1)Create Page
> 2)Parse xml tags
> 3)Link xml tags to page parts
> 4)place xml data into correct page part
> 5)publish page
> 6)Rinse, repeat
>
> Is there anything that gets me close, or should I be looking at rolling
> my own from scratch? (I would also be interested in extensions that do
> some part of me desired workflow, if only to scavenge code)
>
> Thanks,
> Chaim Kirby
>
> chaim.ki...@childrens.harvard.edu
> Children's Hospital Informatics Program
> Children's Hospital Boston
>
> ___
> 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] Radiant Inheritance?

[john muhl]

I've tried all the existing solutions and have come to the sad
realization none of them work right. with the latest versions of
radiant. if you find something that works please do share.

On Sun, May 24, 2009 at 8:15 PM, Alexis Masters  wrote:
> Hello! I am working again on http://www.wizardofpaws.us and I'm trying to
> figure out how to make "child" pages have the same page structure as their
> parent page. I am virtually certain that my site user will *not* remember to
> add a summary page part when she writes a new article. I had assumed that
> when I made child pages they would inherit the same basic structure as a
> parent page, which in this case is "body" and "summary" -- but to my
> disappointment they do not seem to inherit anything but "body." I think I
> must be doing something wrong or may have overlooked something. Any
> help/advice you can share will be most appreciated.
> ~ Alexis
> =
> Alexis Masters, author and web developer
> http://www.alexismasters.com
> 510 234-0027
>
>
>
> ___
> 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] At my wit's end with Mailer --> (see Mailer.valid_config?)

[john muhl]

maybe trying putting the subject in quotes, the spaces might be choking it up

...
subject: "Thank You"
...

On Mon, May 25, 2009 at 8:31 AM, N. Turnage  wrote:
> I have set up Mailer on 3 different websites and the first two worked right
> out of the box, but the third is not working even though it's set up no
> different than the others. No matter what I push or pull on, I still get the
> "(see Mailer.valid_config?) " error when I try and view the 'Contact' page.
> The content for my page parts is this:
>
>
> Body:
> ...
> 
> 
> ...
>
> mailer:
> ...
> subject: Thank you
> from: he...@goodtastewithtanji.com
> redirect_to: /contact/thank-you/
> recipients:
>  - pixeln...@gmail.com
> ...
>
> email:
> ...
> This is a message from 
> ...
>
> This is my ActionMailer settings from the bottom of the
> 'config.after_initialize' block:
> ...
> # ActionMailer settings for use by the Mailer extension
>   ActionMailer::Base.smtp_settings = {
>     :address => "mail.goodtastewithtanji.com",
>     :domain => "goodtastewithtanji.com",
>     :user_name => "hello+goodtastewithtanji.com",
>     :password => "myrealpassword",
>     :authentication => :login
>   }
> ...
>
> And yes I have removed action_mailer from 'config.frameworks -= []'.
>
>
> Is there anything else I can check or do even if it only means that the
> error changes? I have been banging my head on this for the last two days. I
> have tried reinstalling the extension (3times), moving things around in my
> environment, and nothing works. I don't know what else to do. Any
> help/pointer/criticism appreciated.
>
>
>
>
> ~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] Deploying Radiant on Dreamhost - Passenger Won't Start

[john muhl]

On Tue, Jun 2, 2009 at 2:34 PM, Adam Farnsworth  wrote:
> rake ray:restart --trace
> (in /home/adamgotdiana/adamgotdiana.com)
> rake aborted!
> Don't know how to build task 'ray:restart'

there is no ray:restart task.

maybe you wanted the ray:setup:restart server=passenger task which
does not restart the server itself, instead it tries to restart it
when necessary, after successful extension install for example.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] We need to talk about extension versions

[john muhl]

On Tue, Jun 9, 2009 at 5:59 AM, Jim Gay wrote:
> On Jun 9, 2009, at 6:51 AM, Jason Garber wrote:
>
>> My suggestions for requirements:
>> 1.) Extension authors have a way of specifying a minimum Radiant version
>> with each release/revision of the extension.
>
> I chatted with John Muhl about this and I believe he implemented a
> minimum/maximum Radiant version requirement in Ray ( in addition to the way
> it handles dependencies).

yep, in a dependency.yml file use radiant_min_version and/or
radiant_max_version, it's undocumented but there.

currently it only works on your extension's extension dependencies
since that was what Jim's use case called for, but there are plans to
move it to the top level so you could apply the version constraints
directly to the extension being installed, essentially making some
version(s) of radiant a dependency for your extension.

---
- extension: ext_name
  - radiant_min_version: 0.6.9 #current

---
- radiant_max_version: 0.6.9 #future

assuming extension authors start creating tags like 0.6.9, 0.7.0,
0.7.1 etc. i don't see why ray couldn't grab your radiant version and
check for a tag that matches before just going after the latest
version, i.e. master branch.

>> 4.) The extension install script installs the latest compatible version of
>> an extension.
>
> Definitely needed. Currently the registry only provides a compatible Radiant
> version as an FYI and it's totally flat (only one version can be managed).

any one know an extension that already uses tags like this? i'd like
to get this working in ray.

>> 5.) Easy upgrades.  One command to upgrade Radiant and all my extensions.

rake ray:extension:update name=all - it won't upgrade your radiant but
any installed extensions would be

> In addition, I think it would make complete sense to remove this page from
> the wiki http://wiki.github.com/radiant/radiant/thirdparty-extensions

i agree, just delete it, it's a relic from the pre-registry past and
only adds confusion for new users and waste the time of anyone still
listing their extension there.

> Encouraging authors to put their content into the registry is long overdue.

maybe script/generate extension NewExtension could encourage authors
to add their extension to the registry.

> I've been meaning to, but haven't had time, add a feature to the registry
> where you can add an extension to the registry without an author (because
> you might find an extension on github but the author hasn't signed up at the
> registry), and later claim an orphaned extension as your own.

anything that gets the extension list at the registry more complete
sounds good to me.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Insert rss

[john muhl]

http://wiki.github.com/radiant/radiant/create-a-rss-feed

On Thu, Jun 11, 2009 at 8:11 AM, Mauricio Dulce wrote:
>
> Hello, it is possible to insert an rss within a snippets
> ___
> 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] Re: Creating a UL/IMG based Navigation Bar

[john muhl]

On Mon, Jun 15, 2009 at 3:12 PM, Jeff Casimir wrote:
> Benny,
>
> instead of getting the slug for that element I got the slug for the current 
> page.

you are getting the current page slug because radius tags render
within the context from which they're called. to get around that and
at the slug for each page in an iteration you can do something like:


> And, actually, using the "r:url" works better than expected.  In the
> situation of...
>
> http://site.com/branch/leaf/
>
> The r:url is correctly pulling "branch".
>
> So I guess what I'm saying, is that I agree it should be wrong, but it
> works?  Do you see different results?
>
> As far as the CSS image substitution, you're probably right that it
> would be a better setup, but this is ok for me right now.
>
> - Jeff
>
> On Mon, Jun 15, 2009 at 4:13 AM, Benny
> Degezelle wrote:
>> Hi Jeff,
>>
>> Sorry, but that snippet looks like a recipe for disaster.. Here's some
>> feedback;
>>
>> 1/ You use  as part of the image name. This means that, when you
>> have deeper-nested pages, you would get image names like
>> "products/cats.gif", which is not going to work. You could use 
>> instead, which would only produce "cats.gif".
>>
>> 2/ You don't seem to understand the use of the r:navigation tag;
>>
>> 
>>
>> It's supposed to be something like urls="Blog: /news | About us: /about |
>> Contact us: /contact"
>>
>> 3/ You use only images as content for your links. The fallback (alt
>> attribute) is just the url, which makes for a very poor navigation for
>> clients that cannot see images (think people surfing through WAP, people
>> with a visual handicap, and probably foremost; spider bots like google and
>> the like).
>> What you need to do is provide a text entry that makes more sense as
>> linktext, and then replace that text with the image you want through CSS.
>> You will need a unique id attribute on your  and/or  tags.
>>
>> 4/ Perhaps you should look into the navigation_tags extension. The 
>> tag could make your life much easier.
>> Since you want to use images, you would want to use ids_for_links="true" or
>> ids_for_lis="true".
>> Check the (somewhat outdated) README at
>> http://github.com/jomz/navigation_tags/tree/master
>> I can not provide too much details about the CSS implementation, since that
>> is my colleague's part of the job, but you can see a live implementation at
>> http://www.indewulf.be. Also notice the plethora of handy css hooks r:nav
>> provides.
>>
>> Regards,
>> Benny
>>
>>
>>> Hi All,
>>>
>>> Today is my first day building my site with Radiant -- I'm loving it!
>>>
>>> Once I got the basic layout, snippets, and pages implemented, I had to
>>> figure out my navigation bar.  It took me some tinkering, so I thought
>>> I'd post the results on the wiki:
>>>
>>>
>>> http://wiki.github.com/radiant/radiant/creating-a-ul-img-based-navigation-bar
>>>
>>> I'd appreciate any feedback or redirection if I did something ugly.  I
>>> wrestled with the wiki for a few minutes trying to figure out why
>>> those extra grey spaces were showing up under each code block, but I
>>> didn't crack the problem.
>>>
>>> - Jeff
>>>
>> ___
>> Radiant mailing list
>> Post:   Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Increasing Page Cache Timeout

[john muhl]

On Tue, Jun 30, 2009 at 11:20 PM, Mohit Sindhwani wrote:
> Hi, just a quick question - how do I increase the page caching from 5
> minutes to something much more?
>
> My site has mostly static content other than the use of the comments
> extension which itself clears the cache when the page changes.  I think it
> would make a great difference to the performance to set the cache time out
> to a much larger value.
>
> My understanding is that I should add a line to
> MYRADIANTAPP/config/environment.rb where it says:
>   # Response Caching Defaults
>   ResponseCache.defaults[:directory] =
> ActionController::Base.page_cache_directory
>   ResponseCache.defaults[:logger]    = ActionController::Base.logger

i can't recall exactly how it worked in 0.7 (search the radiant source
for "5.minutes" and you'll find the code that controls it) but in 0.8
there is a method on SiteController called cache_timeout that you use
to set the timeout to whatever you like. i stuck
`SiteController.cache_timeout = 60.minutes` in environment.rb fired up
a rails console, ran SiteController.cache_timeout.value and sure
enough i get 3600 back.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Is SQLite + Radiant very slow?

[john muhl]

my guess is it has nothing to do with sqlite which in my experience is
plenty fast. i'd make sure you're running in the production
environment, with lots of extensions the development environment can
get real slow real fast.

On Thu, Jul 2, 2009 at 8:47 AM, Mohit Sindhwani wrote:
> Hi, I'm just playing around with a Radiant 0.7.1 site with a bunch of
> extensions.  I find that generating a page the first time takes very very
> long - I'm seeing it in the region of 3 seconds - 30 seconds!  Of course, if
> it's cached, it's fine - it's fast.
>
> It's deployed on 2 Mongrels; seems sqlite3 is v3.4.2
>
> I looked at the log and I'm seeing things like:
> Processing SiteController#show_page (for 216.129.119.49 at 2009-07-02
> 08:55:50) [GET]
>  Parameters: {"action"=>"show_page", "url"=>["en", "spec", "t-kernel",
> "1.00", "tkernel_os", "extended_synchronization_and_communication",
> "message_buffer", "tk_cre_mbf"], "controller"=>"site"}
> Completed in 23.40224 (0 reqs/sec) | DB: 6.10926 (26%) | 200 OK
> [http://t-engine.info/en/spec/t-kernel/1.00/tkernel_os/extended_synchronization_and_communication/message_buffer/tk_cre_mbf/]
>
>
> Processing SiteController#show_page (for 216.129.119.49 at 2009-07-02
> 08:58:28) [GET]
>  Parameters: {"action"=>"show_page", "url"=>["en", "spec", "ut-kernel",
> "1.01", "functions", "time_management", "system_time"],
> "controller"=>"site"}
> Completed in 2.85429 (0 reqs/sec) | DB: 2.28977 (80%) | 200 OK
> [http://t-engine.info/en/spec/ut-kernel/1.01/functions/time_management/system_time/]
>
>
> Processing SiteController#show_page (for 216.129.119.49 at 2009-07-02
> 09:01:06) [GET]
>  Parameters: {"action"=>"show_page", "url"=>["en", "spec", "t-engine",
> "1.01", "cpu_board_interface_spec", "usb_host"], "controller"=>"site"}
> Completed in 19.33309 (0 reqs/sec) | DB: 13.02903 (67%) | 200 OK
> [http://t-engine.info/en/spec/t-engine/1.01/cpu_board_interface_spec/usb_host/]
>
>
> Processing SiteController#show_page (for 218.186.65.65 at 2009-07-02
> 09:27:42) [GET]
>  Parameters: {"action"=>"show_page", "url"=>["en", "spec"],
> "controller"=>"site"}
> Completed in 30.12451 (0 reqs/sec) | DB: 27.00055 (89%) | 200 OK
> [http://www.t-engine.info/en/spec]
>
> Any suggestions on what I can do?
>
> Cheers,
> Mohit.
> 7/2/2009 | 10:45 PM.
>
> ___
> 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] Question about extension installation

[john muhl]

you might have a look at:
http://wiki.github.com/radiant/radiant/installing-extensions and see
if that helps at all.

On Mon, Jul 6, 2009 at 3:40 PM, Wentao Wang wrote:
> Hey all,
>
> I am a rookie user of radiant CMS. Currently I am stuck by the extenstion
> installation (blog extension, and sns extension). What I did was to download
> the extension zip file, unpack it into my project directory
> (...vendor/extensions). And then I ran the command "rake production db:
> migrate: extensions"
> It gave me the following error message:
> Could not load extension from file: blog_extension.
> #
> Could not load extension from file: sns_extension.
> #
> rake aborted!
> Don't know how to build task 'db:'
>
> I assume it might be configuration issue. I am using Windows Vista and the
> latest version of radiant version.
>
> But this is only my guess. Anyone have any idea with my problem. Any
> suggestions are appreciated.
>
> --
> Thank you for your time and patience!
>
> Best,
>
> Wentao Wang
> ___
> 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] xhtml upgrade path

[john muhl]

it means nothing for radiant so far as i can tell, or am i missing
something? the admin interface's html is not important (to me at
least) and you've always been able to build the front end of your site
using any markup language you like.

On Tue, Jul 7, 2009 at 4:21 AM, Jan M.J. Storms wrote:
> Taken from "An Unofficial Q&A about the Discontinuation of the XHTML2
> WG" at :
>
> "What’s the upgrade path from XHTML 1.x?
> For the technical kind of XHTML 1.x—that is, XHTML served as application/
> xhtml+xml—the upgrade path is to XHTML5. For the marketing kind of XHTML
> 1.x—that is, XHTML served as text/html—the upgrade path is to HTML5.
> Moreover, “HTML5” replaces “XHTML” (and “Ajax”!) as the coolest
> marketing buzzword."
>
> I wonder what this means for Radiant CMS pages.
>
> Jan
> ___
> 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] mailer extension and 0.8

[john muhl]

has anyone successfully used mailer on 0.8? whenever i try to send
mail i get a 500 error page and the following:

  SQL (1.2ms)SELECT name
 FROM sqlite_master
 WHERE type = 'table' AND NOT name = 'sqlite_sequence'

  SQL (1.9ms)   SELECT DISTINCT class_name FROM pages WHERE class_name
<> '' AND class_name IS NOT NULL
/!\ FAILSAFE /!\  Wed Jul 08 09:01:58 -0600 2009
  Status: 500 Internal Server Error
  wrong number of arguments (1 for 2)

/private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
`restore_response'

/private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
`invalidate'

/private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
`map'

/private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
`invalidate'

/private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in
`invalidate'

/private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in
`call!'

/private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in
`call'
/opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in `call'
/opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in
`call'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in
`call'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in
`call'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in
`call'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in
`call'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in
`call'
/opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call'
/opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in
`synchronize'
/opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in `call'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in
`call'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/cgi_process.rb:44:in
`dispatch_cgi'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:102:in
`dispatch_cgi'

/private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:28:in
`dispatch'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:81:in
`call'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:69:in
`call'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:76:in
`pre_process'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in
`catch'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in
`pre_process'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:57:in
`process'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:42:in
`receive_data'

/opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib/eventmachine.rb:242:in
`run_machine'

/opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib/eventmachine.rb:242:in
`run'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/backends/base.rb:57:in
`start'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/server.rb:156:in `start'

/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/controllers/controller.rb:80:in
`start'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/runner.rb:174:in `send'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/runner.rb:174:in
`run_command'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/runner.rb:140:in `run!'
/opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/bin/thin:6
/opt/ree/bin/thin:19:in `load'
/opt/ree/bin/thin:19
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] mailer extension and 0.8

[john muhl]

thanks but it gives the same error.

On Wed, Jul 8, 2009 at 10:02 AM, Cristi Duma wrote:
> Hi John,
>
> I'm playing with it right now, tried some fixes, features and stuff
>
> It works for me on a site I'm currently developing
>
> Check it out: http://github.com/Aissac/radiant-mailer-extension/tree/master
>
> On 7/8/09 6:05 PM, john muhl wrote:
>>
>> has anyone successfully used mailer on 0.8? whenever i try to send
>> mail i get a 500 error page and the following:
>>
>>   SQL (1.2ms)    SELECT name
>>  FROM sqlite_master
>>  WHERE type = 'table' AND NOT name = 'sqlite_sequence'
>>
>>   SQL (1.9ms)   SELECT DISTINCT class_name FROM pages WHERE class_name
>> <>  '' AND class_name IS NOT NULL
>> /!\ FAILSAFE /!\  Wed Jul 08 09:01:58 -0600 2009
>>   Status: 500 Internal Server Error
>>   wrong number of arguments (1 for 2)
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
>> `restore_response'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
>> `invalidate'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
>> `map'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
>> `invalidate'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in
>> `invalidate'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in
>> `call!'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in
>> `call'
>>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in
>> `call'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in
>> `call'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in
>> `call'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in
>> `call'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in
>> `call'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in
>> `call'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in
>> `call'
>>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in
>> `call'
>>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in
>> `synchronize'
>>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in
>> `call'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:106:in
>> `call'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/cgi_process.rb:44:in
>> `dispatch_cgi'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:102:in
>> `dispatch_cgi'
>>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:28:in
>> `dispatch'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:81:in
>> `call'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/rack/adapter/rails.rb:69:in
>> `call'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:76:in
>> `pre_process'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in
>> `catch'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:74:in
>> `pre_process'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:57:in
>> `process'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/connection.rb:42:in
>> `receive_data'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib/eventmachine.rb:242:in
>> `run_machine'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/eventmachine-0.12.8/lib/eventmachine.rb:242:in
>> `run'
>>
>> /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/backends/base.rb:57:in
>> `start'
>>     /opt/ree/lib/ruby/gems/1.8/gems/thin-1.2.2/lib/thin/server.rb:156:in
>> `start'
>>
>> 

Re: [Radiant] mailer extension and 0.8

[john muhl]

this is running locally in the development environment. i've tested
with webrick, mongrel, thin and passenger and they all have the same
error message until you get to server specific part. the test site is
the styled blog with only the mailer extension added. all the page
parts and environment.rb are here: http://gist.github.com/142995 - i
also have mailer.post_to_page? = true set.

just to make sure it wasn't inherent in the system i setup a styled
blog with 0.7.1 installed mailer, used the same parts and smtp
settings and was able to send mail on all 4 servers.

thanks for help.

On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hoka wrote:
> John, it looks like you are getting this on your production machine where
> you are using Thin. Could you test with Passenger or Mongrel, perhaps
> locally and see if you get the same error?
> Also, could you provide some more context? For instance, are you trying to
> attach a file or is it a simple form you are mailing?
>
> Cheers!
> --
> Istvan Hoka
>
>
> On Wed, Jul 8, 2009 at 7:34 PM, john muhl  wrote:
>
>> thanks but it gives the same error.
>>
>> On Wed, Jul 8, 2009 at 10:02 AM, Cristi Duma wrote:
>> > Hi John,
>> >
>> > I'm playing with it right now, tried some fixes, features and stuff
>> >
>> > It works for me on a site I'm currently developing
>> >
>> > Check it out:
>> http://github.com/Aissac/radiant-mailer-extension/tree/master
>> >
>> > On 7/8/09 6:05 PM, john muhl wrote:
>> >>
>> >> has anyone successfully used mailer on 0.8? whenever i try to send
>> >> mail i get a 500 error page and the following:
>> >>
>> >>   SQL (1.2ms)    SELECT name
>> >>  FROM sqlite_master
>> >>  WHERE type = 'table' AND NOT name = 'sqlite_sequence'
>> >>
>> >>   SQL (1.9ms)   SELECT DISTINCT class_name FROM pages WHERE class_name
>> >> <>  '' AND class_name IS NOT NULL
>> >> /!\ FAILSAFE /!\  Wed Jul 08 09:01:58 -0600 2009
>> >>   Status: 500 Internal Server Error
>> >>   wrong number of arguments (1 for 2)
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
>> >> `restore_response'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
>> >> `invalidate'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
>> >> `map'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
>> >> `invalidate'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in
>> >> `invalidate'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in
>> >> `call!'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in
>> >> `call'
>> >>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in
>> >> `call'
>> >>
>> >>
>> /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in
>> >> `call'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in
>> >> `call'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in
>> >> `call'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in
>> >> `call'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in
>> >> `call'
>> >>
>> >>
>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/failsafe.rb:11:in
>> >> `call'
>> >>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in
>> >> `call'
>> >>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in
>> >> `synchronize'
>> >>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/lock.rb:11:in
>> >> `cal

Re: [Radiant] mailer extension and 0.8

[john muhl]

oh, and those results are the same with radiant/mailer or aissac/mailer

On Wed, Jul 8, 2009 at 11:43 AM, john muhl wrote:
> this is running locally in the development environment. i've tested
> with webrick, mongrel, thin and passenger and they all have the same
> error message until you get to server specific part. the test site is
> the styled blog with only the mailer extension added. all the page
> parts and environment.rb are here: http://gist.github.com/142995 - i
> also have mailer.post_to_page? = true set.
>
> just to make sure it wasn't inherent in the system i setup a styled
> blog with 0.7.1 installed mailer, used the same parts and smtp
> settings and was able to send mail on all 4 servers.
>
> thanks for help.
>
> On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hoka wrote:
>> John, it looks like you are getting this on your production machine where
>> you are using Thin. Could you test with Passenger or Mongrel, perhaps
>> locally and see if you get the same error?
>> Also, could you provide some more context? For instance, are you trying to
>> attach a file or is it a simple form you are mailing?
>>
>> Cheers!
>> --
>> Istvan Hoka
>>
>>
>> On Wed, Jul 8, 2009 at 7:34 PM, john muhl  wrote:
>>
>>> thanks but it gives the same error.
>>>
>>> On Wed, Jul 8, 2009 at 10:02 AM, Cristi Duma wrote:
>>> > Hi John,
>>> >
>>> > I'm playing with it right now, tried some fixes, features and stuff
>>> >
>>> > It works for me on a site I'm currently developing
>>> >
>>> > Check it out:
>>> http://github.com/Aissac/radiant-mailer-extension/tree/master
>>> >
>>> > On 7/8/09 6:05 PM, john muhl wrote:
>>> >>
>>> >> has anyone successfully used mailer on 0.8? whenever i try to send
>>> >> mail i get a 500 error page and the following:
>>> >>
>>> >>   SQL (1.2ms)    SELECT name
>>> >>  FROM sqlite_master
>>> >>  WHERE type = 'table' AND NOT name = 'sqlite_sequence'
>>> >>
>>> >>   SQL (1.9ms)   SELECT DISTINCT class_name FROM pages WHERE class_name
>>> >> <>  '' AND class_name IS NOT NULL
>>> >> /!\ FAILSAFE /!\  Wed Jul 08 09:01:58 -0600 2009
>>> >>   Status: 500 Internal Server Error
>>> >>   wrong number of arguments (1 for 2)
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
>>> >> `restore_response'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
>>> >> `invalidate'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
>>> >> `map'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
>>> >> `invalidate'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in
>>> >> `invalidate'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in
>>> >> `call!'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:50:in
>>> >> `call'
>>> >>     /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/head.rb:9:in
>>> >> `call'
>>> >>
>>> >>
>>> /opt/ree/lib/ruby/gems/1.8/gems/rack-1.0.0/lib/rack/methodoverride.rb:24:in
>>> >> `call'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in
>>> >> `call'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/rewindable_input.rb:25:in
>>> >> `call'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:93:in
>>> >> `call'
>>> >>
>>> >>
>>> /private/tmp/mailer/vendor/radiant/vendor/rails/actionpack/lib/action_controller/reloader.rb:9:in
>>> >

Re: [Radiant] mailer extension and 0.8

[john muhl]

same error with the smtp settings in development.rb

On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hoka wrote:
> Could you try moving the contents of your config.after_initialize block to
> development.rb or production.rb?
> --
> Istvan Hoka
>
>
> On Wed, Jul 8, 2009 at 8:47 PM, john muhl  wrote:
>
>> oh, and those results are the same with radiant/mailer or aissac/mailer
>>
>> On Wed, Jul 8, 2009 at 11:43 AM, john muhl wrote:
>> > this is running locally in the development environment. i've tested
>> > with webrick, mongrel, thin and passenger and they all have the same
>> > error message until you get to server specific part. the test site is
>> > the styled blog with only the mailer extension added. all the page
>> > parts and environment.rb are here: http://gist.github.com/142995 - i
>> > also have mailer.post_to_page? = true set.
>> >
>> > just to make sure it wasn't inherent in the system i setup a styled
>> > blog with 0.7.1 installed mailer, used the same parts and smtp
>> > settings and was able to send mail on all 4 servers.
>> >
>> > thanks for help.
>> >
>> > On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hoka
>> wrote:
>> >> John, it looks like you are getting this on your production machine
>> where
>> >> you are using Thin. Could you test with Passenger or Mongrel, perhaps
>> >> locally and see if you get the same error?
>> >> Also, could you provide some more context? For instance, are you trying
>> to
>> >> attach a file or is it a simple form you are mailing?
>> >>
>> >> Cheers!
>> >> --
>> >> Istvan Hoka
>> >>
>> >>
>> >> On Wed, Jul 8, 2009 at 7:34 PM, john muhl  wrote:
>> >>
>> >>> thanks but it gives the same error.
>> >>>
>> >>> On Wed, Jul 8, 2009 at 10:02 AM, Cristi Duma
>> wrote:
>> >>> > Hi John,
>> >>> >
>> >>> > I'm playing with it right now, tried some fixes, features and stuff
>> >>> >
>> >>> > It works for me on a site I'm currently developing
>> >>> >
>> >>> > Check it out:
>> >>> http://github.com/Aissac/radiant-mailer-extension/tree/master
>> >>> >
>> >>> > On 7/8/09 6:05 PM, john muhl wrote:
>> >>> >>
>> >>> >> has anyone successfully used mailer on 0.8? whenever i try to send
>> >>> >> mail i get a 500 error page and the following:
>> >>> >>
>> >>> >>   SQL (1.2ms)    SELECT name
>> >>> >>  FROM sqlite_master
>> >>> >>  WHERE type = 'table' AND NOT name = 'sqlite_sequence'
>> >>> >>
>> >>> >>   SQL (1.9ms)   SELECT DISTINCT class_name FROM pages WHERE
>> class_name
>> >>> >> <>  '' AND class_name IS NOT NULL
>> >>> >> /!\ FAILSAFE /!\  Wed Jul 08 09:01:58 -0600 2009
>> >>> >>   Status: 500 Internal Server Error
>> >>> >>   wrong number of arguments (1 for 2)
>> >>> >>
>> >>> >>
>> >>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
>> >>> >> `restore_response'
>> >>> >>
>> >>> >>
>> >>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:94:in
>> >>> >> `invalidate'
>> >>> >>
>> >>> >>
>> >>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
>> >>> >> `map'
>> >>> >>
>> >>> >>
>> >>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/metastore.rb:93:in
>> >>> >> `invalidate'
>> >>> >>
>> >>> >>
>> >>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:137:in
>> >>> >> `invalidate'
>> >>> >>
>> >>> >>
>> >>>
>> /private/tmp/mailer/vendor/radiant/vendor/rack-cache/lib/rack/cache/context.rb:69:in
>> >>> >> `call!'
>> >>> >>
>> >>> >>
>> >>>
>>

Re: [Radiant] mailer extension and 0.8

[john muhl]

i went down through the code and think i may have found the issue
which appears to be at the radiant level. thanks again for all the
help.

On Wed, Jul 8, 2009 at 1:10 PM, Cristi Duma wrote:
> I created a radiant project with the code from the gist you supplied, and
> after putting the config.after_initialize block in development.rb worked
> flawlessly. So is there the possibility that the problem is not in
> mailer_extension?
>
>
> On 7/8/09 9:58 PM, john muhl wrote:
>>
>> same error with the smtp settings in development.rb
>>
>> On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hoka
>>  wrote:
>>
>>>
>>> Could you try moving the contents of your config.after_initialize block
>>> to
>>> development.rb or production.rb?
>>> --
>>> Istvan Hoka
>>>
>>>
>>> On Wed, Jul 8, 2009 at 8:47 PM, john muhl  wrote:
>>>
>>>
>>>>
>>>> oh, and those results are the same with radiant/mailer or aissac/mailer
>>>>
>>>> On Wed, Jul 8, 2009 at 11:43 AM, john muhl  wrote:
>>>>
>>>>>
>>>>> this is running locally in the development environment. i've tested
>>>>> with webrick, mongrel, thin and passenger and they all have the same
>>>>> error message until you get to server specific part. the test site is
>>>>> the styled blog with only the mailer extension added. all the page
>>>>> parts and environment.rb are here: http://gist.github.com/142995 - i
>>>>> also have mailer.post_to_page? = true set.
>>>>>
>>>>> just to make sure it wasn't inherent in the system i setup a styled
>>>>> blog with 0.7.1 installed mailer, used the same parts and smtp
>>>>> settings and was able to send mail on all 4 servers.
>>>>>
>>>>> thanks for help.
>>>>>
>>>>> On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hoka
>>>>>
>>>>
>>>> wrote:
>>>>
>>>>>>
>>>>>> John, it looks like you are getting this on your production machine
>>>>>>
>>>>
>>>> where
>>>>
>>>>>>
>>>>>> you are using Thin. Could you test with Passenger or Mongrel, perhaps
>>>>>> locally and see if you get the same error?
>>>>>> Also, could you provide some more context? For instance, are you
>>>>>> trying
>>>>>>
>>>>
>>>> to
>>>>
>>>>>>
>>>>>> attach a file or is it a simple form you are mailing?
>>>>>>
>>>>>> Cheers!
>>>>>> --
>>>>>> Istvan Hoka
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 8, 2009 at 7:34 PM, john muhl  wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> thanks but it gives the same error.
>>>>>>>
>>>>>>> On Wed, Jul 8, 2009 at 10:02 AM, Cristi Duma
>>>>>>>
>>>>
>>>> wrote:
>>>>
>>>>>>>>
>>>>>>>> Hi John,
>>>>>>>>
>>>>>>>> I'm playing with it right now, tried some fixes, features and stuff
>>>>>>>>
>>>>>>>> It works for me on a site I'm currently developing
>>>>>>>>
>>>>>>>> Check it out:
>>>>>>>>
>>>>>>>
>>>>>>> http://github.com/Aissac/radiant-mailer-extension/tree/master
>>>>>>>
>>>>>>>>
>>>>>>>> On 7/8/09 6:05 PM, john muhl wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> has anyone successfully used mailer on 0.8? whenever i try to send
>>>>>>>>> mail i get a 500 error page and the following:
>>>>>>>>>
>>>>>>>>>   SQL (1.2ms)    SELECT name
>>>>>>>>>  FROM sqlite_master
>>>>>>>>>  WHERE type = 'table' AND NOT name = 'sqlite_sequence'
>>>>>>>>>
>>>>>>>>>   SQL (1.9ms)   SELECT DISTINCT class_name FROM pages WHERE
>>>>>>>>>
>>>>
>>>> class_name
>>>>
>>>>>>

Re: [Radiant] mailer extension and 0.8

[john muhl]

yes, of course. i'm just not convinced it's the proper fix, it just
happened to be the most expedient one. here is the diff for the
curious:

diff --git a/lib/radiant/cache.rb b/lib/radiant/cache.rb
index a82..2e16de9 100644
--- a/lib/radiant/cache.rb
+++ b/lib/radiant/cache.rb
@@ -48,7 +48,7 @@ module Radiant
   end

   private
-  def restore_response(hash, body)
+  def restore_response(hash, body=nil)
 # Cribbed from the Rack::Cache source
 status = hash.delete('X-Status').to_i
 response = Rack::Cache::Response.new(status, hash, body)


On Wed, Jul 8, 2009 at 1:56 PM, Victor Elsendoorn wrote:
> Only mentioning you fixed it, won't do any help for the Radiant community.
> Please inform us about the solution or bugs you have found.
>
> Thanks in advance.
>
>
> On Jul 8, 2009, at 9:51 PM, john muhl wrote:
>
>> i went down through the code and think i may have found the issue
>> which appears to be at the radiant level. thanks again for all the
>> help.
>>
>> On Wed, Jul 8, 2009 at 1:10 PM, Cristi Duma wrote:
>>>
>>> I created a radiant project with the code from the gist you supplied, and
>>> after putting the config.after_initialize block in development.rb worked
>>> flawlessly. So is there the possibility that the problem is not in
>>> mailer_extension?
>>>
>>>
>>> On 7/8/09 9:58 PM, john muhl wrote:
>>>>
>>>> same error with the smtp settings in development.rb
>>>>
>>>> On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hoka
>>>>  wrote:
>>>>
>>>>>
>>>>> Could you try moving the contents of your config.after_initialize block
>>>>> to
>>>>> development.rb or production.rb?
>>>>> --
>>>>> Istvan Hoka
>>>>>
>>>>>
>>>>> On Wed, Jul 8, 2009 at 8:47 PM, john muhl  wrote:
>>>>>
>>>>>
>>>>>>
>>>>>> oh, and those results are the same with radiant/mailer or
>>>>>> aissac/mailer
>>>>>>
>>>>>> On Wed, Jul 8, 2009 at 11:43 AM, john muhl  wrote:
>>>>>>
>>>>>>>
>>>>>>> this is running locally in the development environment. i've tested
>>>>>>> with webrick, mongrel, thin and passenger and they all have the same
>>>>>>> error message until you get to server specific part. the test site is
>>>>>>> the styled blog with only the mailer extension added. all the page
>>>>>>> parts and environment.rb are here: http://gist.github.com/142995 - i
>>>>>>> also have mailer.post_to_page? = true set.
>>>>>>>
>>>>>>> just to make sure it wasn't inherent in the system i setup a styled
>>>>>>> blog with 0.7.1 installed mailer, used the same parts and smtp
>>>>>>> settings and was able to send mail on all 4 servers.
>>>>>>>
>>>>>>> thanks for help.
>>>>>>>
>>>>>>> On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hoka
>>>>>>>
>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>>>>
>>>>>>>> John, it looks like you are getting this on your production machine
>>>>>>>>
>>>>>>
>>>>>> where
>>>>>>
>>>>>>>>
>>>>>>>> you are using Thin. Could you test with Passenger or Mongrel,
>>>>>>>> perhaps
>>>>>>>> locally and see if you get the same error?
>>>>>>>> Also, could you provide some more context? For instance, are you
>>>>>>>> trying
>>>>>>>>
>>>>>>
>>>>>> to
>>>>>>
>>>>>>>>
>>>>>>>> attach a file or is it a simple form you are mailing?
>>>>>>>>
>>>>>>>> Cheers!
>>>>>>>> --
>>>>>>>> Istvan Hoka
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Jul 8, 2009 at 7:34 PM, john muhl
>>>>>>>>  wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> thanks but it giv

Re: [Radiant] mailer extension and 0.8

[john muhl]

the issue seems to have resolved itself with radiant edge.

On Wed, Jul 8, 2009 at 2:20 PM, john muhl wrote:
> yes, of course. i'm just not convinced it's the proper fix, it just
> happened to be the most expedient one. here is the diff for the
> curious:
>
> diff --git a/lib/radiant/cache.rb b/lib/radiant/cache.rb
> index a82..2e16de9 100644
> --- a/lib/radiant/cache.rb
> +++ b/lib/radiant/cache.rb
> @@ -48,7 +48,7 @@ module Radiant
>       end
>
>       private
> -      def restore_response(hash, body)
> +      def restore_response(hash, body=nil)
>         # Cribbed from the Rack::Cache source
>         status = hash.delete('X-Status').to_i
>         response = Rack::Cache::Response.new(status, hash, body)
>
>
> On Wed, Jul 8, 2009 at 1:56 PM, Victor Elsendoorn 
> wrote:
>> Only mentioning you fixed it, won't do any help for the Radiant community.
>> Please inform us about the solution or bugs you have found.
>>
>> Thanks in advance.
>>
>>
>> On Jul 8, 2009, at 9:51 PM, john muhl wrote:
>>
>>> i went down through the code and think i may have found the issue
>>> which appears to be at the radiant level. thanks again for all the
>>> help.
>>>
>>> On Wed, Jul 8, 2009 at 1:10 PM, Cristi Duma wrote:
>>>>
>>>> I created a radiant project with the code from the gist you supplied, and
>>>> after putting the config.after_initialize block in development.rb worked
>>>> flawlessly. So is there the possibility that the problem is not in
>>>> mailer_extension?
>>>>
>>>>
>>>> On 7/8/09 9:58 PM, john muhl wrote:
>>>>>
>>>>> same error with the smtp settings in development.rb
>>>>>
>>>>> On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hoka
>>>>>  wrote:
>>>>>
>>>>>>
>>>>>> Could you try moving the contents of your config.after_initialize block
>>>>>> to
>>>>>> development.rb or production.rb?
>>>>>> --
>>>>>> Istvan Hoka
>>>>>>
>>>>>>
>>>>>> On Wed, Jul 8, 2009 at 8:47 PM, john muhl  wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> oh, and those results are the same with radiant/mailer or
>>>>>>> aissac/mailer
>>>>>>>
>>>>>>> On Wed, Jul 8, 2009 at 11:43 AM, john muhl  wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> this is running locally in the development environment. i've tested
>>>>>>>> with webrick, mongrel, thin and passenger and they all have the same
>>>>>>>> error message until you get to server specific part. the test site is
>>>>>>>> the styled blog with only the mailer extension added. all the page
>>>>>>>> parts and environment.rb are here: http://gist.github.com/142995 - i
>>>>>>>> also have mailer.post_to_page? = true set.
>>>>>>>>
>>>>>>>> just to make sure it wasn't inherent in the system i setup a styled
>>>>>>>> blog with 0.7.1 installed mailer, used the same parts and smtp
>>>>>>>> settings and was able to send mail on all 4 servers.
>>>>>>>>
>>>>>>>> thanks for help.
>>>>>>>>
>>>>>>>> On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hoka
>>>>>>>>
>>>>>>>
>>>>>>> wrote:
>>>>>>>
>>>>>>>>>
>>>>>>>>> John, it looks like you are getting this on your production machine
>>>>>>>>>
>>>>>>>
>>>>>>> where
>>>>>>>
>>>>>>>>>
>>>>>>>>> you are using Thin. Could you test with Passenger or Mongrel,
>>>>>>>>> perhaps
>>>>>>>>> locally and see if you get the same error?
>>>>>>>>> Also, could you provide some more context? For instance, are you
>>>>>>>>> trying
>>>>>>>>>
>>>>>>>
>>>>>>> to
>>>>>>>
>>>>>>>>>
>>>>>>>>> attach a file or is it a simple form you are mailing?
>

Re: [Radiant] mailer extension and 0.8

[john muhl]

turns out the culprit is "mailer.post_to_page? = true"

On Wed, Jul 8, 2009 at 3:31 PM, john muhl wrote:
> the issue seems to have resolved itself with radiant edge.
>
> On Wed, Jul 8, 2009 at 2:20 PM, john muhl wrote:
>> yes, of course. i'm just not convinced it's the proper fix, it just
>> happened to be the most expedient one. here is the diff for the
>> curious:
>>
>> diff --git a/lib/radiant/cache.rb b/lib/radiant/cache.rb
>> index a82..2e16de9 100644
>> --- a/lib/radiant/cache.rb
>> +++ b/lib/radiant/cache.rb
>> @@ -48,7 +48,7 @@ module Radiant
>>       end
>>
>>       private
>> -      def restore_response(hash, body)
>> +      def restore_response(hash, body=nil)
>>         # Cribbed from the Rack::Cache source
>>         status = hash.delete('X-Status').to_i
>>         response = Rack::Cache::Response.new(status, hash, body)
>>
>>
>> On Wed, Jul 8, 2009 at 1:56 PM, Victor Elsendoorn 
>> wrote:
>>> Only mentioning you fixed it, won't do any help for the Radiant community.
>>> Please inform us about the solution or bugs you have found.
>>>
>>> Thanks in advance.
>>>
>>>
>>> On Jul 8, 2009, at 9:51 PM, john muhl wrote:
>>>
>>>> i went down through the code and think i may have found the issue
>>>> which appears to be at the radiant level. thanks again for all the
>>>> help.
>>>>
>>>> On Wed, Jul 8, 2009 at 1:10 PM, Cristi Duma wrote:
>>>>>
>>>>> I created a radiant project with the code from the gist you supplied, and
>>>>> after putting the config.after_initialize block in development.rb worked
>>>>> flawlessly. So is there the possibility that the problem is not in
>>>>> mailer_extension?
>>>>>
>>>>>
>>>>> On 7/8/09 9:58 PM, john muhl wrote:
>>>>>>
>>>>>> same error with the smtp settings in development.rb
>>>>>>
>>>>>> On Wed, Jul 8, 2009 at 12:01 PM, Istvan Hoka
>>>>>>  wrote:
>>>>>>
>>>>>>>
>>>>>>> Could you try moving the contents of your config.after_initialize block
>>>>>>> to
>>>>>>> development.rb or production.rb?
>>>>>>> --
>>>>>>> Istvan Hoka
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Jul 8, 2009 at 8:47 PM, john muhl  wrote:
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> oh, and those results are the same with radiant/mailer or
>>>>>>>> aissac/mailer
>>>>>>>>
>>>>>>>> On Wed, Jul 8, 2009 at 11:43 AM, john muhl  wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> this is running locally in the development environment. i've tested
>>>>>>>>> with webrick, mongrel, thin and passenger and they all have the same
>>>>>>>>> error message until you get to server specific part. the test site is
>>>>>>>>> the styled blog with only the mailer extension added. all the page
>>>>>>>>> parts and environment.rb are here: http://gist.github.com/142995 - i
>>>>>>>>> also have mailer.post_to_page? = true set.
>>>>>>>>>
>>>>>>>>> just to make sure it wasn't inherent in the system i setup a styled
>>>>>>>>> blog with 0.7.1 installed mailer, used the same parts and smtp
>>>>>>>>> settings and was able to send mail on all 4 servers.
>>>>>>>>>
>>>>>>>>> thanks for help.
>>>>>>>>>
>>>>>>>>> On Wed, Jul 8, 2009 at 10:49 AM, Istvan Hoka
>>>>>>>>>
>>>>>>>>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> John, it looks like you are getting this on your production machine
>>>>>>>>>>
>>>>>>>>
>>>>>>>> where
>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> you are using Thin. Could you test with Passenger or Mongrel,
>>>>>>>>>>

Re: [Radiant] mailer extension and 0.8

[john muhl]

do you mean works with 0.8.0 as in being able to use
"mailer.post_to_page? = true" without having to hack on it? as far as
i can tell it still causes 500s in your "new" version.

On Tue, Jul 14, 2009 at 12:23 AM, Cristi Duma wrote:
> glad you figured it out. this means I can anounce the "new" version of
> mailer
>
> this version <http://github.com/Aissac/radiant-mailer-extension/tree/master>
> of Mailer Extension works on Radiant 0.8 and I added the mail attachments
> from Jomz's branch. Also there are some cucumber features and the specs have
> been fixed. Hasn't been tested on a production site yet, but locally it
> works pretty good.
>
> Pull requests have been sent.
>
> Cheers, Cristi
>
> On 7/14/09 12:24 AM, john muhl wrote:
>>
>> turns out the culprit is "mailer.post_to_page? = true"
>>
>
> ___
> 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] New setup - How to get it right?

[john muhl]

as jim points out it's probably your rubygems version, if you
installed rubygems via apt-get then you have 1.2... which will not
work and due to the way debian packages rubygems you cannot easily
update the system version. so your best bet is to reinstall the latest
rubygems from source and then reinstall all your gems using that
version.

On Wed, Jul 22, 2009 at 2:04 PM, Jim Gay wrote:
> What version of rubygems do you have?
>
> gem --version
>
> Try updating rubygems and you should be good. Rails requires version 1.3.1
> or greater I believe.
>
> gem update system
>
> Jim Gay
> http://www.saturnflyer.com
>
>
>
> On Jul 22, 2009, at 3:23 PM, exitseven wrote:
>
>>> On Wed, Jul 22, 2009 at 12:16 PM, Mamed Mamedov 
>>> wrote:

 Installation process of radiant is very simple. Feel free to try and ask
 if
 any questions ;)
>>
>> Sad to say... The installation seems not to be that very simple.
>> That's why I asked before but I am in trouble again as every time I
>> have to intall this thing...
>> Would you please help?
>>
>> This is what I did:
>> # gem install radiant (including dependencies)
>> # export PATH=${PATH}:/var/lib/gems/1.8/bin (because radiant was not
>> found by default install)
>>
>> This is what I get:
>> # radiant --database mysql
>>
>> /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/../../activesupport/lib/active_support/dependencies.rb:55:
>> uninitialized constant ActiveSupport::Dependencies::Mutex (NameError)
>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
>> `gem_original_require'
>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
>>       from
>> /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/../../activesupport/lib/active_support.rb:56
>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
>> `gem_original_require'
>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
>>       from
>> /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/rails_generator.rb:28
>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
>> `gem_original_require'
>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
>>       from /var/lib/gems/1.8/gems/radiant-0.8.0/bin/radiant:18
>>       from /var/lib/gems/1.8/bin/radiant:18:in `load'
>>       from /var/lib/gems/1.8/bin/radiant:18
>>
>> Any ideas?
>>
>> Thanks,
>> rainer
>> ___
>> Radiant mailing list
>> Post:   Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
> ___
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] New setup - How to get it right?

[john muhl]

actually better yet is to probably just use ruby enterprise edition
and forego debian's ruby packages completely.
http://www.rubyenterpriseedition.com/download.html - i've always felt
it was a much easier way to install ruby on any type of system.

On Wed, Jul 22, 2009 at 2:15 PM, john muhl wrote:
> as jim points out it's probably your rubygems version, if you
> installed rubygems via apt-get then you have 1.2... which will not
> work and due to the way debian packages rubygems you cannot easily
> update the system version. so your best bet is to reinstall the latest
> rubygems from source and then reinstall all your gems using that
> version.
>
> On Wed, Jul 22, 2009 at 2:04 PM, Jim Gay wrote:
>> What version of rubygems do you have?
>>
>> gem --version
>>
>> Try updating rubygems and you should be good. Rails requires version 1.3.1
>> or greater I believe.
>>
>> gem update system
>>
>> Jim Gay
>> http://www.saturnflyer.com
>>
>>
>>
>> On Jul 22, 2009, at 3:23 PM, exitseven wrote:
>>
>>>> On Wed, Jul 22, 2009 at 12:16 PM, Mamed Mamedov 
>>>> wrote:
>>>>>
>>>>> Installation process of radiant is very simple. Feel free to try and ask
>>>>> if
>>>>> any questions ;)
>>>
>>> Sad to say... The installation seems not to be that very simple.
>>> That's why I asked before but I am in trouble again as every time I
>>> have to intall this thing...
>>> Would you please help?
>>>
>>> This is what I did:
>>> # gem install radiant (including dependencies)
>>> # export PATH=${PATH}:/var/lib/gems/1.8/bin (because radiant was not
>>> found by default install)
>>>
>>> This is what I get:
>>> # radiant --database mysql
>>>
>>> /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/../../activesupport/lib/active_support/dependencies.rb:55:
>>> uninitialized constant ActiveSupport::Dependencies::Mutex (NameError)
>>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
>>> `gem_original_require'
>>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
>>>       from
>>> /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/../../activesupport/lib/active_support.rb:56
>>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
>>> `gem_original_require'
>>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
>>>       from
>>> /var/lib/gems/1.8/gems/radiant-0.8.0/vendor/rails/railties/lib/rails_generator.rb:28
>>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in
>>> `gem_original_require'
>>>       from /usr/lib/ruby/1.8/rubygems/custom_require.rb:27:in `require'
>>>       from /var/lib/gems/1.8/gems/radiant-0.8.0/bin/radiant:18
>>>       from /var/lib/gems/1.8/bin/radiant:18:in `load'
>>>       from /var/lib/gems/1.8/bin/radiant:18
>>>
>>> Any ideas?
>>>
>>> Thanks,
>>> rainer
>>> ___
>>> Radiant mailing list
>>> Post:   Radiant@radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>> ___
>> Radiant mailing list
>> Post:   Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] multi_site

[john muhl]

try `git clone git://github.com/radiant/radiant-multi-site-extension.git`

all the extensions from the old svn repo have been moved to
http://github.com/radiant and almost all 3rd party extension
development has moved to git as well. although if you're trying to use
0.6.7 you may find the versions available on github incompatible it
has after all been over a year since that release.

On Sun, Jul 26, 2009 at 3:13 PM, Caleb Adam
Haye wrote:
> I am using the multi-site extension, and am having trouble packaging my app
> up for deployment.
>
> The following command doesn’t work, because the SVN repo is "Gone" (410):
> svn export
> http://svn.radiantcms.org/radiant/tags/rel_0-6-7/extensions/multi_site/vendor/extensions/multi_site
>
> Any idea where it went? or how i can achieve my goal of being able to deploy
> my site w/ the multi_site extension encapsulated?
> ___
> 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] Ray extension problem

[john muhl]

can you post the contents of vendor/extensions/ray/preferences.yml

On Tue, Jul 28, 2009 at 5:25 AM, Jonathan Batchelor wrote:
> I've been playing about with Radiant for a few days now and am really
> liking it's simplicity and flexibility.
>
> After installing on my MacBook and beginning some developmet I want to
> install on my Dreamhost account. I have been migrated to a newer server by
> Dreamhost and have Radiant 0.8.0 working now.
>
> I started to install install extensions and took the advice on the wiki
> page to use ray as it will automatically reload Passenger for me. However
> although the script/extensions install command works fine, as did setting
> the config for ray using rake ray:setup:restart server=passenger, when I
> come to install an extension it does not work. I have included the --trace
> output below - can anyone help?
>
> Thanks,
> Jonathan.
>
> $ rake production ray:extension:install name=dashboard --trace
> (in /home//_radiant)
> ** Invoke production (first_time)
> ** Execute production
> ** Invoke environment (first_time)
> ** Execute environment
> ** Invoke ray:extension:install (first_time)
> ** Execute ray:extension:install
> rake aborted!
> undefined method `strip' for nil:NilClass
> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:807:in
> `get_download_preference'
> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:151:in
> `install_extension'
> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:20
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `call'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `execute'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `each'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain'
> /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
> /home//.gems/gems/rake-0.8.7/bin/rake:31
> /home//.gems/bin/rake:19:in `load'
> /home//.gems/bin/rake:19
> ___
> 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] Ray extension problem

[john muhl]

actually, this looks like an error someone else had with dreamhost,
you probably just need to delete the preferences file, then run

rake ray:setup:download
rake ray:setup:restart server=passenger

then try installing extensions. i have no idea why this only happens
with dreamhost.

On Tue, Jul 28, 2009 at 9:27 AM, john muhl wrote:
> can you post the contents of vendor/extensions/ray/preferences.yml
>
> On Tue, Jul 28, 2009 at 5:25 AM, Jonathan Batchelor wrote:
>> I've been playing about with Radiant for a few days now and am really
>> liking it's simplicity and flexibility.
>>
>> After installing on my MacBook and beginning some developmet I want to
>> install on my Dreamhost account. I have been migrated to a newer server by
>> Dreamhost and have Radiant 0.8.0 working now.
>>
>> I started to install install extensions and took the advice on the wiki
>> page to use ray as it will automatically reload Passenger for me. However
>> although the script/extensions install command works fine, as did setting
>> the config for ray using rake ray:setup:restart server=passenger, when I
>> come to install an extension it does not work. I have included the --trace
>> output below - can anyone help?
>>
>> Thanks,
>> Jonathan.
>>
>> $ rake production ray:extension:install name=dashboard --trace
>> (in /home//_radiant)
>> ** Invoke production (first_time)
>> ** Execute production
>> ** Invoke environment (first_time)
>> ** Execute environment
>> ** Invoke ray:extension:install (first_time)
>> ** Execute ray:extension:install
>> rake aborted!
>> undefined method `strip' for nil:NilClass
>> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:807:in
>> `get_download_preference'
>> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:151:in
>> `install_extension'
>> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:20
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `call'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `execute'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `each'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain'
>> /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in
>> `standard_exception_handling'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in
>> `standard_exception_handling'
>> /home//.gems/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
>> /home//.gems/gems/rake-0.8.7/bin/rake:31
>> /home//.gems/bin/rake:19:in `load'
>> /home//.gems/bin/rake:19
>> ___
>> 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] Ray extension problem

[john muhl]

i've just fixed this, update ray and you shouldn't run into that anymore.

On Tue, Jul 28, 2009 at 5:25 AM, Jonathan Batchelor wrote:
> I've been playing about with Radiant for a few days now and am really
> liking it's simplicity and flexibility.
>
> After installing on my MacBook and beginning some developmet I want to
> install on my Dreamhost account. I have been migrated to a newer server by
> Dreamhost and have Radiant 0.8.0 working now.
>
> I started to install install extensions and took the advice on the wiki
> page to use ray as it will automatically reload Passenger for me. However
> although the script/extensions install command works fine, as did setting
> the config for ray using rake ray:setup:restart server=passenger, when I
> come to install an extension it does not work. I have included the --trace
> output below - can anyone help?
>
> Thanks,
> Jonathan.
>
> $ rake production ray:extension:install name=dashboard --trace
> (in /home//_radiant)
> ** Invoke production (first_time)
> ** Execute production
> ** Invoke environment (first_time)
> ** Execute environment
> ** Invoke ray:extension:install (first_time)
> ** Execute ray:extension:install
> rake aborted!
> undefined method `strip' for nil:NilClass
> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:807:in
> `get_download_preference'
> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:151:in
> `install_extension'
> /home//_radiant/vendor/extensions/ray/lib/tasks/ray_extension_tasks.rake:20
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `call'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:636:in `execute'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `each'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:631:in `execute'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:597:in `invoke_with_call_chain'
> /usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:590:in `invoke_with_call_chain'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:583:in `invoke'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2051:in `invoke_task'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /home//.gems/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
> /home//.gems/gems/rake-0.8.7/bin/rake:31
> /home//.gems/bin/rake:19:in `load'
> /home//.gems/bin/rake:19
> ___
> 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] Radiant In Herolu

[john muhl]

i've done this a few times and it was straightforward. could you be
more specific about where you're running into issues?

On Wed, Jul 29, 2009 at 7:15 AM, Mauricio Dulce wrote:
> Hello, I need help to config paperclipped extension to use in heroku and s3.
> ___
> 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] Radiant In Herolu

[john muhl]

On Wed, Jul 29, 2009 at 9:09 AM, Charlie
Robbins wrote:
> I had also had this thought. It seems that with an s3 (or cloudfiles)
> enabled paperclipped extension along with SnS, it could be possible to run
> Radiant seamlessly in the cloud. Anyone want to get down on this project?
> You fork? I fork? We all can fork fork.

http://empty-river-61.heroku.com/ you can login with admin/radiant to
see the paperclipped settings. obviously i am not giving away s3
credentials so you can't actually upload images but you can at least
see how it works. i still haven't heard a real issue with running
radiant in the cloud. i have a few production sites running completely
on heroku and s3 and haven't had any trouble.

> Charlie
>
> On Wed, Jul 29, 2009 at 9:15 AM, Mauricio Dulce 
> wrote:
>
>> Hello, I need help to config paperclipped extension to use in heroku and
>> s3.
>> ___
>> Radiant mailing list
>> Post:   Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>
> ___
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Radiant In Herolu

[john muhl]

On Wed, Jul 29, 2009 at 10:51 AM, Mauricio
Dulce wrote:
> Thanks, but the problem is that I'm using the previous version of radiant,
> one can say where I get the two paperclipped extensions and settings for
> this or that version 0.7.1 or extensions such as comments and poll event
> calendar work in 0.8

most extensions will have a branch or tag for the different
incompatible versions...of course neither paperclipped or settings
have a branch or tag for 0.7 compatibility so you'll have to go
through the history looking for where they added the changes to go
from 0.7 to 0.8 and checkout the appropriate commit. however comments
has a 0.7.1 tag to use it you would use something like:

git clone git://github.com/artofmission/radiant-comments.git
vendor/extensions/comments
cd vendor/extensions/comments
git checkout -b 071 radiant0.7.1

> thanks
> El Jul 29, 2009, a las 11:17 AM, john muhl escribió:
>
>> On Wed, Jul 29, 2009 at 9:09 AM, Charlie
>> Robbins wrote:
>>>
>>> I had also had this thought. It seems that with an s3 (or cloudfiles)
>>> enabled paperclipped extension along with SnS, it could be possible to
>>> run
>>> Radiant seamlessly in the cloud. Anyone want to get down on this project?
>>> You fork? I fork? We all can fork fork.
>>
>> http://empty-river-61.heroku.com/ you can login with admin/radiant to
>> see the paperclipped settings. obviously i am not giving away s3
>> credentials so you can't actually upload images but you can at least
>> see how it works. i still haven't heard a real issue with running
>> radiant in the cloud. i have a few production sites running completely
>> on heroku and s3 and haven't had any trouble.
>>
>>> Charlie
>>>
>>> On Wed, Jul 29, 2009 at 9:15 AM, Mauricio Dulce
>>> wrote:
>>>
>>>> Hello, I need help to config paperclipped extension to use in heroku and
>>>> s3.
>>>> ___
>>>> Radiant mailing list
>>>> Post:   Radiant@radiantcms.org
>>>> Search: http://radiantcms.org/mailing-list/search/
>>>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>>>
>>> ___
>>> Radiant mailing list
>>> Post:   Radiant@radiantcms.org
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>> ___
>> Radiant mailing list
>> Post:   Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
> ___
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Radiant In Herolu

[john muhl]

On Wed, Jul 29, 2009 at 2:11 PM, Keith Bingman wrote:
> Paperclip actually has a 0.7.1 branch and I think the current version works
> with 0.7.1 as well.  Settings does not, but I have so many "lying" around..
> there are some very minor changes to make it work though.

turns out i was looking at paperclipped-multi-site (for whatever
reason github put it at the top of the search for
radiant+paperclipped). sorry for the confusion.

> Keith
>
>
> On Jul 29, 2009, at 10:21 AM, john muhl wrote:
>
>> On Wed, Jul 29, 2009 at 10:51 AM, Mauricio
>> Dulce wrote:
>>>
>>> Thanks, but the problem is that I'm using the previous version of
>>> radiant,
>>> one can say where I get the two paperclipped extensions and settings for
>>> this or that version 0.7.1 or extensions such as comments and poll event
>>> calendar work in 0.8
>>
>> most extensions will have a branch or tag for the different
>> incompatible versions...of course neither paperclipped or settings
>> have a branch or tag for 0.7 compatibility so you'll have to go
>> through the history looking for where they added the changes to go
>> from 0.7 to 0.8 and checkout the appropriate commit. however comments
>> has a 0.7.1 tag to use it you would use something like:
>>
>> git clone git://github.com/artofmission/radiant-comments.git
>> vendor/extensions/comments
>> cd vendor/extensions/comments
>> git checkout -b 071 radiant0.7.1
>>
>
> ___
> 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] Problem installing mailer extension

[john muhl]

`script/extension install` runs both the migrate and update tasks
regardless just to be safe. extensions that plan for this include
empty migrate/update task to keep these messages from confusing users.

On Thu, Aug 6, 2009 at 1:11 PM, exitseven wrote:
> Hm,
>
> thanks for the answer. But I run the provided installer script
> (./script/extension install mailer). This script is running the
> update. Why is it doing this, if it is not needed? I did not touched
> the script.
>
> I know that the mailer extension needs to get configured in the mailer
> page part. But what do you mean with:
> "You just need to clone the extension and config the mailer in the
> "mailer" page part."
>
> To clone? You mean copy? What do I have to copy?
>
> Your help will be very appreciated! Thanks!
> rainer
>
> On Thu, Aug 6, 2009 at 12:23 PM, Cristi Duma wrote:
>> The thing is that you don't need to run "update" on mailer extension.
>> There's nothing to update. As there is nothing to migrate. You just need to
>> clone the extension and config the mailer in the "mailer" page part.
>>
>> And you get that error, because the "update" task is not present in the
>> extension.
>>
>> Cristi
>>
>> On 06.08.2009 12:29, Mamed Mamedov wrote:
>>>
>>> Does anyone knows if it compatible with last version of radiant (0.8)?
>>> I'am
>>> using it on 0.7.1 without any problem.
>>> 
>>> Regards,
>>> Mamed Mamedov
>>>
>>>
>>> Samuel
>>> Goldwyn
>>> - "I'm willing to admit that I may not always be right, but I am never
>>> wrong."
>>>
>>> On Thu, Aug 6, 2009 at 2:20 PM, exitseven  wrote:
>>>
>>>

 Hey Mamed,

 sure, thanks for the quick reply!

 ~$ ruby -v
 ruby 1.8.6 (2008-08-11 patchlevel 287) [i686-linux]
 Ruby Enterprise Edition 20090610

 ~$ rails -v
 Rails 2.3.3

 ~$ radiant -v
 Radiant 0.8.0

 Does it help?

 Best wishes,
 rainer

 On Thu, Aug 6, 2009 at 11:02 AM, Mamed Mamedov
 wrote:

>
> I think there is problem with your radiant/rails/ruby versions
> cross-compatibility.. ha?
> Please give us your actual versions of radiant, rails and ruby. Thank
>

 you!

>
> 
> Regards,
> Mamed Mamedov
>
>
> Mike Ditka
>

  -

>
> "If God had wanted man to play soccer, he wouldn't have given us arms."
>
> On Thu, Aug 6, 2009 at 1:45 PM, exitseven  wrote:
>
>
>>
>> Hello again,
>>
>> I just tried to install the mailer extension as described
>>
>> here: http://wiki.github.com/radiant/radiant/mailer-extension
>> and here (manually):
>> http://wiki.github.com/radiant/radiant/installing-extensions#manual
>>
>> Unfortunately the installation process (rake) exits with:
>>
>> $ rake radiant:extensions:mailer:update --trace
>> (in /home/claude/DEV/freiraumart)
>> rake aborted!
>> Don't know how to build task 'radiant:extensions:mailer:update'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1728:in

>>
>> `[]'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2050:in

>>
>> `invoke_task'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in

>>
>> `top_level'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in

>>
>> `each'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in

>>
>> `top_level'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in

>>
>> `standard_exception_handling'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in

>>
>> `top_level'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in

>>
>> `run'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in

>>
>> `standard_exception_handling'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in

>>
>> `run'
>>
>>
>>


 /opt/ruby-enterprise-1.8.6-20090610/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31

>>
>> /opt/ruby-enterprise-1.8.6-20090610/bin/rake:19:in `load'
>> /opt/ruby-enterprise-1.8.6-20090610/bin/rake:19
>>
>> What a

Re: [Radiant] Problem unsolved: Multiple languages for content

[john muhl]

could you just ask your snippet to give the right urls?








still some duplication but much less and duplicating layouts

On Thu, Aug 6, 2009 at 2:06 PM, exitseven wrote:
> Hey again,
>
> sorry, I'm still looking around for a solution. I stumbled over an old
> post of someone having the same problem
> (http://www.ruby-forum.com/topic/133019). He writes exactly about what
> I need. But besides I am unable to install the Language Redirect
> extension, it is not exactly what I need.
>
> I have to page trees:
>
> 1) /de/page
> 2) /en/page
>
> The /de-tree is working fine. The user should now be able to hit a
> link "English version" on the site and should then get to the
> /en-tree-contents.
>
> So far not a problem. The user gets to for example /en/home. But from
> now on he should only get contents from the /en-tree:
>
> /en/home/
> /en/about_us
> /en/contact
> /en/...
>
> I use a snippet to render the menu:
> 
>
> Do I have to double every layout I have into an /en- and an
> /de-version? I thought there is propably some extension that
> automatically routes every /de-request to the /en-tree if the user
> requested the english version of the site one time by clicking the
> "English version" link.
>
> Hopefully you understand the problem and there is an answer somewhere 
> outside...
>
> Best wishes,
> rainer
> ___
> 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] Problem installing mailer extension

[john muhl]

you must be looking at old documentation - there is no longer any
mailer page type.

http://wiki.github.com/radiant/radiant/mailer-extension

On Sun, Aug 9, 2009 at 9:05 AM, exitseven wrote:
> Well okay,
>
> I just disabled other extensions and git cloned the mailer extension.
> Mailer extension shows up under extensions in radiant. But I am unable
> to set the page type to "mailer", because it is not listed in the
> dropdown.
>
> What can I do? Why is "mailer" not listed in the dropdown?
>
> Best wishes,
> rainer
>
> On Thu, Aug 6, 2009 at 10:11 PM, john muhl wrote:
>> `script/extension install` runs both the migrate and update tasks
>> regardless just to be safe. extensions that plan for this include
>> empty migrate/update task to keep these messages from confusing users.
>>
>> On Thu, Aug 6, 2009 at 1:11 PM, exitseven wrote:
>>> Hm,
>>>
>>> thanks for the answer. But I run the provided installer script
>>> (./script/extension install mailer). This script is running the
>>> update. Why is it doing this, if it is not needed? I did not touched
>>> the script.
>>>
>>> I know that the mailer extension needs to get configured in the mailer
>>> page part. But what do you mean with:
>>> "You just need to clone the extension and config the mailer in the
>>> "mailer" page part."
>>>
>>> To clone? You mean copy? What do I have to copy?
>>>
>>> Your help will be very appreciated! Thanks!
>>> rainer
>>>
>>> On Thu, Aug 6, 2009 at 12:23 PM, Cristi Duma wrote:
>>>> The thing is that you don't need to run "update" on mailer extension.
>>>> There's nothing to update. As there is nothing to migrate. You just need to
>>>> clone the extension and config the mailer in the "mailer" page part.
>>>>
>>>> And you get that error, because the "update" task is not present in the
>>>> extension.
>>>>
>>>> Cristi
>>>>
>>>> On 06.08.2009 12:29, Mamed Mamedov wrote:
>>>>>
>>>>> Does anyone knows if it compatible with last version of radiant (0.8)?
>>>>> I'am
>>>>> using it on 0.7.1 without any problem.
>>>>> 
>>>>> Regards,
>>>>> Mamed Mamedov
>>>>>
>>>>>
>>>>> Samuel
>>>>> Goldwyn<http://www.brainyquote.com/quotes/authors/s/samuel_goldwyn.html>
>>>>> - "I'm willing to admit that I may not always be right, but I am never
>>>>> wrong."
>>>>>
>>>>> On Thu, Aug 6, 2009 at 2:20 PM, exitseven  wrote:
>>>>>
>>>>>
>>>>>>
>>>>>> Hey Mamed,
>>>>>>
>>>>>> sure, thanks for the quick reply!
>>>>>>
>>>>>> ~$ ruby -v
>>>>>> ruby 1.8.6 (2008-08-11 patchlevel 287) [i686-linux]
>>>>>> Ruby Enterprise Edition 20090610
>>>>>>
>>>>>> ~$ rails -v
>>>>>> Rails 2.3.3
>>>>>>
>>>>>> ~$ radiant -v
>>>>>> Radiant 0.8.0
>>>>>>
>>>>>> Does it help?
>>>>>>
>>>>>> Best wishes,
>>>>>> rainer
>>>>>>
>>>>>> On Thu, Aug 6, 2009 at 11:02 AM, Mamed Mamedov
>>>>>> wrote:
>>>>>>
>>>>>>>
>>>>>>> I think there is problem with your radiant/rails/ruby versions
>>>>>>> cross-compatibility.. ha?
>>>>>>> Please give us your actual versions of radiant, rails and ruby. Thank
>>>>>>>
>>>>>>
>>>>>> you!
>>>>>>
>>>>>>>
>>>>>>> 
>>>>>>> Regards,
>>>>>>> Mamed Mamedov
>>>>>>>
>>>>>>>
>>>>>>> Mike Ditka<http://www.brainyquote.com/quotes/authors/m/mike_ditka.html>
>>>>>>>
>>>>>>
>>>>>>  -
>>>>>>
>>>>>>>
>>>>>>> "If God had wanted man to play soccer, he wouldn't have given us arms."
>>>>>>>
>>>>>>> On Thu, Aug 6, 2009 at 1:45 PM,

Re: [Radiant] Comments Extension and Notifications

[john muhl]

you can set `Radiant::Config['comments.auto_approve'] = true` through
the console, your environment or the settings extension and it will
auto-approve comments.

On Thu, Aug 13, 2009 at 12:02 PM,  wrote:
> Hi,
>
> Firstly thanks to all those who developed this extension, it seems like
> quite a roll call.
>
> Is this feature supported? I can see in TODO a note about stating that
> something similar is pending, but a quick glance through the code suggests
> it is in place.
>
> If it isn't implemented is it possible to auto approve comments that pass
> the simple spam test?
>
> Thanks ,
>
> ___
> 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] Re: Condition in Page Attachments extension

[john muhl]

i think the ...
might be what you're looking for.

On Wed, Aug 19, 2009 at 3:54 PM, Rafael
Carvalho wrote:
> I resolved it just adding if page.attachment(name) != nil in tag
> "attachment:image" do |tag|
>
>
> --
> Rafael Carvalho
> ___
> 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] Re: Condition in Page Attachments extension

[john muhl]

don't forget the available tags link in the page edit interface. open
that and type "attachment" into the search most if not all of
page_attachments tags should be documented in there.

On Wed, Aug 19, 2009 at 6:36 PM, Rafael
Carvalho wrote:
> hmm... i'm starting to use the page attachments now... i didn't know about
> this tag! i'm shine... ehhe
>
> thanks!
>
>
> --
> Rafael Carvalho
> ___
> 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] radiant keyword list is too small

[john muhl]

i've never heard of anyone using, recommending or suggesting 1000
characters of keywords. where did you read that? most sources i've
seen suggest about 5 keywords or about 250 characters. beside that
aren't keywords mostly useless for search engines since their mostly
used by spammers?

On Tue, Sep 1, 2009 at 2:37 AM, dave- wrote:
> When describing a document for the search engines using the  tag you
> are supposed to limit the keywords list to 1,000 characters or less. Radiant
> only allows to a list of about 200 characters.  dave-
> ___
> 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] radiant keyword list is too small

[john muhl]

On Tue, Sep 1, 2009 at 12:41 PM, dave4c03 wrote:
> The quote is in a new book I bought about HTML 4.01 strict.
> "HTML in easy steps" sixth edition (2009) by Mike McGrath page 28 says:
>
>> Promotion of the page by keywords is best achieved by following some
>> simple guidelines:
>
> Use only lowercase characters
>
> Keep all keywords on a simple line
>
> Never repeat a keyword in the list
>
> Limit the keywords list to 1,000 characters or less
>
> Try to use the plural form for keywords - to match searches made with both
> the single and plural forms of that word

"Hypertext-Matching Analysis: Our search engine also analyzes page
content. However, instead of simply scanning for page-based text
(which can be manipulated by site publishers through meta-tags), our
technology analyzes the full content of a page and factors in fonts,
subdivisions and the precise location of each word. We also analyze
the content of neighboring web pages to ensure the results returned
are the most relevant to a user's query." [1]

"Don't load pages with irrelevant keywords." [2]

""Keyword stuffing" refers to the practice of loading a webpage with
keywords in an attempt to manipulate a site's ranking in Google's
search results. Filling pages with keywords results in a negative user
experience, and can harm your site's ranking. Focus on creating
useful, information-rich content that uses keywords appropriately and
in context." [3]

"Use a "keyword" meta-tag to list key words for the document. Use a
distinct list of keywords that relate to the specific page on your
site instead of using one broad set of keywords for every page." [4]

none of those sources suggest to me that 1000 characters of keywords
is going to be any more useful in page ranking than 200 characters.

[1] http://www.google.com/corporate/tech.html
[2] http://www.google.com/support/webmasters/bin/answer.py?answer=35769
[3] http://www.google.com/support/webmasters/bin/answer.py?answer=66358
[4] http://help.yahoo.com/l/us/yahoo/search/ranking/ranking-02.html
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Backup

[john muhl]

it depends on how what sort of database you're using. if it's sqlite
you can simply zip up the entire radiant project and call that a
backup. if it's mysql or something else you can use that db's
dump/import tools plus a zip file of the radiant project to create a
backup. version control also works well for rolling back the project
directory (and database if you're using sqlite).

2009/9/7 María Paula Mariani :
> Hello!
>
> I'd like to know which is the best way to freeze or to make a backup
> of my project made in Radiant. I'd like to try some extensions and I'd
> like to have a backup just in case something goes wrong.
>
> How is the best way to restore the project and database (from a backup)?
>
> Thanks very much!
>
> --
> Paula
> ___
> 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] Backup

[john muhl]

2009/9/9 María Paula Mariani :
> Considering this, I've made a .tar.gz of my whole radiant directory,
> including /config. I would like to make that db:dump (which is the
> correct command?) to create the db backup but I don't know which
> command is it and which is the name of the database radiant is
> creating per default when we create a project.

you can find your database connection information inside the
config/database.yml file. you're probably most interested in the
production database settings; unless of course you have other
environments you'd like to backup.

for mysql you'll need to run a terminal command such as:
mysqldump -u mysql_user your_radiant_db_name > dump.mysql.db

or:
mysqldump -u mysql_user -p your_radiant_db_name > dump.mysql.db

if the mysql_user requires a password to connect to the db.
see http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html for the full
documentation.
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

[Radiant] extension dependencies in ray

[john muhl]

On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs  wrote:
> Looks like it's time for another release of Radiant:
> WHAT'S NEW IN THIS RELEASE?
> * Allow extensions to declare dependencies [Josh French]

does this mean that i can safely rip out all the code in ray that
tries to allow some extension dependencies? my feeling is that it
wasn't ever a hit feature in ray and that the implementation in
radiant is more usable/flexible.

is anyone using the dependency feature in ray who be sad to see it go?
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] extension dependencies in ray

[john muhl]

thanks for the details. guess that code stays for now.

On Wed, Sep 9, 2009 at 1:32 PM, Sean Cribbs  wrote:
> This is a *runtime* dependency, not an install-time one.
>
> Basically, an extension can do this:
>
> extension_config do |config|
>  config.extension "paperclipped"
> end
>
> The initializer will check that "paperclipped" is available in the app and
> error out if not.
>
> Sean
>
> john muhl wrote:
>>
>> On Sat, Sep 5, 2009 at 10:12 AM, Sean Cribbs  wrote:
>>
>>>
>>> Looks like it's time for another release of Radiant:
>>> WHAT'S NEW IN THIS RELEASE?
>>> * Allow extensions to declare dependencies [Josh French]
>>>
>>
>> does this mean that i can safely rip out all the code in ray that
>> tries to allow some extension dependencies? my feeling is that it
>> wasn't ever a hit feature in ray and that the implementation in
>> radiant is more usable/flexible.
>>
>> is anyone using the dependency feature in ray who be sad to see it go?
>> ___
>> Radiant mailing list
>> Post:   Radiant@radiantcms.org
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>>
>
> ___
> Radiant mailing list
> Post:   Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] copy move extension install error

[john muhl]

it looks like the copy_move extension doesn't have an install task try:

rake production radiant:extensions:copy_move:migrate
rake production radiant:extensions:copy_move:update

or just use ./script/extension install copy_move and let it take care
of that for you.

On Thu, Sep 10, 2009 at 9:02 AM, Jan M.J. Storms  wrote:
> Hi,
>
> I just installed the copy/move extension for a site running radiant 0.8.1
>
> The installation gives the error below. As far as I can tell thoucgh,
> the extension works properly.
>
>
> rake production radiant:extensions:copy_move:install --trace
> (in /Library/WebServer/stekstad/info.psychopathie/cms/radiant)
> ** Invoke production (first_time)
> ** Execute production
> ** Invoke environment (first_time)
> ** Execute environment
> rake aborted!
> Don't know how to build task 'radiant:extensions:copy_move:install'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1728:in `[]'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2050:in `invoke_task'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `each'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2029:in `top_level'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2023:in `top_level'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2001:in `run'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:2068:in
> `standard_exception_handling'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/lib/rake.rb:1998:in `run'
> /usr/local/lib/ruby/gems/1.8/gems/rake-0.8.7/bin/rake:31
> /usr/local/bin/rake:16:in `load'
>
> -
> Jan
>
>
> ___
> 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] Blade Interface merged into edge

[john muhl]

On Tue, Sep 15, 2009 at 11:10 AM, John W. Long  wrote:
> For those of you who are developing extensions for Radiant, please update
> them to work with the new interface and give us your feedback on what your
> like and dislike. The most significant changes in the UI have been made to
> help extension developers keep things organized.

i sent a bunch of feedback to the list sometime ago about the blade ui
but it was never responded to. should i bother re-sending that? or was
the lack of response the response?
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Re: [Radiant] Blade Interface merged into edge

[john muhl]

On Tue, Sep 15, 2009 at 3:15 PM, John W. Long  wrote:
> On Sep 15, 2009, at 3:47 PM, john muhl wrote:
>>
>> i sent a bunch of feedback to the list sometime ago about the blade ui
>> but it was never responded to. should i bother re-sending that? or was
>> the lack of response the response?
>
> I must have missed that somehow. Please repost it.

http://groups.google.com/group/radiantcms-dev/browse_thread/thread/dc9b43114574cc40
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant