AcrossAI Abilities Manager<\/strong> in the WordPress admin menu.<\/li>\n<\/ol>\n\nAdd-ons:<\/strong><\/p>\n\n\n- Go to AcrossAI Abilities Manager \u2192 Add-ons<\/strong> to browse available add-ons.<\/li>\n
- Free add-ons can be installed with one click via the standard WordPress plugin installer.<\/li>\n
- Paid add-ons require connecting your account \u2014 click Buy<\/strong> on any paid add-on to begin.<\/li>\n<\/ol>\n\n\n
\nDoes this plugin support Multisite?<\/h3><\/dt>\nNo. This plugin has not been tested on WordPress Multisite installations.<\/p><\/dd>\n
Does this plugin modify the WordPress ability registry?<\/h3><\/dt>\nNo. The plugin stores only overrides \u2014 fields that differ from the registry defaults. The ability registry itself (wp_get_ability()<\/code>) is never modified.<\/p><\/dd>\nWhat happens when I reset an override?<\/h3><\/dt>\nThe override row is deleted from the database. The ability will inherit its values from the registry again.<\/p><\/dd>\n
What is the Ability Library?<\/h3><\/dt>\nThe Library page lets you enable or disable ability groups registered by add-on plugins. Each group shows an ON\/OFF master toggle and an All\/Specific mode selector. In Specific mode, individual ability slots can be toggled independently.<\/p><\/dd>\n
What is the MCP Adapter integration?<\/h3><\/dt>\nIf the MCP Adapter plugin is active on your site, AcrossAI Abilities Manager will display the list of registered MCP servers in the ability edit panel. This is entirely optional \u2014 the plugin works without the MCP Adapter.<\/p><\/dd>\n
Does this plugin make external HTTP requests?<\/h3><\/dt>\nOnly when you explicitly interact with the Add-ons page to connect your account or purchase a paid add-on. In that case, data is sent to Freemius (see \"External Services\"). No external requests are made otherwise.<\/p><\/dd>\n\n<\/dl>\n\n\n
0.0.3<\/h4>\n\n\n- Fix: plugin now activates on installs from WordPress.org.<\/strong> The 0.0.2 release ZIP shipped without the Composer autoloader (
vendor\/autoload_packages.php<\/code>) because the WordPress.org deploy workflow did not run composer install<\/code> before uploading. Users installing 0.0.2 from the WordPress.org plugin directory saw the plugin activation guard trigger: \"AcrossAI Abilities Manager cannot activate: the Composer autoloader is missing\u2026\"<\/em>. The 0.0.3 release ZIP includes the full production autoloader; no other code changes. If you already installed 0.0.2 and hit the activation error, delete the plugin folder and reinstall 0.0.3.<\/li>\n<\/ul>\n\n0.0.2<\/h4>\n\n\n- Composer dependency refresh<\/strong> \u2014
wpb-access-control<\/code> bumped to v2.0.0 (per-consumer database tables); acrossai-co\/main-menu<\/code> bumped to v0.0.10 (now bundles the Add-ons page and includes the JS-side rebrand-sync fix that restores Install \/ Activate \/ Deactivate button behavior). The standalone acrossai-co\/addons-page<\/code> package has been removed from direct dependencies; the same AcrossAI_Addon\\AddonsPage<\/code> class now ships from the main-menu<\/code> package.<\/li>\n- Per-consumer access-control storage<\/strong> \u2014 this plugin now owns its own
{prefix}abilities_access_control<\/code> database table, keeping its rules fully isolated from any other plugin embedding the same access-control library. The dedicated table is created automatically on plugin activation.<\/li>\n- Add-ons submenu URL changed<\/strong> \u2014 the Add-ons page slug is now
acrossai-addons<\/code> (was wpb-addons<\/code>). Any bookmarks or external links pointing at wp-admin\/admin.php?page=wpb-addons<\/code> should be updated to wp-admin\/admin.php?page=acrossai-addons<\/code>. The submenu location and behavior are otherwise unchanged.<\/li>\n- BREAKING \u2014 Access Control rules from earlier releases are NOT migrated.<\/strong> If you previously configured Access Control rules on any ability, those rules were stored in the shared
{prefix}wpb_access_control<\/code> table and are no longer read<\/strong> by this release. After upgrading, please audit every ability's Access Control panel and reconfigure any rules that were previously in place. The legacy table is left on disk (in case you need to reference the prior configuration) and can be dropped manually by a database administrator if desired: DROP TABLE {prefix}wpb_access_control;<\/code> and DELETE FROM {prefix}options WHERE option_name = 'wpb_access_control_db_version';<\/code>.<\/li>\n- BREAKING \u2014 Ability execution logging removed.<\/strong> The dedicated Logs admin page, the log-retention Settings field, the
{prefix}acrossai_ability_logs<\/code> database table, and the \/wp-json\/acrossai-abilities-log\/v1\/logger\/logs<\/code> REST endpoint are all removed. If you rely on ability-execution logging for security monitoring or auditing, install a compatible logging plugin or hook wp_after_execute_ability<\/code> directly in your own consumer code \u2014 the upstream ability-execution events remain available. Bookmarks to wp-admin\/admin.php?page=acrossai-abilities-logs<\/code> receive the standard \"page does not exist\" response. External integrations polling the removed REST endpoint receive 404. On existing installs, the legacy logs table and its schema-version option are orphaned; opt into the \"delete all data on uninstall\" setting to drop them cleanly, or run manually: DROP TABLE {prefix}acrossai_ability_logs;<\/code> and DELETE FROM {prefix}options WHERE option_name IN ('acrossai_abilities_log_retention_days', 'acrossai_ability_logs_db_version');<\/code>.<\/li>\n<\/ul>\n\n0.0.1<\/h4>\n\n\n- Initial release.<\/li>\n
- Sitewide Ability Management: browse, toggle, edit, reset, bulk-action.<\/li>\n
- Ability Library: enable\/disable add-on ability groups with All\/Specific mode controls.<\/li>\n
- Add-ons page powered by wpb-addons-page with Freemius integration.<\/li>\n
- MCP server listing via MCP Adapter integration.<\/li>\n<\/ul>","raw_excerpt":"Manage every WordPress ability registered on your site \u2014 view, search, override, and bulk-control ability metadata from a single admin page.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/311005","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=311005"}],"author":[{"embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/raftaar1191"}],"wp:attachment":[{"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=311005"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=311005"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=311005"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=311005"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=311005"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/cn.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=311005"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}