-
Notifications
You must be signed in to change notification settings - Fork 14
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
Not Rails3 ready? #1
Comments
I got it to work in rails3. The only thing I had to change was in the pfeed/init.rb file, I changed :object to :pfeed_item and made sure all of my individual pfeed item templates (the ones in view/pfeeds) referenced pfeed_item instead of referencing their individual name. (For instance, _user_updated_attribute.html.erb references the object user_updated_attribute, but you have to change it to pfeed_item otherwise it does not work.
|
d'oh, spoke too soon. i'm also having problems; I get basic functionality "__ bought 37 minutes ago" but can't get it to use custom models/views. Everything gets routed through pfeed_item, and looking at the log it looks like this is because pfeed_item objects are always created (never the more specific descendants). |
okay. I got it to work. Maybe your problem is similar? Anyway, hope this helps someone. |
i also have problem using pfeed with rails 3 and got solved by changing pfeed/init.rb :partial => "pfeeds/#{pfeed.view_template_name}.html.erb",:object => pfeed) |
has anyone else been able to get it to work in Rails 3? Is the workaround described by naveedahmad the way to go? |
Hi,
I tried to use this with rails3.beta.4 and its not compatible.
Is there any work in progress for rails3 compatibleness?
The text was updated successfully, but these errors were encountered: