If I check the folders on the server, there is no folder pressbooks/assets/src/scripts only pressbooks/assets/dist/scripts/ with no dashborad.js. I was not able to find out which file is calling src/scripts/dashboards.js.
I installed the Pressbooks Plugin and the themes from the github ZIP files.
Hi. A further report. I managed to solve our issues (no js on dashboard pages) by downgrading php8.2 to php8.1 (and reading more carefully). Usually dependencies are minimums, but in the case of Pressbooks, the PHP dependency is an exact version.
With respect to dashboard.js, during trouble-shooting at one point I created the pressbooks/assets/src/scripts path, downloaded the dashboards.js file from the pressbooks github and put it in the path. Once I had my dashboard pages loading with correct JS I tested with and without the dashboard.js file on the src folder path. No discernible difference except the the 404 error in browsers tools.
thanks @twelch – @t.dumm can you share your diagnostics page? Are you also running PHP 8.2? The institutions.js file was added to Pressbooks in 6.13.0 help with a new ‘dashboard checklist’ we added for new networks, so we’re a little puzzled why this error is occurring for you now rather than, say, 6 months ago?
I did the same as @twelch: I created a folders and placed the missing dshborad.js file there. Afterwards the error was gone. I suspect that the distribution should also inlcude the src/scripts folder or a different dashboard.j should be referenced.
PHP Version: 8.1.27
MySQL Version: 8.0.36
Webserver Info: Apache/2.4.58 (Ubuntu)
PHP Configuration
Memory Limit: 256M
Upload Max Size: 500M
Post Max Size: 256M
Upload Max Filesize: 500M
Time Limit: 300
Max Input Vars: 1000
URL-aware fopen: On (1)
Display Errors: On (1)
PHP Extensions
OPcache: Zend
XDebug: Disabled
cURL: Not Supported
imagick: Not Installed
xsl: Installed
Thanks – looking into it further. It looks like the original commit didn’t add the file to the webpack build configuration, so the file isn’t being included in the /dist folder as expected. We will try to fix this for our next release.