Disable nag notices
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 52/100
Research direction
Start with the main plugin file and locate its require() calls and the DISABLE_NAG_NOTICES constant check. Confirm when the constant is defined and how the plugin loads its files. Done means the require() calls are skipped when nag notices are disabled while normal plugin loading still works.
Written by the indexing model from the issue text.
Description
Suggestion: Wrap the require() calls in the main plugin file in the check for the DISABLE_NAG_NOTICES constant. This saves the file read time.
- Dominant language
- PHP
- Stars
- 26
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 littlebizzy/force-https
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
littlebizzy/force-https#11 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
littlebizzy/force-https#10 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
All issues in littlebizzy/force-https
Similar issues
-
status/awaiting_triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
WordPress/plugin-check#1486 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
az-digital/az_quickstart#6019 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
grokability/snipe-it#19688 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100