CONCATENATE_SCRIPTS

Concat actually works properly for the majority of users, so you are sadly in the 10% minority who has conflicts.

Since you know this is one of your plugins, it would be best to figure out which one and bring it to the attention of that developer. Generally when you know it’s a plugin, it means a plugin has an error/bad JS, which should be fixed since it’s probably slowing your site down as well!

Well, I’m proud to be in the 10% then. ?? It’s not sad at all. My site runs well.

I don’t know that it’s a plugin. I honestly only said that because I knew the first reply would be, “it’s probably a plugin.” So I was trying to keep the focus on: “is this feature truly needed?” Especially on by default. So I went ahead and agreed with you and others who might reply (that it’s a plugin) in hopes that I might get a better response since that was out of the way. A better debate about this feature versus the very common find the plugin reply. I hope that makes sense.

How do you know that only 10% have this issue? Just due to not many people posting about this issue? If that’s the logic consider this:

Over the 18 years that I’ve used WordPress what I end up doing with WordPress issues is I learn to live with them. I don’t report them. Because I know I’ll get replies that amount to: it’s fine, you’re in the minority.

So, I bet any percentages people have in their heads are not accurate. Because, at the end of the day, people get tired of reporting issues and just use a different software or learn to live with things. Or change plugins (but this isn’t always an option or an option that can be done quickly). Or wait for the next update hoping something will start working again.

Now I’m getting deja vu. Like I posted about this here before. I probably have. I think you might have been the one that replied to that one too.

I try to stop myself from posting here as much as possible because I know any suggestion won’t be entertained. Or, there will be no replies at all. And this isn’t about you, this is how all online software communities work. I get it. “Moderators and developers are always right.”

May I summon the strength to not post here for a while. It wastes my time. I need to just focus on doing what I can with the Software.

How do you know that only 10% have this issue?

Of course there’s no way to be sure, but just with both the volume of overall reports and my own personal experience of having to only ever disable concat once until I figured out which plugin was causing it, reported it, and it was fixed the next day. I haven’t had to disable concat since.

From what I’ve seen around here, it’s always either a plugin, a theme, or lack of proper server resources.

The first two can be fixed, but only if you report it to the plugin or theme causing the problem.

The same problem here, i’m also one of the 10%.

Same here after the 6.3 update across several sites.

I have the same problem with version 6.4

maybe don’t ignore this problem so much?

None of the plugins created a conflict because I disabled all of them, it didn’t help,

I added

define( ‘CONCATENATE_SCRIPTS’, false );

and everything works now

• This reply was modified 10 months, 3 weeks ago by azurekonto77.

@azurekonto77 From your account name I deduct you’re running WP on an IIS-server too? Might that be the culprit?

No, it’s just an email name ?? WordPress is hosted on regular litespeed hosting

Just had this same issue with my subdomain multisite install built with roots.io trellis & bedrock upon updating to 6.4.2. Definitely NOT a plugin issue as I was able to reproduce on a staging environment without any plugins active. I can see specifically in dev tools the error is: refused to apply style from .../wp-admin/load-styles.php because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.

I guess I am going ahead with the solution to define( ‘CONCATENATE_SCRIPTS’, false );, as I see that fixes it on my staging environment.

Will monitor to see if this affects performance.

This happened on another one of our customers websites yesterday. The only file change I can see is an automatic update of the norwegian translation files for WooCommerce. No error in the logs.

The MIME types are the same for all the other sites on this server.

We’re now on WordPress 6.4.2.

I’m another user in the 10% community. All of a sudden the backend slowed down so much that it gave a timeout when editing pages. Entering the dashboard needed about one minute, the load-scripts.php is the cause.

Version 6.5.3-de (re-installed to be sure), template 2024, almost no plugins. Disabling them did not change anything, except a duplicate page plugin, which slows it down even in combination with define(‘CONCATENATE_SCRIPTS’, false ); in the wp-config file. Without this plugin the config mod fixes the problem.

I have another WP installation which is almost identical, running on the same host (same php version, same server settings etc.) without this problem. Only difference is the language (en). Runs fine without the config mod and even with the duplicate pages plugin.

A week ago everything worked fine.

Any ideas?

We’re running most installs on the Norwegian version. Could it be an issue with versions NOT in english?

Quick try: changing the backend language to en/US does not fix this problem.