Skip to content

Enable back AI Optimize buttons in Classic editor#22464

Merged
marinakoleva merged 13 commits intotrunkfrom
feature/improve-ai-optimize-in-classic-editor
Jul 29, 2025
Merged

Enable back AI Optimize buttons in Classic editor#22464
marinakoleva merged 13 commits intotrunkfrom
feature/improve-ai-optimize-in-classic-editor

Conversation

@agnieszkaszuba
Copy link
Copy Markdown
Contributor

@agnieszkaszuba agnieszkaszuba commented Jul 29, 2025

Context

Summary

This PR can be summarized in the following changelog entry:

  • Adds back the AI Optimize buttons in Classic editor.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • Use test instructions from the PRs linked above.

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

UI changes

  • This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes #

FAMarfuaty and others added 13 commits June 26, 2025 13:59
…timize-tinymce---improve-the-implementation-for-classic-editor-without-using-class-assignment
…e-the-implementation-for-classic-editor-without-using-class-assignment

Enable back AI buttons in Classic editor
…lassic-editor' into 4687-ai-optimize-tinymce---adapt-the-implementation-to-the-new-structure
…-the-implementation-to-the-new-structure

Removes `defaultProps` in AI button
@agnieszkaszuba agnieszkaszuba added the changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog label Jul 29, 2025
@agnieszkaszuba agnieszkaszuba changed the title Feature/improve ai optimize in classic editor Add changes needed to improve AI Optimize in Classic editor Jul 29, 2025
@agnieszkaszuba agnieszkaszuba changed the title Add changes needed to improve AI Optimize in Classic editor Enable back AI Optimize buttons in Classic editor Jul 29, 2025
@agnieszkaszuba agnieszkaszuba added changelog: other Needs to be included in the 'Other' category in the changelog changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog and removed changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog changelog: other Needs to be included in the 'Other' category in the changelog labels Jul 29, 2025
@agnieszkaszuba agnieszkaszuba added this to the 25.7 milestone Jul 29, 2025
@agnieszkaszuba agnieszkaszuba added the innovation Innovative issue. Relating to performance, memory or data-flow. label Jul 29, 2025
@coveralls
Copy link
Copy Markdown

Pull Request Test Coverage Report for Build ec8c8b0565b9d194f832d7914942881cf71fe5eb

Details

  • 2 of 2 (100.0%) changed or added relevant lines in 2 files are covered.
  • 2 unchanged lines in 2 files lost coverage.
  • Overall coverage decreased (-0.003%) to 52.645%

Files with Coverage Reduction New Missed Lines %
packages/js/src/components/contentAnalysis/ReadabilityAnalysis.js 1 0.0%
packages/js/src/components/contentAnalysis/SeoAnalysis.js 1 0.0%
Totals Coverage Status
Change from base Build 9f80b043a8a5ad7e73d00dffcb7af7c437bf44b5: -0.003%
Covered Lines: 31017
Relevant Lines: 59685

💛 - Coveralls

@agnieszkaszuba agnieszkaszuba added changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog and removed changelog: enhancement Needs to be included in the 'Enhancements' category in the changelog labels Jul 29, 2025
@marinakoleva marinakoleva merged commit 69147ce into trunk Jul 29, 2025
51 of 52 checks passed
@marinakoleva marinakoleva deleted the feature/improve-ai-optimize-in-classic-editor branch July 29, 2025 10:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog innovation Innovative issue. Relating to performance, memory or data-flow.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants