Skip to content

Connectors: Replace plugin.slug with plugin.file#11400

Open
jorgefilipecosta wants to merge 2 commits intoWordPress:trunkfrom
jorgefilipecosta:update/connector-plugin-file
Open

Connectors: Replace plugin.slug with plugin.file#11400
jorgefilipecosta wants to merge 2 commits intoWordPress:trunkfrom
jorgefilipecosta:update/connector-plugin-file

Conversation

@jorgefilipecosta
Copy link
Copy Markdown
Member

Summary

  • Replace plugin.slug with plugin.file (the full plugin file path, e.g. akismet/akismet.php) in connector registrations
  • Simplify script module data: remove get_plugins() slug-to-file map, use file_exists() and is_plugin_active() directly
  • Add isInstalled to the frontend plugin data
  • Update PHPDoc for plugin type across registry and public API functions

Test plan

  • Verify connectors page loads and shows correct plugin status
  • Verify install and activate flows still work for AI provider plugins

…ation

Use the plugin's main file path (e.g. 'akismet/akismet.php') instead of
just the slug. This lets the script module data function use file_exists()
and is_plugin_active() directly, removing the get_plugins() slug-to-file
map. The frontend derives the slug from the file path when needed.
@github-actions
Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props jorgefilipecosta.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

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.

1 participant