Make WordPress Core

Opened 6 weeks ago

Closed 4 weeks ago

#64746 closed defect (bug) (fixed)

Connectors - Something went wrong!

Reported by: stefanofp's profile stefanofp Owned by:
Milestone: 7.0 Priority: normal
Severity: critical Version: trunk
Component: Editor Keywords:
Focuses: Cc:

Description

Hello,
after updating from WordPress 7.0 beta 1 to beta 2, when I go into the connectors tab appears an error in the page.

This is the message
Failed to resolve module specifier "@wordpress/connectors". Relative references must start with either "/", "./", or "../".

From Query Monitor this is the error

Function WP_Script_Modules::register was called incorrectly. The script module with the ID "wp/routes/connectors-home/content" was enqueued with dependencies that are not registered: @wordpress/connectors. (This message was added in version 6.9.1.)

I also added a screenshot

https://pic.li/d3kQ

Attachments (1)

Error-connectors.jpg (163.0 KB) - added by stefanofp 6 weeks ago.
Errors into the connectors page

Download all attachments as: .zip

Change History (7)

@stefanofp
6 weeks ago

Errors into the connectors page

#1 @mukesh27
6 weeks ago

  • Version set to trunk

#2 @westonruter
6 weeks ago

@stefanofp Thanks for opening a ticket. Do you have any plugins active? What theme is active?

#3 @stefanofp
6 weeks ago

Hi @westonruter,
I checked and I found the route of the cause, into my local environment there was enabled the Gutenberg plugin version 22.6.0. In fact when I disabled it the error message disappear and all works well.

#4 @westonruter
6 weeks ago

  • Component changed from AI to Editor
  • Milestone changed from Awaiting Review to 7.0

Thanks for that. So there appears to be a conflict with the latest beta and the latest Gutenberg, at least for you.

#5 @justlevine
6 weeks ago

I'm not entirely sure what made it into 22.6 specifically, but I'm assuming this will be resolved by https://github.com/WordPress/wordpress-develop/pull/11080 or a different sync PR. cc @gziolo just in case.

#6 @wildworks
4 weeks ago

  • Resolution set to fixed
  • Status changed from new to closed

I think this problem doesn't occour now. See this discussion on Slack: https://wordpress.slack.com/archives/C02RQBWTW/p1772720658821199

Please feel free to comment if I've missed anything.

Note: See TracTickets for help on using tickets.