-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in Rails 6 #339
Comments
@wernerlaude using master branch seems to have fixed this issue for me,
|
Thanks.. |
Could be closed after the release :) |
Can you try |
Confirmed, it works with Rails 6.0.0.rc1 and the 1-6-stable branch. |
Since Rails 6 is coming up, could you make a release of the 1-6 branch so that everybody are able to test if the rest of their application are releasable with Rails 6. |
Any news on a release that's compatible with Rails 6? |
Hey guys, I released 1.6.4, can you please try if it helped? /cc @hllewelyn @jesperronn @tbuehlmann @dmitry |
Just tried it out, switching from the 1-6-stable branch to 1.6.4 seems to work for me. |
As of 1.6.4 version, I have Rails 6 and Mongoid with mongoid orm configration, but I got |
I have a same issue with Feuda when using with MongoId |
same issue here, pretty blocking. Has anyone a workaround for that ? |
@dfabreguette-ap seems like repo is abandoned, you can check some forks here: https://github.com/chaps-io/public_activity/network |
@Feuda @dfabreguette @dmitry Is that still a problem for you? Development stalled for a while but overall this gem is not abandoned; quite the opposite. However, personally, I have no need for Mongo, so not sure the adapters even work at this point. I’ll happily accept a patch. Otherwise, I might remove the Mongo adapters entirely. |
@ur5us good to hear. Do you have a fix for this issue. I have the exact same problem in Rails 7. I get things like
when everything is setup as per the 2012 docs |
@noctivityinc Not in front of my computer but it looks like the # change this
tracked owner: Proc.new{ |controller, model| controller.current_user }
# to this
tracked owner: Proc.new{ |controller, model| controller.send :current_user } |
Perfect thanks. Im also wondering if the new Current class can be used.
…On Aug 9, 2024 at 3:54:36 PM, Juri Hahn ***@***.***> wrote:
@noctivityinc <https://github.com/noctivityinc> Not in front of my
computer but it looks like the current_user method is not private so
you'd need to adapt the following line:
# change thisinclude PublicActivity::Modeltracked owner: Proc.new{ |controller, model| controller.current_user }# to thisinclude PublicActivity::Modeltracked owner: Proc.new{ |controller, model| controller.send :current_user }
—
Reply to this email directly, view it on GitHub
<#339 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAATIAXGOHD2OR5HJDOAFKTZQUM7ZAVCNFSM6AAAAABMIZFTXSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYGY2DMMBYHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sorry for the late response, I think YES, I removed it from Gemfile and quite |
@noctivityinc I haven’t tried it but I’d expect |
I have:
class ApplicationController < ActionController::Base
protect_from_forgery with: :exception
include PublicActivity::StoreController
class Documentation < ApplicationRecord
include PublicActivity::Model
tracked owner: Proc.new{ |controller, model| controller.current_user }
and i get:
unknown attribute 'owner' for PublicActivity::Activity.
Not working in Rails6?
Thanks for help.
The text was updated successfully, but these errors were encountered: