The basic idea behind this change is to allow the implementation of comments for downloads, articles,... in the future. To achieve this, the structure of the table fs2_news_comments has been changed by adding a new varchar field ("content_type") which keeps track of whether a comment is for news, downloads or articles (or whatever might be added in future releases).
The table fs2_news_comments has been renamed to fs2_comments and the news_id field has been renamed to content_id to reflect the generalised nature of the comments stored within.
I've tested the changes and they seem to work as expected, however the tests weren't very extensive.
The basic idea behind this change is to allow the implementation of comments for downloads, articles,... in the future. To achieve this, the structure of the table fs2_news_comments has been changed by adding a new varchar field ("content_type") which keeps track of whether a comment is for news, downloads or articles (or whatever might be added in future releases).
The table fs2_news_comments has been renamed to fs2_comments and the news_id field has been renamed to content_id to reflect the generalised nature of the comments stored within.
I've tested the changes and they seem to work as expected, however the tests weren't very extensive.