WYSIWYG displaying error

Hello there,

I have an issue after installing last update Release v6.41.0 · pressbooks/pressbooks · GitHub , the pressbooks-6.41.0.zip (i was previously using 6.25.1 version) with the WYSIWYG :
there’s an alert saying '“Failed to load plugin url: …/wp-content/plugins/pressbooks/assets/src/scripts/XXX.js” (XXX being different script name, such as anchor.js or textboxes.js or applyclass.js) on all WYSIWYG.

But there is no src/ folder in the assests/ one. And in the dist/scripts/ one, i have a couple of scripts but none of the ones listed in the errors.

I probably have done something wrong in the updating process (i’m not using bedrock) but i can’t figure out what…

It’s not preventing to use and submit forms but i would like to fix the issue :slight_smile:

My System Information:

WordPress Configuration

Network Type: Subdirectory
Version: 6.9.1
Language: en_GB
WP_ENV: Not set
WP_DEBUG: Enabled
Memory Limit: 64M

Pressbooks Configuration

Version: 6.41.0
Book Theme: McLuhan
Book Theme Version: 2.34.0
Root Theme: Aldine
Root Theme Version: 1.25.2

Pressbooks Dependencies

Epubcheck: Not Installed
xmllint: Not Installed
PrinceXML: Not Installed
Saxon-HE: Not Installed

Must-Use Plugins

hm-autoloader.php: n/a

Server Configuration

PHP Version: 8.3.30
MySQL Version: 10.6.27
Webserver Info: Apache/2.4.66 (Debian)

PHP Configuration

Memory Limit: 256M
Upload Max Size: 2M
Post Max Size: 8M
Upload Max Filesize: 2M
Time Limit: 30
Max Input Vars: 1000
URL-aware fopen: On (1)
Display Errors: On (1)

PHP Extensions

OPcache: Zend
XDebug: Disabled
cURL: Supported
cURL Version: 8.14.1
imagick: Installed
xsl: Installed

Let me know if I can provide further information.

Thanks in advance,
Charlotte

Hello, recently we updated our frontend build tools and I think we made a little mistake while building our production assets we will submit a fix for this ASAP.

Thank you for reporting

@RmbxCh we just released Release v6.42.0 · pressbooks/pressbooks · GitHub a new version that fixes that issue, sorry for the inconvenience.

Hi @arzola ,

No more error displayed, Thank you for addressing this so promptly!