thank you, so they aren't meant to be there nowadays, I originally thought i had done something wrong, i can move on now, cheers
You _can_ use attr_accessor in ActiveRecord models. Like this: class Article < ActiveRecord::Base attr_accessor :my_prop end Maybe you could post some code and/or error message. /Lasse -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
So it's bombing out because of the routes.rb, I've taken a look at the routes and nothing jumps out at me as being wrong.
Can you compare ur rails / ruby / gems versions with mine here: http://pastie.org/885392 On 24 March 2010 15:51, Chris <r3ap3r2004@gmail.com> wrote: I get the following error when trying to db:migrate after installing
the spree-paypal-express plugin. Following these instructions to the
letter.
-Chris
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
rake aborted!
undefined local variable or method `map' for main:Object
/Users/MyUsername/test/spree-ppe/vendor/plugins/spree-paypal-express/config/routes.rb:3
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:145:in
`load_without_new_constant_marking'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:145:in
`load'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:521:in
`new_constants_in'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:145:in
`load'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/actionpack-2.3.5/lib/action_controller/routing/route_set.rb:286:in
`load_routes!'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/actionpack-2.3.5/lib/action_controller/routing/route_set.rb:286:in
`each'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/actionpack-2.3.5/lib/action_controller/routing/route_set.rb:286:in
`load_routes!'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/actionpack-2.3.5/lib/action_controller/routing/route_set.rb:266:in
`reload!'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rails-2.3.5/lib/initializer.rb:537:in
`initialize_routing'
/Users/MyUsername/test/spree-ppe/config/../lib/spree/initializer.rb:159:in
`initialize_routing'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rails-2.3.5/lib/initializer.rb:188:in
`process'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rails-2.3.5/lib/initializer.rb:113:in
`send'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rails-2.3.5/lib/initializer.rb:113:in
`run'
/Users/MyUsername/test/spree-ppe/config/../lib/spree/initializer.rb:90:in `run'
/Users/MyUsername/test/spree-ppe/config/environment.rb:13
/Users/MyUsername/.rvm/ree-1.8.7-head/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
/Users/MyUsername/.rvm/ree-1.8.7-head/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:156:in
`require'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:521:in
`new_constants_in'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:156:in
`require'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rails-2.3.5/lib/tasks/misc.rake:4
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:636:in
`call'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:636:in
`execute'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:631:in
`each'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:631:in
`execute'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:597:in
`invoke_with_call_chain'
/Users/MyUsername/.rvm/ree-1.8.7-head/lib/ruby/1.8/monitor.rb:242:in
`synchronize'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:590:in
`invoke_with_call_chain'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:607:in
`invoke_prerequisites'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:604:in
`each'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:604:in
`invoke_prerequisites'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:596:in
`invoke_with_call_chain'
/Users/MyUsername/.rvm/ree-1.8.7-head/lib/ruby/1.8/monitor.rb:242:in
`synchronize'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:590:in
`invoke_with_call_chain'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:583:in
`invoke'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:2051:in
`invoke_task'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:2029:in
`top_level'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:2029:in
`each'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:2029:in
`top_level'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:2023:in
`top_level'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:2001:in
`run'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:2068:in
`standard_exception_handling'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/lib/rake.rb:1998:in
`run'
/Users/MyUsername/.rvm/gems/ree-1.8.7-head/gems/rake-0.8.7/bin/rake:31
/Users/MyUsername/.rvm/ree-1.8.7-head/bin/rake:22:in `load'
/Users/MyUsername/.rvm/ree-1.8.7-head/bin/rake:22
On Tue, Mar 23, 2010 at 6:06 PM, Brian Quinn < brian@railsdog.com> wrote: > I must be doing some weird locally that everyone else is missing, so here's > the exact steps I just done to get PPE working. > git clone git:// github.com/railsdog/spree.git spree-ppe > cd spree-ppe > cp config/database.yml.example config/database.yml > rake db:bootstrap > ./script/plugin install git:// github.com/railsdog/spree-paypal-express.git > rake db:migrate > ./script/server > Once the server starts, login to the admin and create a new Payment Method > setting the following fields: > Name: PayPal > Environment: Development > Active: Yes > Provider: BillingIntegration::PaypalExpress > Review: unchecked > Server: test > No Shipping: unchecked > Test Mode: checked > For the actual login details, I've been using the PayPal Sandbox (API > Credentials page): > Login: API Username (be careful NOT to use the test account email address > here) > Password: API Password > Signature: Signature > > Now try to checkout? Feel free to ping me on the IRC channel if u see me on > (briandquinn). > Hope this helps. > BDQ
-- Brian Quinn ------------------------------------------- Rails Dog LLC 2 Wisconsin Circle, Suite 700 Chevy Chase, MD 20815 voice: (301)560-2000 ------------------------------------------- -- You received this message because you are subscribed to the Google Groups "Spree" group. To post to this group, send email to spree-user@googlegroups.com. To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
Or you could use mod_rails (Passenger) instead. /Lasse -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Check out http://www.anchor.com.au/hosting/dedicated/Running-Rails-2.3-Using-CGI-with-Rack under "The Meat". /Lasse 2010/3/24 Peter <Peterorpete@me.com> I'm doing a series of ruby on rails tutorials and it got to a part where i need to edit the following files that should be automatically inside the public folder: dispatch.cgi,dispatch.fcgi,dispatch.rb but I have none of these inside my public folder. Is there a reason for this? And how can i change it so they are back The only files in my public folder at present are 404.html 500.html 422.html images javascripts stylesheets favicon.ico index.html robots.txt -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
dont worry about this, i just stopped trying to have a version of ruby in my local folder and everything seems to work fine now On Mar 24, 5:40 pm, Peter <Peterorp...@me.com> wrote:
> can anybody tell me what is going wrong from the information taken
> from the development log below. WHen i start WEBrick and try and view
> a page on the localhost i get the following error, "We're sorry, but
> something went wrong.We've been notified about this issue and we'll
> take a look at it shortly."
> I'm a complete beginner and really want to start learning Ruby on
> rails, but cannot at the moment get past the setup phase despite a
> long time trying and i feel I'm almost there. Hope someone can help.
>
> # Logfile created on Wed Mar 24 17:13:17 +0000 2010/!\ FAILSAFE /!\
> Wed Mar 24 17:13:27 +0000 2010
> Status: 500 Internal Server Error
> uninitialized constant Encoding
> /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
> active_support/dependencies.rb:443:in `load_missing_constant'
> /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
> active_support/dependencies.rb:80:in `const_missing'
> /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
> active_support/dependencies.rb:92:in `const_missing'
> /usr/local/lib/ruby/gems/1.8/gems/sqlite3-0.0.8/lib/sqlite3/
> encoding.rb:9:in `find'
> /usr/local/lib/ruby/gems/1.8/gems/sqlite3-0.0.8/lib/sqlite3/
> database.rb:66:in `initialize'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/sqlite3_adapter.rb:13:in `new'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/sqlite3_adapter.rb:13:in
> `sqlite3_connection'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:223:in
> `send'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:223:in
> `new_connection'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:245:in
> `checkout_new_connection'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:188:in
> `checkout'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:184:in
> `loop'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:184:in
> `checkout'
> /usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:183:in
> `checkout'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:98:in
> `connection'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:326:in
> `retrieve_connection'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_specification.rb:
> 123:in `retrieve_connection'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_specification.rb:
> 115:in `connection'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/query_cache.rb:9:in `cache'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/query_cache.rb:28:in `call'
> /usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
> active_record/connection_adapters/abstract/connection_pool.rb:361:in
> `call'
> /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
> action_controller/string_coercion.rb:25:in `call'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/head.rb:
> 9:in `call'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
> methodoverride.rb:24:in `call'
> /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
> action_controller/params_parser.rb:15:in `call'
> /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
> action_controller/session/cookie_store.rb:93:in `call'
> /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
> action_controller/failsafe.rb:26:in `call'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/lock.rb:
> 11:in `call'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/lock.rb:
> 11:in `synchronize'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/lock.rb:
> 11:in `call'
> /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
> action_controller/dispatcher.rb:114:in `call'
> /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
> action_controller/reloader.rb:34:in `run'
> /usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
> action_controller/dispatcher.rb:108:in `call'
> /usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/rails/rack/
> static.rb:31:in `call'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
> urlmap.rb:46:in `call'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
> urlmap.rb:40:in `each'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
> urlmap.rb:40:in `call'
> /usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/rails/rack/
> log_tailer.rb:17:in `call'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
> content_length.rb:13:in `call'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/handler/
> webrick.rb:50:in `service'
> /usr/local/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
> /usr/local/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
> /usr/local/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
> /usr/local/lib/ruby/1.8/webrick/server.rb:162:in `start'
> /usr/local/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
> /usr/local/lib/ruby/1.8/webrick/server.rb:95:in `start'
> /usr/local/lib/ruby/1.8/webrick/server.rb:92:in `each'
> /usr/local/lib/ruby/1.8/webrick/server.rb:92:in `start'
> /usr/local/lib/ruby/1.8/webrick/server.rb:23:in `start'
> /usr/local/lib/ruby/1.8/webrick/server.rb:82:in `start'
> /Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/handler/
> webrick.rb:14:in `run'
> /usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/commands/
> server.rb:111
> /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `gem_original_require'
> /usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
> `require'
> script/server:3 --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
I'm doing a series of ruby on rails tutorials and it got to a part where i need to edit the following files that should be automatically inside the public folder: dispatch.cgi,dispatch.fcgi,dispatch.rb but I have none of these inside my public folder. Is there a reason for this? And how can i change it so they are back The only files in my public folder at present are 404.html 500.html 422.html images javascripts stylesheets favicon.ico
index.html robots.txt --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
I'm doing a series of ruby on rails tutorials and it got to a part where i need to edit the following files that should be automatically inside the public folder: dispatch.cgi,dispatch.fcgi,dispatch.rb but I have none of these inside my public folder. Is there a reason for this? And how can i change it so they are back The only files in my public folder at present are 404.html 500.html 422.html images javascripts stylesheets favicon.ico
index.html robots.txt --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Mar 24, 2010 at 1:27 PM, mr_jake < jacob.d.lichner@gmail.com> wrote: > I've installed this extensions and made sure to run the migrate and > update tasks and the attachment does show up on my pages, yet the > green plus icon does nothing when clicked. > > I did research it and it seems someone had this problem before: > http://lists.radiantcms.org/pipermail/radiant/2009-January/011925.html> > Any solutions? what version of radiant? what version of page_attachments? i think the
master branch of page_attachments is already updated for 0.9 and so
you need to checkout the 0.8 branch (or tag) to work with the current
release version of radiant. if you're on radiant master and
page_attachments master then look for javascript errors and output in
your application log files. > Also, is there any reason why I SHOULDN'T use this extension? Should I
> be using paperclip instead? they are two different approaches to the same problem. pick the one
that you prefer. personally i prefer the "this file belongs to this
page" concept of page_attachments better (and my clients were confused
by the "bucket" approach of paperclipped; e.g. "why do i have to
delete the file two times?"). --
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/ To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
On Wed, Mar 24, 2010 at 1:23 PM, mr_jake < jacob.d.lichner@gmail.com> wrote: > > On Mar 24, 10:04 am, john muhl < johnm...@gmail.com> wrote: >> when you get a bunch of pages >> under any particular parent the hierarchical page view doesn't work so >> well. > > Why is that, exactly? What do you suggest? it's nothing specific to radiant but i just don't think a tree view or
whatever you call it is well suited to handle hundreds or thousands of
children. as for radiant when you click the disclosure triangle to see a page's
children there is an ajax request made and if you have to fetch
hundreds or thousands of records from the database the time between
the click and the children appearing may not be instantaneous. i've
never had a page with anywhere near that many children so i'm just
guessing. perhaps someone with that experience will chime in. --
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/ To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
Hi I am trying to submit an asp form using Mechanize. I have to parse this site in order to get the results http://www.vitranexpress.com/home/CombinedHome.aspx So for this I have to log in the site which I was successful using Mechanize. Once you logged in you have to select the Link "Rate Quoter". Again using mechanize I got the page that this link pointed to. There is a form which I need to submit to get the shipping charges. To submit that you need to enter the destination zip code. With actual site when you enter the destination zip code it passes an ajax request to the server and returns the area matching the zip code. Once that is done you enter the weight and class. With mechanize I was able to set the destination zip code, weight and class. But when I try to submit it returns me the same form every time. I searched the net for help. I found that the asp.net uses a field "__EVENTTARGET" to be set to submit a form. I tried doing that too but it didn't worked. I would like to know how do I do this. Thank you, Nirav -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Sent from my iPhone On Mar 24, 2010, at 10:06 AM, Ken Foust <lists@ruby-forum.com> wrote: > Conrad Taylor wrote:
>> On Fri, Feb 19, 2010 at 1:08 AM, RaW <rafal@wrzochol.net> wrote:
>>
>>> I think
>>> $ script/generate
>>> has been replaced with
>>> $ r g
>>> in Rails3
>>>
>>> Am I right?
>>>
>>>
>> You'll need to do the following in Rails 3:
>>
>> rails g model user_session
>>
>> Then just edit the file and you should be good to go.
>>
>> Good luck,
>>
>> -Conrad
>
> thanks conrad
> so we scrap the rails generate session user_session
> and just make a new model?? Yes, the generators within Authlogic haven't been updated for Rails
3. Thus, you'll need to manually create the required model for your
application. Good luck, -Conrad > --
> Posted via http://www.ruby-forum.com/.
>
> --
> You received this message because you are subscribed to the Google
> Groups "Ruby on Rails: Talk" group.
> To post to this group, send email to rubyonrails-
> talk@googlegroups.com.
> To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
> .
> --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
hi, im currently utilizing searchlogic. now they want me to add a "searchagent", meaning u can save your criterias and get notified whenever something suitable hits the database. am i correct that all i need to do is to store the searchlogic-params in a userfield and run a daily job to execute the search? or is there "more" to it? thx for any advise tom -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Mar 24, 2010 at 10:31 AM, ES < emstolfo@gmail.com> wrote: > I have an hash of display names and their corresponding object > attribute names called @columns. > As I iterate through @columns, what is the syntax for accessing the > attribute of the object using c? I get an error on the 4th line. > <% for c in @columns["object_"+@object.categorie] do %>
> <tr>
> <td class="name"><%=c.first%></td>
> <td><%= @object.c.second %></td>
> </tr>
> <% end %> It's really hard for me to tell what you're trying to do here. How about
we simplify and take it from there? <% @columns.each do |key, value| %>
<%= key %> = <% value %>
<% end %> Now, what is "@object" and how does it relate to the contents of
either 'key' or 'value'? --
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
I have LabGroup and LabDesc which have many through LabDescGroup. I'd like to identify LabDescs which don't have a LabGroup. This works: x = []
LabDescGroup.find( :all, :select => 'DISTINCT lab_desc_id' ).each{ |c|
x << c.lab_desc_id }
y = []
LabDesc.find( :all, :select => 'id' ).each{ |c| y << c.id }
notfound = x - y But is there a more elegant way? It feels like I should be able to do
this entirely through queries, but I'm not seeing the solution. --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Hey all, in building an application that will require multiple ajax calls
occuring concurently to different database tables in order to display
data in a form, and then require user input to modify data and then
update it to the database, which invokes a multi-step transaction, that
is, making updates to multiple database tables, I was told in order to
do this using rails and ajax, a good approach would be using tuple
spaces and rails. I never heard of this concept of tuple spaces before.
I went on wikipedia and found the following description. I'm afraid I
don't understand it. Any intepretations? Thanks. "In computer science, tuples are directly implemented as product types
in most functional programming languages. More commonly, they are
implemented as record types, where the components are labeled instead of
being identified by position alone. This approach is also used in
relational algebra."
--
Posted via http://www.ruby-forum.com/. --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Mar 24, 2010, at 7:40 AM, tispratik wrote: > Hello,
>
> Does anyone know the reason for the vulnerability in Twitter when a
> lot of DOS attacks were made?
> Were they due to the design of the application or the server where
> they hosted got attacked?
It was a widely publicized distributed denial of service attack.
Thousands of zombie machines were used to connect to Twitter,
eventually using up all available resources. No application design
decision could have defended against this, only more machines.
-j
---
John Adams (@netik)
Retina Communications
jna@retina.net
http://www.retina.net/tech
this email is: [ ] bloggable [ x ] ask first [ ] confidential
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
can anybody tell me what is going wrong from the information taken from the development log below. WHen i start WEBrick and try and view a page on the localhost i get the following error, "We're sorry, but something went wrong.We've been notified about this issue and we'll take a look at it shortly." I'm a complete beginner and really want to start learning Ruby on rails, but cannot at the moment get past the setup phase despite a long time trying and i feel I'm almost there. Hope someone can help. # Logfile created on Wed Mar 24 17:13:17 +0000 2010/!\ FAILSAFE /!\
Wed Mar 24 17:13:27 +0000 2010
Status: 500 Internal Server Error
uninitialized constant Encoding
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:443:in `load_missing_constant'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:80:in `const_missing'
/usr/local/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/
active_support/dependencies.rb:92:in `const_missing'
/usr/local/lib/ruby/gems/1.8/gems/sqlite3-0.0.8/lib/sqlite3/
encoding.rb:9:in `find'
/usr/local/lib/ruby/gems/1.8/gems/sqlite3-0.0.8/lib/sqlite3/
database.rb:66:in `initialize'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/sqlite3_adapter.rb:13:in `new'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/sqlite3_adapter.rb:13:in
`sqlite3_connection'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:223:in
`send'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:223:in
`new_connection'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:245:in
`checkout_new_connection'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:188:in
`checkout'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:184:in
`loop'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:184:in
`checkout'
/usr/local/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:183:in
`checkout'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:98:in
`connection'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:326:in
`retrieve_connection'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_specification.rb:
123:in `retrieve_connection'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_specification.rb:
115:in `connection'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/query_cache.rb:9:in `cache'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/query_cache.rb:28:in `call'
/usr/local/lib/ruby/gems/1.8/gems/activerecord-2.3.5/lib/
active_record/connection_adapters/abstract/connection_pool.rb:361:in
`call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
action_controller/string_coercion.rb:25:in `call'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/head.rb:
9:in `call'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
methodoverride.rb:24:in `call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
action_controller/params_parser.rb:15:in `call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
action_controller/session/cookie_store.rb:93:in `call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
action_controller/failsafe.rb:26:in `call'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/lock.rb:
11:in `call'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/lock.rb:
11:in `synchronize'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/lock.rb:
11:in `call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
action_controller/dispatcher.rb:114:in `call'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
action_controller/reloader.rb:34:in `run'
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.3.5/lib/
action_controller/dispatcher.rb:108:in `call'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/rails/rack/
static.rb:31:in `call'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
urlmap.rb:46:in `call'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
urlmap.rb:40:in `each'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
urlmap.rb:40:in `call'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/rails/rack/
log_tailer.rb:17:in `call'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/
content_length.rb:13:in `call'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/handler/
webrick.rb:50:in `service'
/usr/local/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/usr/local/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/usr/local/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/usr/local/lib/ruby/1.8/webrick/server.rb:162:in `start'
/usr/local/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/usr/local/lib/ruby/1.8/webrick/server.rb:95:in `start'
/usr/local/lib/ruby/1.8/webrick/server.rb:92:in `each'
/usr/local/lib/ruby/1.8/webrick/server.rb:92:in `start'
/usr/local/lib/ruby/1.8/webrick/server.rb:23:in `start'
/usr/local/lib/ruby/1.8/webrick/server.rb:82:in `start'
/Users/peterorpete/.gem/ruby/1.8/gems/rack-1.0.1/lib/rack/handler/
webrick.rb:14:in `run'
/usr/local/lib/ruby/gems/1.8/gems/rails-2.3.5/lib/commands/
server.rb:111
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`gem_original_require'
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in
`require'
script/server:3 --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Role : Sybase IQ Developer Location : Tampa FL
Duration : 6m
Client : Banking Sybase IQ Developer needed with 5-7 yrs exp
Thanks and Regards,
Murali
571 483 2829
Javaji Systems Solutions Inc.,
www.javaji.com -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Read More…
Hi Friends,
Plz send profiles matching the requirement to murali@javaji.com
Title : UAT Coordinator
Location : NJ
Duration : 6m
Client : Banking
UAT testing/ project coordination skills
Thanks and Regards,
Murali
571 483 2829
Javaji Systems Solutions Inc.,
www.javaji.com -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Read More…
I have an hash of display names and their corresponding object attribute names called @columns. As I iterate through @columns, what is the syntax for accessing the attribute of the object using c? I get an error on the 4th line.
<% for c in @columns["object_"+@object.categorie] do %>
<tr>
<td class="name"><%=c.first%></td>
<td><%= @object.c.second %></td>
</tr>
<% end %> --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
re: where is it read from?: I use passenger to serve my rails apps these days (all running on *nix), and per the passenger docs: http://www.modrails.com/documentation/Users%20guide.html#_passengertempdir_lt_directory_gt ...
5.10. PassengerTempDir <directory>
Specifies the directory that Phusion Passenger should use for storing
temporary files. This includes things such as Unix socket files,
buffered file uploads, etc.
... The default for that on *nix is the /tmp dir. So, under such a setup,
when a user uploads a file via the rails app, that uploaded file is
temporarily saved under the /tmp dir. That's why I was saying that if
you didn't want to save the file in terms of the app's context, ie you
just want to parse/process the uploaded file's content, you shouldn't
have to do anything else with that /tmp file, since the underlying os
will handle that clean up of /tmp files as necessary. Jeff On Mar 23, 5:29 pm, GoodGets <goodg...@gmail.com> wrote:
> @Luke: Thanks! Yeah, I saw that tutorial, too. But, also like you
> said, it still saves it to a model, so I'd rather just let paperclip
> handle all that. Thank you anyway though.
>
> @Jeff: Thank you!
> For full disclosure, I'm still a little bit of a noob to Rails (and
> ruby) but I think I get more than the gist of your code. So,
> definitely a big thanks.
>
> I do have a couple questions as to what's going on though. Like I get
> that the file is read, along with its contents, but where is it read
> from? Like, is the file actually uploaded to a temp directory, and
> you're saying that I just don't have to expressly mess with that
> directory? Or, is it just held in memory in a Rails process
> somewhere? Might that be worse than just storing the file, then
> deleting it later?
>
> I'm just asking, I honestly don't know. Also, while the file uploads,
> a Rails process is not tied up, correct? It's actually being buffered
> by the server?
>
> A big thank you Jeff, and to anyone else that wants to chime in. I
> think this is definitely a huge start down the right path.
>
> On Mar 23, 11:35 am, Jeff Lewis <jeff.bu...@gmail.com> wrote:
>
>
>
> > One way would be to just process the uploaded-file data from the
> > request as needed and not worry about saving or doing anything else
> > with the tmp-saved uploaded-file itself, something like:
>
> > ### in ./app/models/uploadable_file.rb
> > class UploadableFile
>
> > ### for use in testing:
>
> > def initialize(fname, contents)
> > @fname = fname
> > @contents = contents
> > end
>
> > def original_filename
> > return @fname
> > end
>
> > def read
> > return @contents
> > end
>
> > ### class meths:
>
> > def self.parse(upfile)
> > return nil if upfile.blank? or not (upfile.respond_to?
> > ('original_filename')\
> > and upfile.respond_to?('read'))
>
> > orig_fname = upfile.original_filename
> > contents = upfile.read
> > # parse/process contents ....
> > end
> > end
>
> > Then just call that class meth in your controller to parse the
> > uploaded file for an example file form element of name "upfile":
>
> > ### in some controller meth that handles that multipart/form-data
> > form:
> > ...
> > parsed_contents = UploadableFile.parse(params[:upfile])
> > # check results ....
>
> > Jeff
>
> > On Mar 22, 9:37 pm, GoodGets <goodg...@gmail.com> wrote:
>
> > > parsing the file's not the problem, just not sure what to do with it
> > > before or after. I was thinking about uploading the files using
> > > Paperclip, parsing it, then deleting itfrom the database. But, that
> > > all seems a little unnecessary, especially if I don't care if they are
> > > even saved.
>
> > > I then thought about grabbing them from the temp directory, but
> > > honestly wasn't sure how to go about doing that. So before I really
> > > delve into the Tempfile, should I even worry about it in the first
> > > place? Each user uploaded file will be like 30kb max, and I'll only
> > > be processing a couple hundred a month. Also, I'm hosted on heroku,
> > > so the s3 transfers (if I do save the file) will be free. What ya
> > > think?
>
> > > Any advice really is appreciated --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
> for example I have the following simple code in my views: > > <%= link_to "Here", :controller => 'home', :action => 'inside_here' %> > > I get the "actual" view in the page looking like this: > > Here (/home/inside_here) > > where the underlying url is showing right beside the "Here" word. By > default, the "Here" word should only be outputted and not the path > underneath it. > > Since we presently have no solution to this, my front-end guy keeps on > enclosing these links with <divs> so as to hide the underlying links. > It's a big headache for him.. he's stressed. > > Does anybody have any suggestion on what's happening? Maybe there's > something wrong with the layout or with the stylesheets? Or > javascript? Since the front-end guy was previously developing using > Php and HTML that there might be some tiny detail that shouldn't be > used in Rails by convention. Although he knows the basics needed to > output stuff (like link_to, image_tag, etc) in Rails... Thanks a lot!
My guess is you have some javascript that is doing this. Rails
doesn't do this by default.
Or, perhaps you have installed a plugin that overrides how link_to
works. -philip --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On Wed, Mar 24, 2010 at 10:35 AM, mr_jake < jacob.d.lichner@gmail.com> wrote: > This new site is basically a big blog. There's going to be, oh, > probably hundreds of articles in, say, 10 categories with photos, > advertising, etc. There will be multiple authors publishing anywhere > from 5-10 articles a week when it really gets going, etc. All of the > content will be published through the site itself (nothing is being > pulled from outside sources). No comments, nothing fancy. The home > page will feature articles in all 10 categories while each category > will feature articles in that particular category. There will be a > tagging system and a search function and that's it. i think the main consideration is that when you get a bunch of pages
under any particular parent the hierarchical page view doesn't work so
well. > One of my major concerns is performance. Should I be concerned about
> that and what else should I be concerned about? depends on if you mean front-end performance or the performance of the
admin ui. i wouldn't worry about the former until your traffic
requires a multiple server setup; and the latter is mostly acceptable
in my experience. --
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/ To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
On Wed, Mar 24, 2010 at 12:41 PM, Mislav Marohnić < mislav.marohnic@gmail.com> wrote: > On Wed, Mar 24, 2010 at 17:34, Jim Gay < jim@saturnflyer.com> wrote: >> >> Radiant::Cache.clear > > That deletes all cached files. I wouldn't use this aggressively—Radiant > already uses it too much (on every create/update/destroy action) and I > wanted to make this better so it will never be called again unless there is > real need to delete absolutely all cached data. > Well, Radiant is aggressive about it because there is no easy way of
knowing what page, snippet or layout contains what parts of other
pages or snippets. There's no registry of content to know where some
cached page should expire and some other cached page shouldn't. There is an issue for per-key purging
http://github.com/radiant/radiant/issues#issue/82 which would require
something like http://github.com/svenfuchs/rack-cache-purge (unless it
gets pulled into rack-cache proper).
But even with that, there still would need to be an index of what
content includes what other content if you wanted page saving to only
expire a single cache key.
--
Jim Gay
http://www.saturnflyer.com
--
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/ To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
for example I have the following simple code in my views: <%= link_to "Here", :controller => 'home', :action => 'inside_here' %> I get the "actual" view in the page looking like this: Here (/home/inside_here) where the underlying url is showing right beside the "Here" word. By
default, the "Here" word should only be outputted and not the path
underneath it. Since we presently have no solution to this, my front-end guy keeps on
enclosing these links with <divs> so as to hide the underlying links.
It's a big headache for him.. he's stressed. Does anybody have any suggestion on what's happening? Maybe there's
something wrong with the layout or with the stylesheets? Or
javascript? Since the front-end guy was previously developing using
Php and HTML that there might be some tiny detail that shouldn't be
used in Rails by convention. Although he knows the basics needed to
output stuff (like link_to, image_tag, etc) in Rails... Thanks a lot! --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Thanks for replying, Gintautas. The typo was not in the environment.rb. I did try to add "require 'rubygems' " before require 'zip/zip' but it
still doesn't work.
nor "require 'composite_primary_keys' " works. It seems the gems installed is not recognized at all. :' ( On Mar 24, 4:12 pm, Gintautas Šimkus <dihita...@gmail.com> wrote:
> There is a typo in initilizer. Also require 'rubygems` in your code before
> requiring zip/zip
>
> 2010/3/24 Jay <janus...@gmail.com>
>
>
>
> > First of all, Let me list my configurations:
>
> > FreeBSD 8.0
> > Ruby 1.9.1p376
> > Rails 2.3.5
> > rubyzip 0.9.4 installed in /usr/local/lib/ruby19/gems/1.9/gems/
> > rubyzip-0.9.4
>
> > I have placed the following line inside Rails::Initializer.run block
>
> > cconfig.gem 'rubyzip', :lib => 'zip/zip'
>
> > However, I got a "no such file to load -- zip/zip" error while I have
> > placed a line in a controller file
> > require 'zip/zip'.
>
> > Could somebody give me a hand? Thanks in advance! --
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
On 24 Mar 2010, at 14:21, 31 30 wrote: > With the move to Radiant::Cache, Andrea Franz's DynamicPage extension
> no longer works.
>
> The key section is:
>
> cache = ResponseCache.instance
> self.ancestors.each do |ancestor|
> cache.expire_response(ancestor.url) if ancestor.class_name
> == 'DynamicPage'
> end
>
> Can someone give me a hint as to the appropriate replacement for
> ResponseCache.instance.expire_response() using the new Radiant::Cache
> implementation ? At the moment there's no way to remove a single url from Rack::Cache. It's not really meant to work that way. To use it properly we need a lightweight way to check etags and invalidate stale cache entries. I believe the only way to get rid of a cache entry with current versions of radiant is to call Radiant::Cache.clear. best, will --
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/ To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
On Wed, Mar 24, 2010 at 17:34, Jim Gay <jim@saturnflyer.com> wrote:
Radiant::Cache.clear
That deletes all cached files. I wouldn't use this aggressively—Radiant already uses it too much (on every create/update/destroy action) and I wanted to make this better so it will never be called again unless there is real need to delete absolutely all cached data. -- Radiant CMS Dev Mailing List Post: radiantcms-dev@googlegroups.com Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com Group Site: http://groups.google.com/group/radiantcms-dev/ To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
On Wed, Mar 24, 2010 at 15:21, 31 30 <3130@mail.com> wrote:
Can someone give me a hint as to the appropriate replacement for
ResponseCache.instance.expire_response() using the new Radiant::Cache
implementation ?
What does DynamicPage do?
There isn't a trivial way to expire the response stored by Rack::Cache. You should make sure that the next response returned by Radiant would set the cache headers in a way that Rack::Cache sees that the stored page is obsolete. -- Radiant CMS Dev Mailing List Post: radiantcms-dev@googlegroups.com Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com Group Site: http://groups.google.com/group/radiantcms-dev/ To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
I'm planning on doing a website with Radiant, but I read somewhere that if your site is big and has a lot of articles, then it's best to look elsewhere. Is this true? How big is too big for Radiant and what is Radiant NOT suited for? I really would like to use Radiant for my project for various reasons,
but I don't want to use the wrong tool for the job just because I'm
fond of the tool, if you know what I mean. This new site is basically a big blog. There's going to be, oh,
probably hundreds of articles in, say, 10 categories with photos,
advertising, etc. There will be multiple authors publishing anywhere
from 5-10 articles a week when it really gets going, etc. All of the
content will be published through the site itself (nothing is being
pulled from outside sources). No comments, nothing fancy. The home
page will feature articles in all 10 categories while each category
will feature articles in that particular category. There will be a
tagging system and a search function and that's it. One of my major concerns is performance. Should I be concerned about
that and what else should I be concerned about? Thanks guys! --
Radiant CMS Dev Mailing List
Post: radiantcms-dev@googlegroups.com
Unsubscribe: radiantcms-dev-unsubscribe@googlegroups.com
Group Site: http://groups.google.com/group/radiantcms-dev/ To unsubscribe from this group, send email to radiantcms-dev+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
hi, im using acts_as_tree and im not sure on how to group find-result. x = find.almost_all <p> <% for y in @x.ancestors.reverse %> <%= link_to h(y.title), page %> > <% end %> </p> gives me a nice "breadcrum". but how is it possible to group the list lets say by the 1level or second level? thx -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
I'm definitely down with refactoring if people think it will be easier to understand. Does someone want to create an LH ticket and submit a patch? If you improve checkout please make sure that the hook functionality for steps (see detailed online docs) is maintained as well. I do think its still useful to allow people to hook into a before and after in the update and edit cases. We can just simplify by not overwriting 50% of r_c in this case. Sean Schofield -------------------------------------------
Rails Dog LLC
2 Wisconsin Circle, Suite 700
Chevy Chase, MD 20815
voice: (301)560-2000
------------------------------------------- On Wed, Mar 24, 2010 at 11:52 AM, Michael Guterl <mguterl@gmail.com> wrote:
> CheckoutsController is the one that stands out to me, OrdersController
> isn't as "bad."
>
> Best,
> Michael Guterl
>
> On Wed, Mar 24, 2010 at 1:03 AM, Sarah Mei <sarahmei@gmail.com> wrote:
>> orders_controller and checkouts_controller are the two I'd target.
>> They're the heart of the application, so it's worth being very
>> explicit about what's happening. Plus since checkouts don't really fit
>> REST, you could do something more natural and end up with a much
>> skinnier controller. win-win!
>>
>> On Tue, Mar 23, 2010 at 7:45 PM, Sean Schofield <sean@railsdog.com> wrote:
>>> So which controllers would we like to see move away from r_c? I still
>>> think checkout should have its own r_c like hooks for the checkout
>>> steps. But we could implement that without making that specific
>>> controller and r_c controller.
>>
>> --
>> You received this message because you are subscribed to the Google Groups "Spree" group.
>> To post to this group, send email to spree-user@googlegroups.com.
>> To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
>> For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups "Spree" group.
> To post to this group, send email to spree-user@googlegroups.com.
> To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
>
> --
You received this message because you are subscribed to the Google Groups "Spree" group.
To post to this group, send email to spree-user@googlegroups.com.
To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
CheckoutsController is the one that stands out to me, OrdersController isn't as "bad." Best,
Michael Guterl On Wed, Mar 24, 2010 at 1:03 AM, Sarah Mei <sarahmei@gmail.com> wrote:
> orders_controller and checkouts_controller are the two I'd target.
> They're the heart of the application, so it's worth being very
> explicit about what's happening. Plus since checkouts don't really fit
> REST, you could do something more natural and end up with a much
> skinnier controller. win-win!
>
> On Tue, Mar 23, 2010 at 7:45 PM, Sean Schofield <sean@railsdog.com> wrote:
>> So which controllers would we like to see move away from r_c? I still
>> think checkout should have its own r_c like hooks for the checkout
>> steps. But we could implement that without making that specific
>> controller and r_c controller.
>
> --
> You received this message because you are subscribed to the Google Groups "Spree" group.
> To post to this group, send email to spree-user@googlegroups.com.
> To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
>
> --
You received this message because you are subscribed to the Google Groups "Spree" group.
To post to this group, send email to spree-user@googlegroups.com.
To unsubscribe from this group, send email to spree-user+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/spree-user?hl=en.
|