Missing jquery ui widget.min.js

Hi all,

Justed checked the backups, and going from the timestamp it’s indeed caused by the WP upgrade.
I’ll make a separate post for that…

Hi @tsteur ,

Thanks for the feedback!
I doublechecked the official .zip download, but the file also seems to be missing there.
Then filed a bug on track https://core.trac.wordpress.org/ticket/52259.

Feedback of the wordpress team is that these files have indeed been removed:

The latest version of jQuery UI does not have separate files for these two components, they are part of jQuery UI Core, so just enqueuing jquery-ui-core will cover all 3 of them.

There is a back-compat entry for them as well, so this change shouldn’t cause any breaking changes if plugins are using WordPress’ script enqueue system (wp_enqueue_script) properly, so I would reach out to the plugin in question if their plugin isn’t working right now. A quick cursory look shows that the yare not doing this, so this is a plugin issue 🙂

Hi @tsteur,

Thanks for the quick follow-up.
I’ve tried to test, but I’m only getting more confused :p

On my production system, the dashboard page is not loading without your patch (no top bar, no widgets). Other pages mostly work fine. Unfortunately, that’s not exactly a clean environment.

So I’ve tried to reproduce this on a more controled test system, but there it works as you described without the patch. Strange,…

However, if I reïnstall the patch, it breaks:
[HTTP/1.1 500 Internal Server Error 498ms] on http://<siturl>/wp-content/plugins/matomo/app/index.php?module=CoreHome&action=index&idSite=1&period=day&date=today
Unfortunately I didn’t find the time today to test further.

Is there a safe way to reïsntall the plugin on the prod environment without wiping the config & data? It probably makes sense to try to get a reproducable result.

Thanks,

Tim

Hi @tsteur,

Thanks, work perfectly!
Unfortunately the prod environment keeps behaving quick differently from a clean install.
We’re currently running a promo campaign for the main site till mid Februari, which limits my possibilities to do some test things directly on production.
I’m moving a backup from prod to a test system and test further there, but that might take some time.

I’ll keep you posted.

Kind regards,

Tim

Hi @tsteur,

So, finaly some progress 🙂

There were issue with the reverse proxy in front of the website (PURGE ALL was not clearing the full cache). After clearing directly on the reverse proxy, I’m now getting the same as you: still working, but with those errors in the console.

I’ve also managed to set up a copy on test. There I applied your fix.
There seems to be a small error in the version check (line 40).
My version reports as ‘5.6’, which makes that it is detected as 5.5 or older.
If I change ‘5.6.0-rc1’ by ‘5.6’, the fix seems to work:)

Kind regards,

Tim