So, the InPlaceEditor with AJAX is all nice and dandy, works great. What about fields that don''t have any content? As far as I can tell, this doesn''t work so well - there''s nothing to click on so no edit form pops up... Am I missing something? HH
I use before_save actions in my model to ensure that empty fields are filled with ''N/A'' or some other relevant filler. HH wrote:> So, the InPlaceEditor with AJAX is all nice and dandy, works great. > > What about fields that don''t have any content? As far as I can tell, > this > doesn''t work so well - there''s nothing to click on so no edit form pops > up... > > Am I missing something? > > HH-- Posted via http://www.ruby-forum.com/.
Yeah, that would work. What I ended up doing was having an external edit DIV ID and using that to trigger the edit field, sorta like Backpack does. Works great, even on empty fields.> From: Brad Daily <brad@bradleyboy.com> > Reply-To: <rails@lists.rubyonrails.org> > Date: Fri, 10 Mar 2006 01:50:46 +0100 > To: <rails@lists.rubyonrails.org> > Subject: [Rails] Re: In Place Editor and Empty Fields > > I use before_save actions in my model to ensure that empty fields are > filled with ''N/A'' or some other relevant filler. > > HH wrote: >> So, the InPlaceEditor with AJAX is all nice and dandy, works great. >> >> What about fields that don''t have any content? As far as I can tell, >> this >> doesn''t work so well - there''s nothing to click on so no edit form pops >> up... >> >> Am I missing something? >> >> HH > > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails
Hi, I''ve seen quite a few posts about this problem, but still can''t seem to find an answer. I''m trying to set up multiple apps on our web hosting server ( running CentOS with Apache 1.3) and on two of my apps I keep getting the error: FastCGI: incomplete headers (35 bytes) received from server "/path/ app/public/dispatch.fcgi" These apps have run on this server before. I know this is often caused by session conflicts but I have closed the browser, emptied its cache and deleted all session data on the server and it makes no difference. ( Besides, all the apps but one have special session_keys set. Neither of the working apps have a special session key set. However, if I remove that feature from the broken ones, it doesn''t help. ) Apparently it is also sometimes caused by problems with the database.yml file, so I copied the database.yml file from one of the working apps( they both use the same database - the working app has more extensive permissions.) No joy. Does anyone have any other suggestions? I am baffled. Thanks, Denise