Make WordPress Core

Opened 3 years ago

Last modified 18 months ago

#43369 new defect (bug)

Admin panel not fully loaded

Reported by: capoan Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version: 4.9.4
Component: Script Loader Keywords: close reporter-feedback
Focuses: javascript, administration Cc:



The error is on loading hoverIntent via /wp-admin/load-scripts.php URL. If I remove hoverIntent via URL, then is working good. I've eliminated it from script-loader.php and is working now good.

I've made the tests by removing all the plugins from the website. Also, the problem is related with 4.9.4 and webserver because on other servers that we have WordPress is working good.

The fronted is working good.

Change History (3)

#1 @SergeyBiryukov
3 years ago

  • Component changed from General to Script Loader
  • Keywords close reporter-feedback added
  • Summary changed from Admin pannel not fully loaded to Admin panel not fully loaded

Hi @capoan, welcome to WordPress Trac!

The error is on loading hoverIntent via /wp-admin/load-scripts.php URL.

What is the error message?

It sounds like the issue is specific to a particular environment. Could you repload wp-includes/js/hoverIntent.js just in case? Note the capital I, hoverIntent.js is not the same as hoverintent.js on Linux servers.

If that does not resolve the issue, please try the support forums for further troubleshooting.

#2 @capoan
3 years ago


Hosting is telling me that the problem is because of this:

This error is due to this error https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6389
Active IPS systems block access to that resource because of the above mentioned.
You can access the site via HTTPS and you will no longer encounter the error but the vulnerability will remain and the site can be attacked via HTTPS.

On this moment the website is up to date and I've tested with https and is working. I think it has to be a WordPress BUG.

#3 @desrosj
18 months ago

Hi @capoan,

Are you still experiencing this issue? I have been unable to locate similar reports, and I have been unable to reproduce the issue myself.

Note: See TracTickets for help on using tickets.