wordpress-mobile / wordpress-mobile/WordPress-Android
Comments falsely flagged as "closed" on Jetpack app if not opting in for Jetpack Comments
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 3.2k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 69
Description
Expected behavior
It should either be possible to reply to comments from the app if they're enabled on a site, or there should be another way of observing comments are open.
Actual behavior
In 7834708-zen, a user clued us into the fact that it's not possible to reply to comments via the app if Jetpack Comments is not enabled. Furthermore, a misleading "Comments are closed" message displays in this instance, even though regular comments are open on the user's site.
There is an iOS equivalent to this issue open at https://github.com/wordpress-mobile/WordPress-iOS/issues/21737.
Steps to reproduce the behavior
- With a Jetpack-connected site, navigate to Settings → Discussion and toggle the Let visitors use a WordPress.com or Facebook account to comment. option off.
- Ensure comments are otherwise enabled.
- Publish posts.
- View the published posts in the app and verify you see a "Comments are closed" message at the bottom.
Tested on Pixel 6, Android 14, JPAndroid / WPAndroid 24.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue from Settings → Discussion on a Jetpack-connected site, then inspect the published-post comments entry point in the Android app. Confirm the app distinguishes disabled Jetpack Comments from regular comments being open, and verify that the misleading “Comments are closed” message no longer appears when regular comments are enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100