Skip to content

PRO-1039: Replace remaining 'Ignore' terminology with 'Dismiss' - #1782

Merged
SteveJonesDev merged 2 commits into
developfrom
steve/pro-1039-update-terminology-in-rule-descriptions-replace-ignore-with
Jun 22, 2026
Merged

PRO-1039: Replace remaining 'Ignore' terminology with 'Dismiss'#1782
SteveJonesDev merged 2 commits into
developfrom
steve/pro-1039-update-terminology-in-rule-descriptions-replace-ignore-with

Conversation

@SteveJonesDev

@SteveJonesDev SteveJonesDev commented Jun 22, 2026

Copy link
Copy Markdown
Member

Summary

  • Follow-up to the rule-class wording fix already on develop (PRO-1039 scope item: "all other files and components where 'Ignore' terminology appears").
  • Updates the remaining user-facing strings still saying "Ignore" to "Dismiss":
    • includes/options-page.php — settings field label and descriptions
    • admin/class-admin-notices.php — Black Friday promo notice copy
    • admin/class-ajax.php — AJAX error message (4 occurrences)
    • admin/site-health/class-pro.php — Site Health info labels
    • src/frontendHighlighterApp/index.js — highlighter badge label and summary count text

Test plan

  • php -l on all changed PHP files
  • node --check on the changed JS file
  • Verified no remaining translatable strings contain "Ignore"/"ignore" outside of internal field/variable names (e.g. ignore_global, ignore_user_roles), which are out of scope per Linear discussion
  • Manually verify settings page, Black Friday notice, and frontend highlighter render correctly with new copy

Closes PRO-1039

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Style
    • Updated terminology throughout the user interface to improve consistency and clarity by replacing “ignore” with “dismiss” across user-facing elements, including promotional notices, AJAX error messaging, permissions labels, site health indicators, options page descriptions, and issue status badges/counts in the admin and frontend.

Updates user-facing strings in the settings page, admin notices, AJAX
error messages, site health info, and frontend highlighter to use the
current "Dismiss" terminology instead of the legacy "Ignore" wording.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 22, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 000410ed-b64f-4c99-94de-950e55a38468

📥 Commits

Reviewing files that changed from the base of the PR and between 4ee77c5 and e068cef.

📒 Files selected for processing (3)
  • admin/class-admin-notices.php
  • admin/class-ajax.php
  • admin/site-health/class-pro.php
✅ Files skipped from review due to trivial changes (2)
  • admin/class-admin-notices.php
  • admin/site-health/class-pro.php
🚧 Files skipped from review as they are similar to previous changes (1)
  • admin/class-ajax.php

📝 Walkthrough

Walkthrough

Across five files, the PR replaces user-facing "ignore/ignored" terminology with "dismiss/dismissed". Changes affect the Black Friday admin notice copy, four WP_Error message strings in the Ajax::add_ignore() handler, two Site Health field labels, three options-page labels and help texts, and two frontend highlighter UI strings (type badge and issue count).

Changes

Ignore → Dismiss terminology rename

Layer / File(s) Summary
PHP admin and options page label updates
admin/class-admin-notices.php, admin/site-health/class-pro.php, includes/options-page.php
Updates displayed field labels, help text, and the Black Friday notice copy to replace "ignore/Ignore" with "dismiss/Dismiss". No option keys, control flow, or stored values change.
AJAX error message wording update
admin/class-ajax.php
Changes four WP_Error('-2', ...) message strings inside Ajax::add_ignore() from "No ignore data to return" to "No dismissal data to return" across all failure branches.
Frontend highlighter badge and count label updates
src/frontendHighlighterApp/index.js
Updates the type badge text for rule_type === 'ignored' and the pluralized issue count label from "Ignored" to "Dismissed".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

Poem

🐇 A rabbit hopped through the code one day,
And found "ignored" had lost its way.
With a twitch of the nose and a quick little hop,
"Dismissed!" now rings from bottom to top.
No logs to ignore, no warnings to shun—
Just "dismiss" all around, and the cleanup is done! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: replacing 'Ignore' terminology with 'Dismiss' throughout user-facing strings across multiple files.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch steve/pro-1039-update-terminology-in-rule-descriptions-replace-ignore-with

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the terminology in the Accessibility Checker plugin, replacing variations of 'ignore' with 'dismiss' across admin notices, AJAX handlers, settings, and frontend scripts. The review feedback points out several grammatical issues introduced by this direct replacement, suggesting the use of the noun forms 'dismissal' or 'dismissals' instead of 'dismiss' or 'dismisses' in phrases like 'dismissal logs', 'No dismissal data to return', and 'Dismissals DB Table Count' to ensure natural and correct English phrasing.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread admin/class-admin-notices.php Outdated
$message = '<div class="edac_black_friday_notice notice notice-info is-dismissible">';
$message .= '<p><strong>' . esc_html__( '🎉 Black Friday special! 🎉', 'accessibility-checker' ) . '</strong><br />';
$message .= esc_html__( 'Upgrade to a paid version of Accessibility Checker from November 24th to December 3rd and get 30% off! Full site scanning, site-wide open issues report, ignore logs, and more.', 'accessibility-checker' ) . '<br />';
$message .= esc_html__( 'Upgrade to a paid version of Accessibility Checker from November 24th to December 3rd and get 30% off! Full site scanning, site-wide open issues report, dismiss logs, and more.', 'accessibility-checker' ) . '<br />';

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase 'dismiss logs' is grammatically awkward. Since 'dismiss' is a verb, using the noun form 'dismissal' (i.e., 'dismissal logs') is more grammatically correct and natural in English.

        $message .= esc_html__( 'Upgrade to a paid version of Accessibility Checker from November 24th to December 3rd and get 30% off! Full site scanning, site-wide open issues report, dismissal logs, and more.', 'accessibility-checker' ) . '<br />';

Comment thread admin/class-ajax.php Outdated

if ( ! $first_id || ! $valid_table ) {
wp_send_json_error( new \WP_Error( '-2', __( 'No ignore data to return', 'accessibility-checker' ) ) );
wp_send_json_error( new \WP_Error( '-2', __( 'No dismiss data to return', 'accessibility-checker' ) ) );

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase 'No dismiss data to return' is grammatically incorrect. Using the noun form 'dismissal' (i.e., 'No dismissal data to return') is grammatically correct and matches standard English usage.

            wp_send_json_error( new \WP_Error( '-2', __( 'No dismissal data to return', 'accessibility-checker' ) ) );

Comment thread admin/class-ajax.php Outdated
$batch_object = $wpdb->get_var( $wpdb->prepare( 'SELECT object FROM %i WHERE id = %d', $valid_table, $first_id ) );
if ( ! $batch_object ) {
wp_send_json_error( new \WP_Error( '-2', __( 'No ignore data to return', 'accessibility-checker' ) ) );
wp_send_json_error( new \WP_Error( '-2', __( 'No dismiss data to return', 'accessibility-checker' ) ) );

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase 'No dismiss data to return' is grammatically incorrect. Using the noun form 'dismissal' (i.e., 'No dismissal data to return') is grammatically correct and matches standard English usage.

                wp_send_json_error( new \WP_Error( '-2', __( 'No dismissal data to return', 'accessibility-checker' ) ) );

Comment thread admin/class-ajax.php Outdated

if ( empty( $affected_post_ids ) ) {
wp_send_json_error( new \WP_Error( '-2', __( 'No ignore data to return', 'accessibility-checker' ) ) );
wp_send_json_error( new \WP_Error( '-2', __( 'No dismiss data to return', 'accessibility-checker' ) ) );

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase 'No dismiss data to return' is grammatically incorrect. Using the noun form 'dismissal' (i.e., 'No dismissal data to return') is grammatically correct and matches standard English usage.

            wp_send_json_error( new \WP_Error( '-2', __( 'No dismissal data to return', 'accessibility-checker' ) ) );

Comment thread admin/class-ajax.php Outdated

if ( ! $data ) {
wp_send_json_error( new \WP_Error( '-2', __( 'No ignore data to return', 'accessibility-checker' ) ) );
wp_send_json_error( new \WP_Error( '-2', __( 'No dismiss data to return', 'accessibility-checker' ) ) );

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase 'No dismiss data to return' is grammatically incorrect. Using the noun form 'dismissal' (i.e., 'No dismissal data to return') is grammatically correct and matches standard English usage.

            wp_send_json_error( new \WP_Error( '-2', __( 'No dismissal data to return', 'accessibility-checker' ) ) );

Comment thread admin/site-health/class-pro.php Outdated
],
'ignores_db_table_count' => [
'label' => __( 'Ignores DB Table Count', 'accessibility-checker' ),
'label' => __( 'Dismisses DB Table Count', 'accessibility-checker' ),

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The phrase 'Dismisses DB Table Count' is grammatically incorrect because 'Dismisses' is a verb form. The plural noun form 'Dismissals' (i.e., 'Dismissals DB Table Count') should be used instead to match the original 'Ignores DB Table Count'.

                    'label' => __( 'Dismissals DB Table Count', 'accessibility-checker' ),

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4ee77c55e1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread includes/options-page.php
add_settings_field(
'edacp_ignore_user_roles',
__( 'Ignore Permissions', 'accessibility-checker' ),
__( 'Dismiss Permissions', 'accessibility-checker' ),

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Regenerate catalogs for renamed UI strings

When a bundled non-English locale is active, this renamed msgid (and the other renamed strings in this commit) is no longer translatable because the checked-in catalogs were not regenerated: languages/accessibility-checker.pot/.po still contain the old Ignore Permissions, No ignore data to return, Ignored, and %d Ignored entries, and the frontend-highlighter JSON still lacks the new Dismissed/%d Dismissed keys. Since WordPress looks up translations by the exact English msgid, these labels fall back to English after this change; please update the POT/PO/MO/JSON artifacts with the source changes.

Useful? React with 👍 / 👎.

Use the noun form "dismissal" instead of the verb "dismiss"/"dismisses"
where grammatically required, per Gemini Code Assist review feedback.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@SteveJonesDev

Copy link
Copy Markdown
Member Author

Addressed the Gemini Code Assist grammar feedback in e068cef — switched to the noun form "dismissal"/"dismissals" where "dismiss"/"dismisses" was grammatically wrong:

  • admin/class-admin-notices.php — "dismiss logs" → "dismissal logs"
  • admin/class-ajax.php — "No dismiss data to return" → "No dismissal data to return" (4 occurrences)
  • admin/site-health/class-pro.php — "Dismisses DB Table Count" → "Dismissals DB Table Count"

Re the Codex comment on regenerating POT/PO/MO/JSON catalogs: this repo regenerates languages/accessibility-checker.pot via the dedicated make-pot.yml workflow, which only runs on automatic_translations_*/tm_edits_* branches or manual dispatch — not on regular feature PRs. Hand-editing the compiled .mo/.json catalogs here would be outside that process and risks corrupting them, so I'm leaving catalog regeneration to that workflow rather than doing it manually in this PR.

@SteveJonesDev
SteveJonesDev merged commit 6286243 into develop Jun 22, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants