J-Admin: Warning! Internet Explorer should not be used for proper operation of the Administrator Backend. #37409

kyavuz54 · 2022-03-29T18:40:21Z

Problem identified

I'm getting "Warning! Internet Explorer should not be used for proper operation of the Administrator Backend." on Joomla 4.0.6 while I'm on Chrome. Frontend works just fine.

Proposed solution

I renamed .htaccess to htaccess.txt, but it didn't help.

Open questions

Any idea?

drmenzelit · 2022-03-29T19:06:51Z

Internet Explorer is dead, it should not be used for anything... Please use modern browsers like Firefox, Chrome, Edge, Brave, Vivaldi....

richard67 · 2022-03-29T19:16:52Z

Hmm, it looks as if there is no js and css loaded at all, and so that message about IE is not hidden like it should be. Please make sure to comment out the last section in your .htaccess file which is about using precomptessed js and css.

brianteeman · 2022-03-29T19:17:43Z

@drmenzelit as the user stated they are using chrome and the screenshot is chrome

The confusion is because when javascript and css etc does not load then you can see that message.

The screenshot does however explain exactly what the error is. which is what @richard67 said (while I was searching the docs site to try and find the detailed explanation)

richard67 · 2022-03-29T19:25:46Z

Not related to the issue, but you should update to the current version 4.1.1 as soon as this problem is fixed because your 4.0.6 is old and has security issues. There is nothing special with updating to 4.1.1, it is a normal update within the same major version, not such a big thing like a 3.10.x to 4.y.z update.

kyavuz54 · 2022-03-29T19:43:48Z

Yes, I'm on Chrome.

I did the suggested, so the bottom part of .htaccess went from this

to this

But, I still see the following

That is the plan to update if I can get this to work.

Any more ideas?

Hackwar · 2022-03-29T19:57:46Z

You have this only in the administrator? Not in the frontend? Do you maybe have an (outdated version of) Akeeba Admintools installed? Regardless, your browser can't load any JS/CSS, so you would have to find out why that is. It is not an issue of core Joomla. A hosting issue, a third party extension or a misconfiguration in htaccess somewhere...

Hackwar · 2022-03-29T19:59:02Z

I would assume that somehow you are encoding your content with gzip twice.

kyavuz54 · 2022-03-29T20:10:53Z

This happens only in the admin, not in the frontend.
Akeeba Admin Tools Core version is 7.1.1.

I don't see any other gzip related coding on .htaccess besides the ones that I commented out

I'll have to get in touch with the hosting.

richard67 · 2022-03-29T20:17:03Z

According to https://www.akeeba.com/download/admin-tools.html your version of admin tools is not the latest one.

kyavuz54 · 2022-03-29T22:24:22Z

This is weird.

I was able to go on the admin panel on my cell phone. I updated all extensions and the Joomla to 4.1.0 (which seems to be the only available version that I see after checking for a new update).

Unfortunately, I still get the same warning on Chrome, Firefox, Opera, and Edge "Warning! Internet Explorer should not be used for proper operation of the Administrator Backend."

Why don't JS/CSS files load on regular browser?

kyavuz54 · 2022-03-29T22:33:00Z

I restored files from a backup that is a month old. I renamed the .htaccess to htaccess.txt which brought me to the following:

Seems like I'm on the right track, but not all files load accurately.

Any suggestions?

Hackwar · 2022-03-29T22:36:00Z

Again, sounds like you have issues with a third party extension or your hosting, not with Joomla itself. I would advise to ask in the forum if your hoster can't help you.

kitepascal · 2022-03-29T23:10:40Z

Whats your gzip setting in configuration.php?

public $gzip = '0';

...and all .htaccess disabled (check also subdirectories, e.g. /media) should solve your problem.

A new inkognito browser window (close all inkognito windows before) is better for testing.

drmenzelit · 2022-03-30T05:23:57Z

@drmenzelit as the user stated they are using chrome and the screenshot is chrome

The confusion is because when javascript and css etc does not load then you can see that message.

The screenshot does however explain exactly what the error is. which is what @richard67 said (while I was searching the docs site to try and find the detailed explanation)

My bad, I didn't read properly

Hackwar · 2022-04-02T22:48:47Z

