It is really worthwhile googling REST and Rails, and reading about the 
underlying expectations of the Rails framework. If you do things the way it 
expects, then your job becomes easier. Not trivially easy, but considerably 
easier.

Are Invoices structurally different than a Page? Do they need separate rules, 
or different roles to access them for editing, or a means of payment? I would 
argue that adding an invoice to a pages_controller would probably mean a lot 
harder work ahead for you than just creating a separate model and controller to 
handle these.

Walter

> On Oct 24, 2018, at 11:51 AM, Joe Guerra <jgue...@jginfosys.com> wrote:
> 
> I've got a pages controller [which is a catch all for most pages on my site] 
> and in it, I have defined an invoice page.
> 
> Just a bunch of users I would need to invoice [manually for now]
> 
> so, I created a method called 'update_invoice_link'.  how would I manually 
> create this route and what action or url do I need in my form field?
> 
> Thanks,
> Joe
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-talk+unsubscr...@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-talk/804cc6ce-c3c9-4334-ad33-3135d22c5942%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-talk+unsubscr...@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/C4FEFF6F-9A79-47AF-BF77-7FDADBEB95F1%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to