Rearrange config
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
No source file or test is named in the issue. Start by locating the plugin's existing settings page and comment-related options; done means the settings are grouped under the requested sections and their labels and explanatory text match the issue.
Written by the indexing model from the issue text.
Description
Could we rearrange the settings as follows, with section headings? (And some text changes suggested too.)
Display
-
Text for comments label
Enter text to use instead of 'Comments' as section heading. Leave empty to use 'Comments'. -
Allow public to view comments?
This will make comments visible to logged-out users as well as all user roles. -
Which user roles can view comments?
If none are checked, comments will be visible to Super Users only. -
Use threaded comments?
If checked, replies will be displayed indented below the comment.
Submissions
(or something like that.)-
Which user roles can leave comments?
The comment form will be invisible if you do not check one of these options or the following setting. -
Allow public commenting?
Allows everyone, including non-registered users to comment. Using this without Akismet is strongly discouraged. -
WordPress API key for Akismet
We recommend setting up both reCaptcha and Akismet to control abuse of the comment form, if you are not restricting comments to logged-in users. -
You have not entered reCAPTCHA API keys in the security settings. We recommend adding these keys, or the commenting form will be vulnerable to spam.
Moderation
-
User roles whose comments require moderation before publishing
If the role can moderate comments below, that will override the setting here. -
User roles that can moderate comments
Moderation is done in the administrative interface. -
New comment notification emails
An email message will be sent to each address here whenever a new comment is contributed (one email per line). Leave blank if you do not want anyone to be alerted of comments by email.
- Dominant language
- PHP
- Stars
- 4
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from omeka/plugin-Commenting
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
omeka/plugin-Commenting#70 ·
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
omeka/plugin-Commenting#67 ·
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
omeka/plugin-Commenting#64 ·
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
omeka/plugin-Commenting#63 ·
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
omeka/plugin-Commenting#62 ·
All issues in omeka/plugin-Commenting
Similar issues
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
a11y
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
omeka/plugin-ExhibitBuilder#169 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
35-feedback
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day