Issue with the comment module after upgrade to 2.11.2

[Rian]

After the upgrade to release 2.11.2 users can no longer leave a comment on a news item. The option does not show in the front end; although backend parameter settings seem to be ok. The issue does not exist for items commented by users prior to the upgrade.

I have also done the following test:

1. Leaving a comment (which is possible for items that already have a comment) works as expected. Approval in the backoffice is possible and the new comment shows in the frontend.
2. Disabling all comment for a news item also removes the option to leave a comment. When I enable the comment, the option to post comment re-appears together with the comment.

Anybody having similar experience with the comment module?

[xchs]

Is this somehow related to #4064?

Did you get an error message if you enable the respective option "Display error messages" in the system settings?

[Rian]

There is no error message, also not with "display error messages" enabled. The comment field is just not there; also nothing that I can select to trigger an error message.

I have this problem with release 2.11.2, it still worked under 2.11.1. The issue that you mention is related to version 2.11.1

[xchs]

Can you reproduce this in the Contao online demo, too?

[Rian]

I only saw this issue after upgrading from version 2.11.1 to version 2.11.2. The online demo site is still on version 2.11.1. Tried it anyway, the issue does not exists. I will retry once the online demo has been upgraded.

[Julian]

I have the same problem. Nobody can comment on the news items after doing a "fresh" install of 2.11.2 for a new site.

[xchs]

The problem occurs if the number of "Comments per page" is set to a value > 0 (cf. news archive settings). That said, for a value of zero (the default value) the form is shown, for all other values the comment form disappears.

[Rian]

Confirmed. Changed the value from 10 to zero and the comment module works again. Thanks.

[Julian]

Thanks! Now it works perfectly again!

Related issue: When this bug occurs, the HTTP status code returned by Contao is 404 on all news items, although the page is displayed correctly. When the max. number of comments is set to zero, the status code is 200 again.

[xchs]

Related issue: When this bug occurs, the HTTP status code returned by Contao is 404 on all news items, although the page is displayed correctly. When the max. number of comments is set to zero, the status code is 200 again.

Yes, that's right. This was added in commit a2edccc:

Send a 404 header and do not index or cache a page if there is a pagination menu and the page parameter is outside the range of existing pages.

[goransabo]

hi!
I need 10 comments on page. How to fix it?
regards

[xchs]

The issue is fixed in commit b5eab90 and will be rolled out with the next bugfix release 2.11.3.