similar to: newbie q about saving data to mysql

Hi, I am logging users in and keeping them in session. The problem I am having is showing only a certain logged in user''s information. In the Adverts_Controler: def show @advert = Advert.find(params[:id]) end I am also having issues with saving an advert for an user: def create @advert = Advert.new(params[:advert]) if @advert.save flash[:notice] = ''Advert

i have a Project model, which belongs_to :user when i add a project, the users_id is based on the session[:users_id]. to get the users_id into the projects table, i''m doing this: @project = Project.new(params[:project]) @project.users_id = session[:users_id] this is working, i''m just verifying this is the best way to do it.

One of these days I''ll figure this out, but in the meantime help me be a better programmer by eliminating some excess code: I''m trying to check to see if somebody trying to view/edit/update a product is the owner. In my scaffold I have this code that works: def edit @owner = Product.find(params[:id].to_i) if @owner.user_id == @user.id @product =

I have some code working that lists only items from a particular user. The code in my list action finds the user and then conditionally lists only his/her items: def list user = User.find(session[:user]) user_id = user.id @product_pages, @products = paginate :products, :per_page => 10, :conditions =>[''user_id = ?'', user.id]

I''m trying to create a basic web page where people can register. Before they are approved they are emailed a link where that they must click in order to verify their info is correct (or at least their email). Should I use acts as authenticated or the login engine for this? http://technoweenie.stikipad.com/plugins/show/Acts+as+Authenticated http://rails-engines.org/login_engine TIA

In my database I have a products table that has a bunch of attributes (title, description, etc) including one for date_expires. Is there a best practices method to get the database to erase the expired items? Is that done outside RoR via Cron or something? Else is it better to just have my app filter out anything that is expired but still keep those records in my dbase? -- Posted via

Clearly I have the session and can see that session[:user_id] = 7 Now I want to use the results of this...in a page...so I am trying to use the instance variable @sess_user and at the top of the application controller, I have either... @sess_user = User.find([:first, "id = ?", session[:user_id]) or @sess_user = User.find([:first, "id = ?", session[:user_id]) gives me an

Hi Im uisng the lgoin generatior that as far as I can tell stores the username in session. I have another table that i need to store the id of the user who creates an entry. (the logged in user) Is it possible to store return the id and store it in session once the user is created. then do somthing like @project.user_id = session[:user].id; or can I perform a search in the product table

My question is whether there''s a more idiomatic rails way of structuring this query or of redoing the underlying models. First, the ugly find_by_sql code, which is the method to generate an atom feed: def atom items_per_feed = 15 sql_query = "SELECT activities.*, users.real_name AS real_name, accounts.last_scraped_at AS last_scraped_at,

Throughout my Message controller, I do this a lot: @message = Message.find(params[:id],:conditions => ["user_id = ?", @session[''user''].id]) Since you need to authenticate to use this app, is there a way i can tie the Accounts model in with the Message model so I dont have to pass in the user_id everytime? --~--~---------~--~----~------------~-------~--~----~ You

I''m messing with the agiles store example. I added a field in my product table (user_id) that is also a foreign key relationship via fk_products_user In my scaffold I''d like to list the products as usual, but only those products from the logged in user. I assume that would be done in the controller.. How would I extend the basic controller: def list @product_pages,

I have a bunch of queries to compute some counters, like find_by_sql(<<-SQL SELECT p.*, c.nfavourites FROM people p, ( SELECT fp.person_id, COUNT(fp.user_id) as nfavourites FROM favourite_people fp, users u WHERE fp.user_id = u.id AND u.cluster = ''#{in_cluster_of_user.cluster}'' GROUP BY fp.person_id ) as c WHERE

This is pretty simple, but I must be missing the obvious. I''ve got a table that''s similar to this: USERS: - id int - username varchar(64) - password varchar(64) - role_id int ROLES: - id int - description varchar(16) I''ve had no troubles doing has_many relationships at all. But I want to map the user.role directly to the role model automatically (which sounds

My layout calls a few links like so: <%= link_to ''| Home '', :controller => ''search'', :action => ''''%> <%= link_to ''| Search '', :controller => ''search'', :action => ''''%> I would also like to display two values from my user table in the same layout right after the

I''m looking to do something similar to the "secret URLs" in Rails Recipes, however, with file downloads. I want to avoid providing direct URLs to people if possible. I have files on disk in public/, so it would be good if each user got a "unique" URL to each file that they are permitted to see (dealt with by a user_id/file_id table). Then they are only allowed

Had this error when trying to add comments to another user''s photo. ActiveRecord::StatementInvalid in User photosController#show Mysql::Error: Unknown column ''comments.user_id'' in ''on clause'': SELECT photos.`id` AS t0_r0, photos.`user_id` AS t0_r1, photos.`title` AS t0_r2, photos.`body` AS t0_r3, photos.`created_at` AS t0.... I did create a user_id

In asp you have an Application built-in object, which works just like the Session hash, but it lets you share information among all users of a given application. which is the rails equivalent??? and if there isn''t, how would you implement such a thing ? (there would be concurrency issues to take into account, in fact asp''s application object has some lock and unlock methods

My application needs to know if a user is an administrator, for security and aesthetic reasons. At the moment, I store true/false in the session by doing the following at login: session[:user_is_admin] = authenticated_user.is_admin? Is this OK to do? Or should I really be doing the following every time: User.find(session[:user_id]).is_admin? (user_id is always in the session too) Is there

I''m using Mongrel 1.0.1 and Apache 2.0 to serve up a handulf of Rails applications. Apache proxies requests to the instances of Mongrel and uses ProxyPass and ProxyPassReverse to deliver static files. The Rails application uses sessions, and this appears to be where the issue is occurring. If too many users login to the application, then at some point the application stops

I have two tables: ------------------------------ drop table if exists users; create table users ( id int not null auto_increment, username varchar(100) not null, password varchar(20) not null, firstname varchar(20) not null, lastname varchar(20) not null, primary key (id) ) TYPE = InnoDB; ------------------------------ drop table