#60867 closed defect (bug) (invalid)
Manage Theme Fonts, Javascript error
Reported by: | franzstephan | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Themes | Keywords: | reporter-feedback |
Focuses: | javascript | Cc: |
Description
Bug Report
Description
Describe the bug.
Javascript error in Dashboard - Appearance - Manage Theme Fonts, while testing WP 6.5 RC4.
Environment
- WordPress: 6.5-RC4
- PHP: 8.0.30-dev
- Server: PHP.wasm
- Database: WP_SQLite_Translator (Server: 5.5 / Client: 3.40.1)
- Browser: Chrome 122.0.0.0
- OS: Could not determine
- Theme: Twenty Twenty-Four 1.1
- MU Plugins:
- 0-playground.php
- 0-sqlite.php
- WordPress WXZ Exporter 0.1
- Plugins:
- Create Block Theme 1.13.8
- Debug Bar 1.1.6
- Health Check & Troubleshooting 1.7.0
- Query Monitor 3.15.0
- Test Reports 1.1.0
- User Switching 1.7.3
- WordPress Importer Git loader 0.8.2
Steps to Reproduce
- 🐞 Bug occurs.
Expected Results
- ✅ What should happen.
Actual Results
- ❌ What actually happened.
Visit Dashboard - Appearance - Manage Theme Fonts. Click the Reset Button.
You get the following Debug Alert for Javascript:
Uncaught TypeError: o is not a function
https://playground.wordpress.net/scope:0.3815221276059668/wp-includes/js/dist/vendor/react-dom.min.js?ver=18.2.0 line 10
Additional Notes
- Any additional details worth mentioning.
Ran the test on Playground.wordpress.net
Supplemental Artifacts
Add Inline:
or
Add as Attachment
Change History (2)
Note: See
TracTickets for help on using
tickets.
Hi @franzstephan and welcome to WordPress Trac.
Thank you for taking the time to report this issue.
The menu item and screen that you are describing, Dashboard - Appearance - Manage Theme Fonts,
is part of the Create block theme plugin.
There may be conflicts between WordPress 6.5 and the plugin, but the problem needs to be reported in the GitHub repository for Create block theme:
https://github.com/WordPress/create-block-theme/issues
Because of this, I am closing the issue.
(Please note that there are plans to replace this screen in the plugin in a future version, so the contributors may decide to not fix this issue short term.)