Any news, @kyavuz54? As we all said, it looks very much like a hosting issue, for example an additional htaccess in your administrator folder or some strange server configuration. I would say that this isn't a Joomla bug.

HLeithner · 2022-04-02T23:11:20Z

I'm closing this for now because it seems that is not a core issue, please ask in the forum for help. If you really think or found out that's core issue you can always reopen this issue.

jweaver0312 · 2022-04-15T17:03:14Z

I would have to disagree with the belief that it is not a core issue and the people saying its a hosting issue. If it were truly to be a hosting issue, then every browser in existence would be affected, not just Chromium based among others.

I'm having the same exact issue as the original reporter, except mine affects both the backend and frontend. I'm currently working on the .htaccess file commenting out section by section to narrow down a particular section causing it.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

jweaver0312 · 2022-04-15T17:21:03Z

These directives are only enabled if the Apache mod_headers module is enabled.

This section will check if a .gz file exists and if so will stream it

directly or fallback to gzip any asset on the fly

If your site starts to look strange after enabling this, and you see

ERR_CONTENT_DECODING_FAILED in your browser console network tab,

then your server is already gzipping css and js files and you don't need this

block enabled in your .htaccess

# Serve gzip compressed CSS files if they exist # and the client accepts gzip. RewriteCond "%{HTTP:Accept-encoding}" "gzip" RewriteCond "%{REQUEST_FILENAME}\.gz" -s RewriteRule "^(.*)\.css" "$1\.css\.gz" [QSA]

# Serve gzip compressed JS files if they exist
# and the client accepts gzip.
RewriteCond "%{HTTP:Accept-encoding}" "gzip"
RewriteCond "%{REQUEST_FILENAME}\.gz" -s
RewriteRule "^(.*)\.js" "$1\.js\.gz" [QSA]

# Serve correct content types, and prevent mod_deflate double gzip.
RewriteRule "\.css\.gz$" "-" [T=text/css,E=no-gzip:1]
RewriteRule "\.js\.gz$" "-" [T=text/javascript,E=no-gzip:1]

<FilesMatch "(\.js\.gz|\.css\.gz)$">
	# Serve correct encoding type.
	Header append Content-Encoding gzip

	# Force proxies to cache gzipped &
	# non-gzipped css/js files separately.
	Header append Vary Accept-Encoding
</FilesMatch>

Comment all this out and it'll be fine. The question then shifts to what I said prior, if it truly were a hosting issue, then every browser in existence would have this issue, but the fact of the matter is, not all browsers share in this issue, namely Safari. If the server is gzipping css and js files, then every browser in existence should inherently share the same issue.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

jweaver0312 · 2022-04-15T17:23:40Z

Reposting to make it look good, forgot to preview it before posting.

## These directives are only enabled if the Apache mod_headers module is enabled.
## This section will check if a .gz file exists and if so will stream it
##     directly or fallback to gzip any asset on the fly
## If your site starts to look strange after enabling this, and you see
##     ERR_CONTENT_DECODING_FAILED in your browser console network tab,
##     then your server is already gzipping css and js files and you don't need this
##     block enabled in your .htaccess
<IfModule mod_headers.c>
	# Serve gzip compressed CSS files if they exist
	# and the client accepts gzip.
	RewriteCond "%{HTTP:Accept-encoding}" "gzip"
	RewriteCond "%{REQUEST_FILENAME}\.gz" -s
	RewriteRule "^(.*)\.css" "$1\.css\.gz" [QSA]

	# Serve gzip compressed JS files if they exist
	# and the client accepts gzip.
	RewriteCond "%{HTTP:Accept-encoding}" "gzip"
	RewriteCond "%{REQUEST_FILENAME}\.gz" -s
	RewriteRule "^(.*)\.js" "$1\.js\.gz" [QSA]

	# Serve correct content types, and prevent mod_deflate double gzip.
	RewriteRule "\.css\.gz$" "-" [T=text/css,E=no-gzip:1]
	RewriteRule "\.js\.gz$" "-" [T=text/javascript,E=no-gzip:1]

	<FilesMatch "(\.js\.gz|\.css\.gz)$">
		# Serve correct encoding type.
		Header append Content-Encoding gzip

		# Force proxies to cache gzipped &
		# non-gzipped css/js files separately.
		Header append Vary Accept-Encoding
	</FilesMatch>
