We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Admin pannel scripts error on EE6.0.1 update installation

Development and Programming

Pavel's avatar
Pavel
1 posts
about 5 years ago
Pavel's avatar Pavel

I recently updated my site from EE5.4 to EE6.0.1 following the documentation and everything working fine except some scripts on the admin side.

I have two errors and nothing like a drop-down or switcher not working properly in the admin panel.

The first and persistent one:

Uncaught ReferenceError: _ is not defined
    Underscore 5
admin.php:7365:5

The second and just sometimes appear:

Uncaught ReferenceError: React is not defined
    <a> mywebsite.com/admin.php?S=...&D=cp&C=javascript&M=combo_load&plugin=ui.touch.punch&file=cp/date_picker,cp/perpage,cp/publish/entry-list,components/bulk_edit_entries,cp/publish/bulk-edit,fields/relationship/mutable_relationship,fields/relationship/relationship&v=1611744164:665
admin.php:665:1

Any ideas how I can fix them without to proceed to reinstall the latest version of EE?

Thanks a lot for your time and help!

       
Tom Jaeger's avatar
Tom Jaeger
449 posts
about 5 years ago
Tom Jaeger's avatar Tom Jaeger

Hi Pavel,

Thanks for getting in touch about this.

What version of PHP and MySQL are you currently running?

Also, just to throw it out there, for errors like this, you’ll generally see a faster response time in Slack. Theres currently just shy of 7,000 people in there, that are happy to lend a hand!

Thanks, -Tom Jaeger

       
Green Egg Media's avatar
Green Egg Media
111 posts
4 years ago
Green Egg Media's avatar Green Egg Media

For anyone finding this via Google, I also encountered an issue like this.

In my particular case, we were working with a Git repository that was ignoring vendor and it turns out that some of the JS that EE relies on was being stored in /themes/ee/cp/js/build/vendor/ (along with a few other paths).

The goal of ignoring vendor in our repo was to keep certain files out of the repository that would be created during a build pipeline. The solution was as simple as doing what we should have done in the first place - replacing vendor with a more precise path in .gitignore.

Your mileage may vary.

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.