Carousel: Master kill switch for comments

[kraftbj]

The Carousel window allows comments, that are associated with the attachment post, based on each media item's Discussion settings.

Individual attachments will have comments enabled based on Core's generic option for opening comments on new articles. To disable for an individual media item, users need to visit the Media Library, choose a particular image, click the "Edit More Details" link, (enable the Discussions metabox via Screen Options), uncheck Comments and Save.

Idea: Should we add an option that will kill the comment form on all carousel modals? Or is there a better way to handle this ourselves? Or a Core problem?

ref: 2443324-t

[jeherve]

Related:
http://jetpack.me/2013/05/01/remove-comments-carousel/

[jeherve]

Closing this for now because of the lack of activity on this. We can always reopen in the future if needed.

[htdat]

Reopening this as this user is requesting it 1744463-zen:

I would like to encourage you to build in a switch to turn off the comment
function below the carousel (Gallerie).
There are so many reasons against this comment function.

1. It dosn't work in the most cases.
2. Ugly and disturbing
3. Pics would be more centered.
4. I don't want any comment to my pics :-)

I have a lot of friends and colleagues using Jetpack and nearly each of them
using the carousel is complaining about the comment function.
I know 4 persons not using Jetpack at all anymore because of problems with the
some other 'lighboxes' and they don't want to have also these comment function.

[jeherve]

It dosn't work in the most cases.

I assume this is the issue reported in #11148; it will be fixed in the next release.

Ugly and disturbing

It would be good to find out more here; the comment feature is not displayed in the modal by default, you have to scroll down to see it. Are they referring to the same comment feature?

Pics would be more centered.

The comment form does not have an impact on the alignment of the images in the Carousel modal.

Could you ask them for more details about this?

[htdat]

Thanks Jeremy. I am asking this user in 1744463-zen.

[tbradsha]

Requested here: 11166400-hc.

[stale]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[zdenys]

Another where it would have been helpful to avoid the CSS solution 16997128-hc

[stale]

This issue has been marked as stale. This happened because:

• It has been inactive in the past 6 months.
• It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.

[jeherve]

This was implemented in #15436.