It appears that the new integrated comments system has a few drawbacks. If anyone else has another take on this, please enlighten me.
- There is no permissions on Comments, so if you have access to Comments, you can see everything, there is also no default filter based on the origin table permissions you have (News, Events, Articles). If a content editor is only assigned to deal with comments from News (e.g. a blog), they still see all the comments, and this will be rather confusing to them. This is especially true when they have been given access to not all News Archives, but only 1 archive, e.g. Design Division News. They will see all comments from all archives and also all the Article, Calendar, FAQ, etc. comments.
- Also, even though you can group by type, or filter by type, there is no nice TL view to show comments by origin. Maybe a new view coded into DC_Table to support parent tables where items are grouped by a parent PID is shown (non-self-referencial tables like tl_calendar and tl_news_archive), just to show the parent as a grouper with a [+] root point.
- Personally if there was a way to display comments directly on an archive like before, or comments on an individual news item, that would be perfect, but TL doesn't yet support a 3-level deep navigation for its buttons (as only do=application&id=23 allows a single parent table as PID and 1 level deep sub-table to be edited). If TL supported this n-level deep DC_Table driver, we could have comments appear by each news item as a button as we can see them there as well.
Bookmarks