</IfModule>

Comment all this out and it'll be fine. The question then shifts to what I said prior, if it truly were a hosting issue, then every browser in existence would have this issue, but the fact of the matter is, not all browsers share in this issue, namely Safari. If the server is gzipping css and js files, then every browser in existence should inherently share the same issue. The question shifts to, why those browsers in specific.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

jweaver0312 · 2022-04-15T17:32:29Z

@Hackwar that seem to be a case but I tried with Joomla Gzip page compression on and off and nothing changed the behavior, only thing that helped was commenting that section of the .htaccess out.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

jweaver0312 · 2022-04-15T17:36:48Z

To original reporter: that might be a caching issue on your part where its still showing like that, on my instance, as soon as I do that to comment it out, that resolves it.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

Sandra97 · 2022-04-19T09:34:37Z

I just had this issue after transferring a site from the server of my hosting company to the server of the hosting company of my client. Commenting the section of the .htaccess solved the issue.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

brianteeman · 2022-04-19T10:28:58Z

what was the hosting company @Sandra97 I would like to find a way to display a helpful message on screen instead of the browser console but I dont have a host I can test this with (and failed to work out how to replicate it locally)

Sandra97 · 2022-04-19T10:35:25Z

The issue happened at GoDaddy

Jadzia · 2022-05-26T07:23:11Z

I am having the same issue, the code doesn't exist in the.htaccess and its the same in all browsers not just Chrome.
It's a bit hard to disable 3rd party components when you can't get in. Will post when I fix it.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

pearsony · 2022-07-17T13:13:57Z

Has a solution to this issue been posted? A client's website is still intermittently experiencing this issue.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

pearsony · 2022-07-17T13:46:59Z

I'm using Joomla 4.1.5

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

bomkallo · 2022-10-11T15:41:10Z

The solution is to change "gzip page compression" from enabled to disabled. It is in global configuration. Probably you're not able to access administrator area in normal way so you need to rename .htaccess or comment out last 10-30 lines or just open configuration.php and change public $gzip = TRUE;

Depends on hosting. If there is no styles under /administrator it means gzip compression is on and must be turned off as stated above.

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

bomkallo · 2022-10-11T15:42:14Z

PS: I mean $gzip = false; as stated above :)

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

pearsony · 2022-10-11T17:37:58Z

Unfortunately, all of my Joomla 4.x websites gzip set to off position. ~ Scott From: Peter ***@***.***> Sent: Tuesday, October 11, 2022 10:42 AM To: joomla/joomla-cms ***@***.***> Cc: pearsony ***@***.***>; Comment ***@***.***> Subject: Re: [joomla/joomla-cms] J-Admin: Warning! Internet Explorer should not be used for proper operation of the Administrator Backend. (Issue #37409) PS: I mean $gzip = false; as stated above :)

…

________________________________ This comment was created with the J!Tracker Application<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjoomla%2Fjissues&data=05%7C01%7C%7C7a280534c23247aff14008daab9f3279%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638010997474194615%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LUjdtTmODPLwU%2FhhgHFfbUnjMszr2RQPzQHiP8VXhwM%3D&reserved=0> at issues.joomla.org/tracker/joomla-cms/37409<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.joomla.org%2Ftracker%2Fjoomla-cms%2F37409&data=05%7C01%7C%7C7a280534c23247aff14008daab9f3279%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638010997474194615%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fnrs4fGnG%2BOGZfoapLZjjnCJ19iFCO2xQIzxDWoA2p0%3D&reserved=0>. - Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjoomla%2Fjoomla-cms%2Fissues%2F37409%23issuecomment-1274904959&data=05%7C01%7C%7C7a280534c23247aff14008daab9f3279%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638010997474194615%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ORNkGjdLvNbD237PwnHyMSw7efbiA%2FOEvLHQgPVKFTM%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACNGSQFZWHM4FQTTPKWBBB3WCWDGDANCNFSM5R7J3FAQ&data=05%7C01%7C%7C7a280534c23247aff14008daab9f3279%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638010997474194615%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=boapH4TWQgK7XZBCE%2FkbA1x6PA9xKPCnBRoz%2BKrVUPk%3D&reserved=0>. You are receiving this because you commented.Message ID: ***@***.******@***.***>>

jimmyxXx · 2024-04-13T15:24:13Z

So, which one is better - to comment off the gzip block in .htaccess as in jweaver0312's post, or to turn off gzip compression in joomla server configuration?

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/37409.}

