Skip to content

Conversation

@edluis97
Copy link

@edluis97 edluis97 commented Dec 4, 2025

…wpmy/public_html/wp-content/plugins/wordpress-seo/inc/options/class-wpseo-options.php on line 579 - free plan only

Context

Summary

This PR can be summarized in the following changelog entry:

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:

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:

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.
  • I have ran grunt build:images and commited the results, if my PR introduces new images or SVGs.

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 #

…pmy/public_html/wp-content/plugins/wordpress-seo/inc/options/class-wpseo-options.php on line 579 - free plan only
@enricobattocchi
Copy link
Member

@edluis97 can you give instructions about how to reproduce the issue you are experiencing?

@edluis97
Copy link
Author

edluis97 commented Dec 4, 2025

I'll be honest with you, I'm fairly inexperienced with Yoast, having started using only about a few days ago (and WP too for that matter).

However, since I wanted to display the errors, in order to check my own plugin, I changed my wp-config.php.
Commented define( 'WP_DEBUG', false );
And added

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', true );
define( 'WP_DEBUG_LOG', true );
@ini_set( 'display_errors', 1 );

I'm using the free version of Yoast, as of now, at least.
I noticed within the plugins list page it was displaying the following warnings that were also stored to my debug.log:

[04-Dec-2025 05:46:35 UTC] PHP Warning:  Undefined array key "wpseo_premium" in MY_WEBSITES_PATH/wp-content/plugins/wordpress-seo/inc/options/class-wpseo-options.php on line 579
[04-Dec-2025 05:46:35 UTC] PHP Warning:  foreach() argument must be of type array|object, null given in MY_WEBSITES_PATH/wp-content/plugins/wordpress-seo/inc/options/class-wpseo-options.php on line 583

I installed yoast through the WordPress repo, btw. My website's running PHP 8.3.26.

Hope this info is useful. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants