New Comments system in TL 2.8

[thyon]

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.

[ga.n]

Hi thyon,

- 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.

if you want to get your comments grouped by a topic please consider taking a look at ZedSeries CommentEverything
basically it allows you to set a "topic" for each comments content element you put in your website ... topic can be related to a known table trough a simple foreign key relationship then you can view this relationship into the backend comments module (will be available together with the other filters)

hope this helps in some way

[leo]

There is no permissions on Comments

This issue will be fixed in version 2.8.1.

[thyon]

Hey leo. kewl for the permissions.

Maybe if there was a way to display the comments in a tree or node filtered view, then we can create buttons on a news item to jump to the comments BE app , with a node filter for that archive or news item? THAT would be useful....

[leo]

You can already filter by "parent" (= parent table) and "pid" (= ID of the parent element). Since the filter settings are stored in the session, you could add a navigation icon to the news module that sets the filter and redirects to the comments module showing only the comments that relate to the selected news item (not the archive unfortunately).

[ga.n]

I wrote an article about how the CommentEverything extension works and an example on how to replace the default faq "comments system".

Once configured you will find a new filter in the backend module that contains all the (faq item|news item|what_you_like)
so you can filter your comments for "Question #1" instead of Parent table: tl_faq and parent id: 1.

For a more detailed example you can take a look at the above mentioned article

http://developmentwithtypolight.wordpre ... verything/