I already check with there website, has_attached_file is still valid.
https://github.com/thoughtbot/paperclip#readme
--
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
sorry i meant you should check that you can still pass
:rails_root/public/:class/:attachment/:id/:style_:basename.:extension
instead of
Rails.root.join
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Talk group.
To post to this group, send email
GFP wrote:
I am an RoR newb, so bear with me here. I am on an Intel based Mac
running OS X 10.4.11
Er, why are you still on Tiger?
I have started the 'RoR Essentials' tutorial on lynda.com.
Don't. That tutorial is way out of date. You won't be able to use it
with current Rails versions.
Since I am that much of a newb and unfamiliar with the 'rake' command
(notwithstanding your instructions) I removed the db names from
'database.yml' and that solved the issue - for now.
I suspect I may encounter another issue when I get to the part in the
tutorial when the database *is* created?
Since I am that much of a beginner and not familiar with the rake
command (notwithstanding your instructions) I removded the database
names from the database.yml file and that appears to have resolved the
issue for now. I suspect I may encounter another issue when the/a
database is created (?).
I
On 14 June 2010 12:29, GFP herecomesgr...@gmail.com wrote:
Since I am that much of a beginner and not familiar with the rake
command (notwithstanding your instructions) I removded the database
names from the database.yml file and that appears to have resolved the
issue for now. I suspect I may
check your database.yml as well Yours DBMS Table Schema and if possible
make yours app carefully Again if its not too Large .
On Mon, Apr 12, 2010 at 1:45 PM, sameera sameera...@gmail.com wrote:
Hi
Looks like you are using sqlite as thr database. so make sure you
installed the sqlite gem
check your database.yml, whether the mentioned database name is correct
or not..
--
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
Hi
Looks like you are using sqlite as thr database. so make sure you
installed the sqlite gem
sqlite3-ruby (1.2.5)
you can check this from the command
'gem list' in the command prompt
if not install it using the following command,
gem install sqlite3-ruby
cheers,
sameera
On Apr 9, 5:35
I've got the entire application back to where I was before I thought
upgrading MySQL might be the solution to my problem.
The problem was that I added an expense item which included an amount,
say 10.50. After saving the new item, the expense amount displayed
as simply 10 -- no .50 anywhere. I
Pleas check your routes.rb file and configure your map.root
parameter. You can use the tutorial below or assistance.
tutorial: http://guides.rubyonrails.org/getting_started.html see
section 4
On Mar 13, 2:27 am, kannav rajeev rajeevsharm...@gmail.com wrote:
Check out yours database and table
Richard,
Straight to the point.
There are a few ways to get out of this problem, most of them driving
you to a MySQL DLL downgrade.
IMHO, the fact is MySQL 5.1 doesn't work properly with RoR, so, stick
with 5.0, report the problem to MySQL staff and wait for: an official
patch for 5.1, or for
RichardOnRails wrote:
Hi All,
We're sorry, but something went wrong. is the message I got when I
started up an RoR app in the environment:
Rails 2.3.5
Ruby 1.8.6
WinXP-Pro/SP3
Firefox 3.6
MySQL 5.0.37-community-nt
Mongrel
The app under development was working fine until I
Try reinstalling mysql gem!
On Sat, Mar 13, 2010 at 1:07 AM, Aldric Giacomoni li...@ruby-forum.comwrote:
RichardOnRails wrote:
Hi All,
We're sorry, but something went wrong. is the message I got when I
started up an RoR app in the environment:
Rails 2.3.5
Ruby 1.8.6
Hi Aldric Sandip,
Thanks for your ideas. It's great to have friends around the world.
After I posted the message, I went on a bug hunt that, after two
hours, revealed that the message should have been supplemented with:
Database RTS_Development does not exist. Then I would have known
that
Check out yours database and table is they are fine ?
and if possible rebuilt app
or
reconfigure database.yml
thanks its about database connectivity issue i think
--
Thanks:
Rajeev sharma
--
You received this message because you are subscribed to the Google Groups Ruby
on Rails: Talk group.
I'm going to go out on a limb say that you did not perform your
migrations in the production environment. The find_by* methods are
dynamically generated. No find_by_user_id method = no user_id
column.
On Dec 31, 8:36 am, RubyonRails_newbie craigwest...@googlemail.com
wrote:
Hi all,
Yeah good spot.
I avoided rake db:migrate because of my error posted yesterday that
returned:
rake aborted!
undefined method `reenable' for Rake::Task db:schema:dump =
[environment]:Rake::Task
So I understand your reply, but I don't know how to fix it... Is there
a solution besides manually
I've not kept up with migrations, as we have to use a different method
here. You definitely want to fix your migrations, though.
Priorities, priorities...
On Dec 31, 9:11 am, RubyonRails_newbie craigwest...@googlemail.com
wrote:
Yeah good spot.
I avoided rake db:migrate because of my error
2009/12/31 RubyonRails_newbie craigwest...@googlemail.com:
Yeah good spot.
I avoided rake db:migrate because of my error posted yesterday that
returned:
rake aborted!
undefined method `reenable' for Rake::Task db:schema:dump =
[environment]:Rake::Task
So I understand your reply, but I
Thanks for that ,
I can add it manually, but as you say I'll always be out of sync. I'll
dig a bit deeper.
Thank you
On 31 Dec, 15:27, Colin Law clan...@googlemail.com wrote:
2009/12/31 RubyonRails_newbie craigwest...@googlemail.com:
Yeah good spot.
I avoided rake db:migrate because of
The problem is that form that server I cannot connect to the MSql
server, so the error is, no DB connection. Ii there a way to test the
DB connection of a Rails application?
On Oct 13, 7:02 pm, Hassan Schroeder hassan.schroe...@gmail.com
wrote:
On Tue, Oct 13, 2009 at 10:56 AM, rtacconi
Hi
First check ur database and then give previliage in ur application.
Thanks
On Mon, Oct 19, 2009 at 2:36 PM, rtacconi rtacc...@gmail.com wrote:
The problem is that form that server I cannot connect to the MSql
server, so the error is, no DB connection. Ii there a way to test the
DB
On Mon, Oct 19, 2009 at 2:06 AM, rtacconi rtacc...@gmail.com wrote:
The problem is that form that server I cannot connect to the MSql
server, so the error is, no DB connection. Ii there a way to test the
DB connection of a Rails application?
Are you saying you can't connect manually from the
Sorry, not litterally, it is the tipical Rails error, but it happens
on Tomcat, we Rails deployed as WAR. There is nothing in Rails logs,
nothing in tomcat log too! I have Tomcat on my PC and I get the same
error. But Tomcat in my PC is running stand alone not as development
server, I have not
On Tue, Oct 13, 2009 at 6:33 AM, rtacconi rtacc...@gmail.com wrote:
Sorry, not litterally, it is the tipical Rails error, but it happens
on Tomcat, we Rails deployed as WAR. There is nothing in Rails logs,
nothing in tomcat log too! I have Tomcat on my PC and I get the same
error. But Tomcat
Thanks, for your help.
I created a super simple Rails app with generate scaffolding, one
table with one column. On tomcat on my Win PC the app is working. On
Tomcat on Solaris not. My web.xml is this:
!DOCTYPE web-app PUBLIC
-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN
On Tue, Oct 13, 2009 at 9:08 AM, rtacconi rtacc...@gmail.com wrote:
I created a super simple Rails app with generate scaffolding, one
table with one column. On tomcat on my Win PC the app is working. On
Tomcat on Solaris not. My web.xml is this:
context-param
I changed to development but I cannot see any change, except when I
call http://10.3.111.79:8080/test/posts, Tomcat hangs, does not reply.
On Oct 13, 5:34 pm, Hassan Schroeder hassan.schroe...@gmail.com
wrote:
On Tue, Oct 13, 2009 at 9:08 AM, rtacconi rtacc...@gmail.com wrote:
I created a
Wait wait, I have found this:
13-Oct-2009 18:00:12 org.apache.catalina.startup.HostConfig
deployDescriptor
SEVERE: Error deploying configuration descriptor ROOT.xml
org.xml.sax.SAXParseException: The element type Context must be
terminated by the matching end-tag /Context.
at
On Tue, Oct 13, 2009 at 10:05 AM, rtacconi rtacc...@gmail.com wrote:
Wait wait, I have found this:
13-Oct-2009 18:00:12 org.apache.catalina.startup.HostConfig
deployDescriptor
SEVERE: Error deploying configuration descriptor ROOT.xml
org.xml.sax.SAXParseException: The element type Context
I am deploying a test. I think I have mess up ROOT.xml few days ago. I
will try to have a clean Tomcat, then I will deploy test.war again.
Thanks.
On Oct 13, 6:08 pm, Hassan Schroeder hassan.schroe...@gmail.com
wrote:
On Tue, Oct 13, 2009 at 10:05 AM, rtacconi rtacc...@gmail.com wrote:
Wait
On Tue, Oct 13, 2009 at 10:30 AM, rtacconi rtacc...@gmail.com wrote:
I am deploying a test. I think I have mess up ROOT.xml few days ago. I
will try to have a clean Tomcat
Geez, NO. Just FIX the stupid ROOT context file. The error message
is telling you exactly what's wrong.
No need to
Well I have wasted my time by reinstalling Tomcat :-)
I cannot see any error in catalina.2009-10-13.log, so the ROOT.xml
error is gone. But I still have We're sorry, but something went
wrong. I changed web.xml to development, but I cannot see any log. I
must be a severe error. I have the MySql
On Tue, Oct 13, 2009 at 10:56 AM, rtacconi rtacc...@gmail.com wrote:
I cannot see any error in catalina.2009-10-13.log, so the ROOT.xml
error is gone. But I still have We're sorry, but something went
wrong. I changed web.xml to development, but I cannot see any log.
Did you restart Tomcat
On Mon, Oct 12, 2009 at 9:14 AM, rtacconi rtacc...@gmail.com wrote:
I am using JRuby and I have to deploy on Tomcat. My web app is working
fine in the dev envirmonment, with Mongel, but when I deploy on Tomcat
I get We're sorry, but something went wrong on Tomcat.
? literally, it says went
One thing that you may or may not know is that the default session
storage for Rails is cookies now. Therefore, if you have any
unexpected failures and subsequent bizarre behaviour in your
application, first thing to do is to clear cookies, otherwise you will
be chasing either wrong problems or
Bharat Ruparel wrote:
One thing that you may or may not know is that the default session
storage for Rails is cookies now.
I followed some instructions to uncomment one line in
config/initializers/session_store.rb (rails 2.3), which created database
storage for sessions, hence the repeated
Frederick Cheung wrote:
� attr_reader :items
A hash with a default value that is a proc has (you guessed it) a proc
embedded in it. There are a few places in rails where if things go
badly wrong at a time rails didn't expect it you just get a 'sorry
it's screwed' error rather than the usual
7stud -- wrote:
7stud -- wrote:
Is the error saying Product isn't hashable?
I think that had to do with an old version of the cart implemented with
an array that was still stored in sessions. I cleared my sessions with:
rake db:sessions:clear
and that got rid of the error.
Jeremy McAnally wrote:
It should.
Sorry, I'm not sure what that is referring to.
How are you running your app? If you run it with
script/server, unless you're forcing production mode, you should get a
nice error page with a stack trace, error information, session dump,
etc.
--Jeremy
start your server with
script/server --debugger
or
script/server -u (this is the same)
then set a breakpoint in this method like
def find_cart
debugger
session[:cart] ||= Cart.new
end
then you can look, what is exactly in your session var
the development.log output of the console
Rafael Schaer { beYou media } wrote:
start your server with
script/server --debugger
or
script/server -u (this is the same)
then set a breakpoint in this method like
def find_cart
debugger
session[:cart] ||= Cart.new
end
then you can look, what is exactly in your session
I'm just wondering why rails doesn't display the TypeError along with a
stack trace?
--
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
On p. 678 it says,
If the objects to be dumped [marshaled] include bindings, procedure
[proc] or method objects, ...
a TypeError will be raised.
This is my initialize() method in the Cart class(which is called by
Cart.new):
class Cart
attr_reader :items
def initialize
45 matches
Mail list logo
