Better handling of existing views that handle comments
tevih - November 6, 2009 - 17:16
| Project: | Node comments |
| Version: | 6.x-2.0-beta1 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Feel free to disregard this as a bug if you think it is more of a feature request. I can't think of a solution myself, but I'm certainly no developer.
There are a lot of modules and installation profiles which automatically create their own views (Open Atrium, Organic Groups, etc.) which use comments. Installing node comments will create tons of errors until those views are update, not to mention the tedium of updating all those views.
Might there be a better way to handle existing views using comments?
#1
erg... nodecomment is wreaking havoc on existing views, and making the required tweaks to work with Nodecomment is proving more difficult than simply tedius! the frustrating thing is that I only want Nodecomments to be working on a content type which previously did not even have comments!
It would be fabulous if core comments module did not have to be disabled in order to specify Nodecomments. Clearly, though, a specific content type couldn't have both Nodecomments and regular comments at the same time.
#2
Core comments does not have to be disabled. They work just fine together and it's set per content type. So just use continue to use comments on the other types.
Michelle
#3
Automatically closed -- issue fixed for 2 weeks with no activity.