Cannot click in magento admin panel

#1

Hi all amazing Magento-devs,
When I enter into my Magento admin panel ALL buttons are not-clickable. Nothing happeneswhen I try to click on different buttons.

I have tried cleaning cache and flush cache through Putty and also I have done the static:compile command. But no result, I cannot still click anywhere.
Any idea? Have you met this issue before?

Superthankful for some advice.

#2

Typically, you’ll find that you can’t click on a button because there has been an error whilst the page was rendering. Therefore, the page doesn’t finish loading and you can’t interact with everything.

These issues can occur after making a change to Magento (e.g. installing, updating, removing a module).

You should open Chrome Inspect Element (F12), select the Console tab and hit Refresh. The console will provide you with a hint as to why the page isn’t rendering correctly.

You probably won’t understand the issue. But the trick is to look for words and references that may point you in the right direction. Sometimes, this can be a line of code or a filename located in a folder.

Follow the trail…

#3

Thanks Craig, I followed your advice and I got nooo idea what this line or words mean :open_mouth:
Hope you can help me:

(index):8 Uncaught SyntaxError: Invalid or unexpected token
(index):1 Refused to execute script from 'https://magent-5277.bolt54.servebolt.com/admin_tpnqng/admin/dashboard/index/key/73210bd4c342da8fac6f31e8bdba6df16f653cf26ac903dff66bb974417f4b14/jquery.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
require.js:141 Uncaught Error: Script error for: jquery
http://requirejs.org/docs/errors.html#scripterror
    at makeError (require.js:166)
    at HTMLScriptElement.onScriptError (require.js:1681)
(index):1 Refused to execute script from 'https://magent-5277.bolt54.servebolt.com/admin_tpnqng/admin/dashboard/index/key/73210bd4c342da8fac6f31e8bdba6df16f653cf26ac903dff66bb974417f4b14/mage/backend/bootstrap.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
require.js:141 Uncaught Error: Script error for: mage/backend/bootstrap
http://requirejs.org/docs/errors.html#scripterror
    at makeError (require.js:166)
    at HTMLScriptElement.onScriptError (require.js:1681)
(index):1 Refused to execute script from 'https://magent-5277.bolt54.servebolt.com/admin_tpnqng/admin/dashboard/index/key/73210bd4c342da8fac6f31e8bdba6df16f653cf26ac903dff66bb974417f4b14/js/theme.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
require.js:141 Uncaught Error: Script error for: js/theme
http://requirejs.org/docs/errors.html#scripterror
    at makeError (require.js:166)
    at HTMLScriptElement.onScriptError (require.js:1681)
(index):1 Refused to execute script from 'https://magent-5277.bolt54.servebolt.com/admin_tpnqng/admin/dashboard/index/key/73210bd4c342da8fac6f31e8bdba6df16f653cf26ac903dff66bb974417f4b14/mage/adminhtml/globals.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
require.js:141 Uncaught Error: Script error for: mage/adminhtml/globals
http://requirejs.org/docs/errors.html#scripterror
    at makeError (require.js:166)
    at HTMLScriptElement.onScriptError (require.js:1681)
(index):1 Refused to execute script from 'https://magent-5277.bolt54.servebolt.com/admin_tpnqng/admin/dashboard/index/key/73210bd4c342da8fac6f31e8bdba6df16f653cf26ac903dff66bb974417f4b14/Magento_Ui/js/modal/confirm.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
require.js:141 Uncaught Error: Script error for: Magento_Ui/js/modal/confirm
http://requirejs.org/docs/errors.html#scripterror
    at makeError (require.js:166)
    at HTMLScriptElement.onScriptError (require.js:1681)
(index):1 Refused to execute script from 'https://magent-5277.bolt54.servebolt.com/admin_tpnqng/admin/dashboard/index/key/73210bd4c342da8fac6f31e8bdba6df16f653cf26ac903dff66bb974417f4b14/mage/adminhtml/grid.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
require.js:141 Uncaught Error: Script error for: mage/adminhtml/grid
http://requirejs.org/docs/errors.html#scripterror
    at makeError (require.js:166)
    at HTMLScriptElement.onScriptError (require.js:1681)
