Ruby on Rails: Using a different controller with in_place_editor_field
Learn how to use in_place_editor_field in Rails with a different controller, ensuring seamless functionality across views and controllers.
I don’t know why this took a while to figure out, but it did. If you are using the stock Rails in_place_editor_field, you know it looks like this in the controller:
in_place_edit_for :user, :name
And like this in the view:
<%= in_place_editor_field :user, :name %>
This works fine so long as you’re rendering from the users controller. But, what if this view is a partial inside a different controller’s view? In that case, what gets called is not /users/set_user_name but /othercontroller/set_user_name. And, of course, it fails because there is no method (dynamic or otherwise) like that there.
The solution is easy, but the documentation isn’t helpful. You need to alter the view to be like this:
<%= in_place_editor_field :user, :name, {}, :url=>{:controller=>'users', :action=>'set_user_name', :id=>user.id}} %>
The agent-shaped org chart
Every real org has the same topology: principal, role-holder, specialists. Staff AI maps onto it, node for node, and the cost collapse shows up in the deliverables that were always just human-handoff overhead.
AI as staff, not software
Two frames for what AI is doing to work. The tool frame makes tools smarter. The staff frame makes roles unnecessary. Those aren't the same product, the same company, or the same industry.
Knowledge work was never work
Knowledge work was always coordination between humans who couldn't share state directly. The artifacts were never the work. They were the overhead — and AI just made the overhead optional.
The work of being available now
A book on AI, judgment, and staying human at work.
The practice of work in progress
Practical essays on how work actually gets done.
Shopping is the last mile
Every meal planning app treats cooking as the hard problem and shopping as a logistics detail. They have it backwards. Cooking is mostly solved. Shopping is the last mile.
Watch what they buy, not what they say
Forms ask people to declare preferences. Receipts record what they did. The gap between the two is where revealed preference lives, and it's wider than most product teams admit.
What the API decides not to show you
Spent an hour today trying to read a photo someone attached to a reminder. The bytes are right there on disk. Apple won't let me see them. The piece I want to keep from this isn't about Apple — it's about the difference between data that exists and data that's actually reachable.
Nomethoderror (undefined method `finder’) with engines and Rails 2.2
Fix the NoMethodError with ActionMailer in Rails 2.2 by applying a simple patch. Save time and troubleshoot efficiently with our guide.
Place custom Rails routes first
Learn how to prioritize custom Rails routes for error-free routing and improved functionality in your web applications. Optimize your code now!
In_place_editor with a collection in a partial in Ruby on Rails
Easily implement in_place_editor for collections in Ruby on Rails partials with this straightforward guide and troubleshooting tips. Save time and simplify...