WordPress.org
Get WordPress

Make WordPress Core

Opened 8 weeks ago

Closed 8 weeks ago

Last modified 6 weeks ago

#65077 closed defect (bug) (duplicate)

Fix incorrect Settings URL for AI plugin in Connectors banner

Reported by: mukesh27's profile mukesh27 Owned by:
Milestone: Priority: normal
Severity: normal Version: 7.0
Component: AI Keywords: has-patch
Focuses: administration Cc:

Description

The Connectors settings page contains a call-to-action (CTA) banner to install/manage the AI plugin. After the plugin is successfully installed, the button link directs users to an incorrect URL, resulting in a "Sorry, you are not allowed to access this page" error.

Steps to Reproduce:

  1. Log in to the WordPress Admin.
  2. Navigate to Settings > Connectors.
  3. In the banner, click the button to Install the AI plugin.
  4. Once installed, observe the button text updates to: "Control features in the AI plugin".
  5. Click this button.

Actual Results:

  • The button links to: wp-admin/options-general.php?page=ai
  • The user is met with a "Sorry, you are not allowed to access this page" error because that slug does not exist.

Expected Results:

  • The button should link to the correct AI plugin settings page: wp-admin/options-general.php?page=ai-wp-admin

Change History (9)

This ticket was mentioned in ​Slack in #core-ai by mukeshpanchal27. ​View the logs.
8 weeks ago

#2 @ocean90
8 weeks ago

  • Keywords needs-patch removed
  • Milestone 7.0 deleted
  • Resolution set to duplicate
  • Status changed from new to closed

Duplicate of #65073.

This ticket was mentioned in ​PR #11576 on ​WordPress/wordpress-develop by ​@nimeshatxecurify.
8 weeks ago #3

  • Keywords has-patch added

Ensures the correct slug (ai-wp-admin) is used for the AI plugin's administration page link.

Trac ticket: https://core.trac.wordpress.org/ticket/65077

​@audrasjb commented on ​PR #11576:
8 weeks ago #4

This PR don't have any changeset @nimesh-xecurify :)

​@nimeshatxecurify commented on ​PR #11576:
8 weeks ago #5

@audrasjb The wordpress-develop-pr-bot updated the build, which contained the changes. I guess I will need to somehow reference the new build from ​https://github.com/WordPress/gutenberg/pull/77336

https://github.com/user-attachments/assets/2302a289-b160-42f6-ae1c-65630ef341f7

​@audrasjb commented on ​PR #11576:
8 weeks ago #6

I still don't see any changeset in WordPress Core file ;)

​@JeffPaul commented on ​PR #11576:
8 weeks ago #7

A fix for this was already backported and will make it into 7.0 with the next sync: ​https://github.com/WordPress/gutenberg/pull/77336#issuecomment-4245449831

​@khokansardar commented on ​PR #11576:
7 weeks ago #8

Cross-reference for #65073: I opened an alternate PR (#11614) that applies the same behavioral fix but names the new constant AI_PLUGIN_PAGE_SLUG to match the upstream source-of-truth in Gutenberg (WordPress/gutenberg#77336). Using the upstream name means the built files will line up with what core receives at the next Gutenberg sync.

No objection to this PR's approach — linking so a committer can pick whichever naming they prefer; one of the two should be closed as a dup once that decision is made.

​@wildworks commented on ​PR #11576:
6 weeks ago #9

The slug change was made in the Gutenberg repository: ​https://github.com/WordPress/gutenberg/pull/77336

That code will be built in the next sync and automatically applied to core. There is no need to make changes directly to core.

Note: See TracTickets for help on using tickets.