joomla-cms-bot added the No Code Attached Yet label Mar 29, 2022

Quy added the Information Required label Apr 2, 2022

HLeithner closed this as completed Apr 2, 2022

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

J-Admin: Warning! Internet Explorer should not be used for proper operation of the Administrator Backend. #37409

J-Admin: Warning! Internet Explorer should not be used for proper operation of the Administrator Backend. #37409

kyavuz54 commented Mar 29, 2022

drmenzelit commented Mar 29, 2022

richard67 commented Mar 29, 2022

brianteeman commented Mar 29, 2022

richard67 commented Mar 29, 2022 •

edited

kyavuz54 commented Mar 29, 2022

Hackwar commented Mar 29, 2022

Hackwar commented Mar 29, 2022

kyavuz54 commented Mar 29, 2022

richard67 commented Mar 29, 2022

kyavuz54 commented Mar 29, 2022

kyavuz54 commented Mar 29, 2022

Hackwar commented Mar 29, 2022

kitepascal commented Mar 29, 2022 •

edited

drmenzelit commented Mar 30, 2022

Hackwar commented Apr 2, 2022

HLeithner commented Apr 2, 2022

jweaver0312 commented Apr 15, 2022

jweaver0312 commented Apr 15, 2022

jweaver0312 commented Apr 15, 2022

jweaver0312 commented Apr 15, 2022

jweaver0312 commented Apr 15, 2022

Sandra97 commented Apr 19, 2022

brianteeman commented Apr 19, 2022

Sandra97 commented Apr 19, 2022

Jadzia commented May 26, 2022

pearsony commented Jul 17, 2022

pearsony commented Jul 17, 2022

bomkallo commented Oct 11, 2022

bomkallo commented Oct 11, 2022

pearsony commented Oct 11, 2022 via email

jimmyxXx commented Apr 13, 2024

J-Admin: Warning! Internet Explorer should not be used for proper operation of the Administrator Backend. #37409

J-Admin: Warning! Internet Explorer should not be used for proper operation of the Administrator Backend. #37409

Comments

kyavuz54 commented Mar 29, 2022

Problem identified

Proposed solution

Open questions

drmenzelit commented Mar 29, 2022

richard67 commented Mar 29, 2022

brianteeman commented Mar 29, 2022

richard67 commented Mar 29, 2022 • edited

kyavuz54 commented Mar 29, 2022

Hackwar commented Mar 29, 2022

Hackwar commented Mar 29, 2022

kyavuz54 commented Mar 29, 2022

richard67 commented Mar 29, 2022

kyavuz54 commented Mar 29, 2022

kyavuz54 commented Mar 29, 2022

Hackwar commented Mar 29, 2022

kitepascal commented Mar 29, 2022 • edited

drmenzelit commented Mar 30, 2022

Hackwar commented Apr 2, 2022

HLeithner commented Apr 2, 2022

jweaver0312 commented Apr 15, 2022

jweaver0312 commented Apr 15, 2022

These directives are only enabled if the Apache mod_headers module is enabled.

This section will check if a .gz file exists and if so will stream it

directly or fallback to gzip any asset on the fly

If your site starts to look strange after enabling this, and you see

ERR_CONTENT_DECODING_FAILED in your browser console network tab,

then your server is already gzipping css and js files and you don't need this

block enabled in your .htaccess

jweaver0312 commented Apr 15, 2022

jweaver0312 commented Apr 15, 2022

jweaver0312 commented Apr 15, 2022

Sandra97 commented Apr 19, 2022

brianteeman commented Apr 19, 2022

Sandra97 commented Apr 19, 2022

Jadzia commented May 26, 2022

pearsony commented Jul 17, 2022

pearsony commented Jul 17, 2022

bomkallo commented Oct 11, 2022

bomkallo commented Oct 11, 2022

pearsony commented Oct 11, 2022 via email

jimmyxXx commented Apr 13, 2024

richard67 commented Mar 29, 2022 •

edited

kitepascal commented Mar 29, 2022 •

edited