(index):1 Refused to execute script from 'https://magent-5277.bolt54.servebolt.com/admin_tpnqng/admin/dashboard/index/key/73210bd4c342da8fac6f31e8bdba6df16f653cf26ac903dff66bb974417f4b14/Magento_Catalog/catalog/product.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
require.js:141 Uncaught Error: Script error for: Magento_Catalog/catalog/product
http://requirejs.org/docs/errors.html#scripterror
    at makeError (require.js:166)
    at HTMLScriptElement.onScriptError (require.js:1681)
(index):1 Refused to execute script from 'https://magent-5277.bolt54.servebolt.com/admin_tpnqng/admin/dashboard/index/key/73210bd4c342da8fac6f31e8bdba6df16f653cf26ac903dff66bb974417f4b14/mage/backend/tabs.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.
require.js:141 Uncaught Error: Script error for: mage/backend/tabs
http://requirejs.org/docs/errors.html#scripterror
    at makeError (require.js:166)
    at HTMLScriptElement.onScriptError (require.js:1681)
#4

Yeah, that doesn’t really tell me much either. But the key piece of information there is:

because its MIME type (‘text/html’) is not executable, and strict MIME type checking is enabled.

Therefore, I have 2 guesses for the cause:

  • You recently amended an Apache Configuration file
  • You recently went into Production Mode

If the latter is true, try to regenerate your static content. Ideally, you should always run this after compiling:

bin/magento setup:static-content:deploy en_US sv_SE -f

Note: sv_SE assumes you’re still using that language

If that fails, you may have to manually clear your static files first:

rm -rf pub/static/*
rm -rf var
bin/magento setup:static-content:deploy en_US sv_SE -f

Note: Run all commands above as “magento” user from within the Magento root directory.

#5

Dear Craig,

Thanks a lot. Now I spent like 48 hours in a row with tech support at server host and theme developer. They say

Hello Maia

We have applied the solution provided by the developers you mentioned (which is the one you wrote to me Craig) on the website copy on our server:

###### Code:

newsit48@it39 [~/public_html]# php71 bin/magento deploy:mode:show
Current application mode: production. (Note: Environment variables may override this value.)
newsit48@it39 [~/public_html]# php71 bin/magento setup:static-content:deploy en_US sv_SE -f

Deploy using quick strategy
frontend/Magento/blank/en_US 2603/2603 ============================ 100% % 1 sec
adminhtml/Magento/backend/en_US 2473/2473 ============================ 100% % 1 sec
frontend/Magento/blank/sv_SE 2603/2603 ============================ 100% % 12 secs
adminhtml/Magento/backend/sv_SE 2473/2473 ============================ 100% % 11 secs
frontend/Magento/luma/en_US 2619/2619 ============================ 100% % 1 sec
frontend/CleverSoft/core/en_US 2645/2645 ============================ 100% % 0
frontend/Magento/luma/sv_SE 2619/2619 ============================ 100% % 14 secs
frontend/CleverSoft/core/sv_SE 2645/2645 ============================ 100% % 20 secs
frontend/CleverSoft/novetty/en_US 2758/2758 ============================ 100% % 5 secs
frontend/CleverSoft/novetty/sv_SE 2758/2758 ============================ 100% % 21 secs

Execution time: 101.1759250164

There is no change in the Magento admin area behaviour. Most of the sections are still inaccessible when the navigation buttons in the left menu are pressed.

The application mode is set to  **production** :

###### Code:

newsit48@it39 [~/public_html]# php71 bin/magento deploy:mode:show
Current application mode: production. (Note: Environment variables may override this value.)

So no result yet…Have you encountered this before? Seems so wierd!!
Thanks for any feedback.

Maia

#6

Not this exact issue. I have had similar issues, but they were related to modules that I’d installed or broke. I was able to narrow down where the issue was using the Console trick I mentioned before. Obviously, in your case the answer is not so obvious by the error message.

The next avenue of investigation would be:

  • Does the issue persist in Developer Mode?
  • What do the error logs say? (exception.log/system.log)
#7

Hi Craig,

Thanks a lot for the feedback. I got back to the dev team again :slight_smile:

#8

Bare in mind that the error will only be logged when you try to load an Admin page. This will help narrow down the log entries. So, just refresh the page whilst watching the logs or something to that effect.

#9

Thanks, I will give it some time trying and testing and I answer you back.