I have a before filter that authorizes a user's credentials before
giving them access to any protected methods (pretty standard
practice). If they fail authorization, I want to direct them to a
chance to login or to create an account (also pretty standard
practice).
Here's the rub:
I want to
Hi. I have a site that is currently running in alpha mode. I have
warned my users that it will be bouncing up and down as I deploy
updates. That said, i'd like to broadcast a real time warning to them
when I am about to do so. Something along the lines of:
The site will be brought down for
to find a 'convention' for this.
Thanks always for your generous support!
Yoram
On Feb 18, 12:17 am, Frederick Cheung frederick.che...@gmail.com
wrote:
On Feb 18, 5:38 am, yber...@msn.com yber...@msn.com wrote:
When my controller passes the view an existing object, I submit the
form
, at 13:29, yber...@msn.com wrote:
On the other hand, I could use 'form_for' which generates the same
params hash format for both cases (existing and new object) but does
not include an id. In this case, I would have the controller pass the
view an instance variable: @record_id = 'foo
I'm trying to use 'fields_for' in a form. I want the same form to
support both the creation of new obejcts as well as the editing of old
ones. So - in my controller, sometimes I will pass to the form an
object that already exists in my database and has an id and other
times I will pass it a newly
I'm trying to create a form/view that displays a mix of records that
exist in the database and records that the user is working on but that
don't yet exist in the database. I want to leverage all of rails' nice
form helpers, especially the params hash that it generates for the
records when the
, yber...@msn.com yber...@msn.com wrote:
I'm trying to create a form/view that displays a mix of records that
exist in the database and records that the user is working on but that
don't yet exist in the database. I want to leverage all of rails' nice
form helpers, especially the params hash
...@agileconsultingllc.com wrote:
On Feb 9, 2009, at 9:58 AM, yber...@msn.com wrote:
they did in my first implementation, but - i ended up changing it as
follows: when i first present the form, i find the highest id of the
preexisting record, i store that in '@last_existing_id'. then render
I'm probably missing something very obvious here, but - I just started
noticing error messages from my log, of the form:
ActionController::RoutingError (No route matches /bullet.gif with
{:method=:get}):
These immediately follow:
Processing ApplicationController#index (for 127.0.0.1 at
9 matches
Mail list logo