Ruby on Rails Tuesday, October 7, 2014

Yes, please specify exactly what you mean when you say "to the resource" or "from that view"

Normally you would do think about this in terms of quiz controller (but really you should pass this off to a domain layer).

Your question (the way I interpreted it) was where/how can you access the scope of current_user. The answer is explained in that stackoverflow post.

-Jason


On Oct 7, 2014, at 10:42 AM, Colin Law <clanlaw@gmail.com> wrote:

> On 7 October 2014 14:59, Joseph Wilks <lists@ruby-forum.com> wrote:
>> Well it already inherits from ApplicationController by default, and I'm
>> unable to send an update request form to the resource from that view
>
> It is no good saying you are unable to do something, show us the error
> and the section of code that causes it. Not large chunks of code, a
> few lines should be enough. Also the output in development.log
> relating to the request, if it looks useful
>
> Colin
>
>>
>>
>>
>> Jason Fb wrote in post #1159259:
>>> You should just be able to do that by making the controller a subclass
>>> of ApplicationController
>>>
>>>
>>> explained here:
>>>
>>>
>> http://stackoverflow.com/questions/19147729/access-devise-current-user-variable-in-rails-controller
>>>
>>>
>>>
>>> On Oct 6, 2014, at 9:14 PM, Joseph Wilks <lists@ruby-forum.com> wrote:
>>>
>>>> Thanks in advance for your help.
>>>>
>>> ----
>>>
>>> Jason Fleetwood-Boldt
>>> tech@datatravels.com
>>> http://www.jasonfleetwoodboldt.com/writing
>>>
>>> All material Jason Fleetwood-Boldt 2014. Public conversations may be
>>> turned into blog posts (original poster information will be made
>>> anonymous). Email jason@datatravels.com with questions/concerns about
>>> this.
>>
>> --
>> Posted via http://www.ruby-forum.com/.
>>
>> --
>> 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+unsubscribe@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/e0936c6fdd2715009bd81ad6c77a5cc9%40ruby-forum.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+unsubscribe@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/CAL%3D0gLvjsP8VCeF7M1k9OK3fuukb8y7ChmrDofamfc-%2BgGixew%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

----

Jason Fleetwood-Boldt
tech@datatravels.com
http://www.jasonfleetwoodboldt.com/writing

All material © Jason Fleetwood-Boldt 2014. Public conversations may be turned into blog posts (original poster information will be made anonymous). Email jason@datatravels.com with questions/concerns about this.

--
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+unsubscribe@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/FDA9558D-60E9-4DEF-A7F4-8885E6FF8C12%40datatravels.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment