Did you receive a message, "Maximum execution time of 30 seconds exceeded?" Not anymore. Just Plug'n-Play. It's that easy!
| Code | Message | Location | Category | |
|---|---|---|---|---|
| ERROR | invalid_plugin_name | Plugin name header in your readme is missing or invalid. Please update your readme with a valid plugin name header. Eg: "=== Example Name ===" | — | Plugin Repo |
| ERROR | outdated_tested_upto_header | Tested up to: 5.6 < 6.8. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress. | — | Plugin Repo |
| ERROR | stable_tag_mismatch | Mismatched Stable Tag: 1.0.2 != 1.0.3. Your Stable Tag is meant to be the stable version of your plugin and it needs to be exactly the same with the Version in your main plugin file's header. Any mismatch can prevent users from downloading the correct plugin files from WordPress.org. | — | Plugin Repo |
| WARNING | readme_parser_warnings_too_many_tags | One or more tags were ignored. Please limit your plugin to 5 tags. | — | Plugin Repo |
| WARNING | trademarked_term | The plugin name includes a restricted term. Your plugin name - "WP Maximum Execution Time Exceeded" - contains the restricted term "wp" which can be used , as long as you don't change it to the full name. For example: You can use WP but not WordPress. | — | Plugin Repo |
| WARNING | trademarked_term | The plugin slug includes a restricted term. Your plugin slug - "wp-maximum-execution-time-exceeded" - contains the restricted term "wp" which can be used within the plugin slug, as long as you don't use the full name in the plugin name. For example: You can use WP but not WordPress. | — | Plugin Repo |
| 11/13/2025, 6:03:59 AM | 8s | 99 | 3 | 3 |