"missing ) after argument list"

Huh! If that was the case, thousands of people would be having this problem. But they’re not. So whatever this is, it’s specific to your site. Have you tried:

– deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

– switching to the Twenty Eleven theme to rule out any theme-specific problems.

– resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

– re-uploading the wp-admin and wp-includes folders from a fresh download of WordPress.

Thanks and yes, we did all of those as a first attempt to resolve the issue.

We have many installs of wordpress and all work fine except for this one.

How would thousands have this issue if this was the case? If this issue prevalent in all WP installs, is that what you are saying?

If this issue prevalent in all WP installs, is that what you are saying?

Exactly that! If all your other installs work fine, it does beg the question – why is this one different? Granted you could have a corrupt wp-admin/js/common.js file but a corruption so specific that it just dropped an closing bracket has to be a million-to-one chance. Usually corrupted files are just code mush.

You could try re-uploading the wp-admin folder from a fresh download of WordPress to see if that helps. If not, it might be case of trying to work out what is different about this install.

Thanks for that, really weird though as I have tried uploading the admin only as well from a fresh copy. And again no change.

Will have to think further but I’m running out of ideas. Thanks.

Is this install on a different server to the others? Have you tried adding define('CONCATENATE_SCRIPTS', false ); to the bottom of your wp-config.php file (just before the require_once line)?

Thanks, it’s on the same server though.

I installed to a new domain name and it worked fine, so I’m wondering if the domain name would have anything to do with it? I wouldn’t expect so but could that play a part?

Nope – the domain name wouldn’t cause this. It has to be something within that site’s set-up.

I had the same problem after migrating from my localhost for a web server.

I noticed that there were differences between the load-scripts.php that was being generated by localhost and what was being generated by the web server. The web server was generating “double quotes” on some parts of que code!

THE SOLUTION: I compared both php.ini and noticed that on my web server the options of “magic_quotes” were enabled. Disable them (like on localhost’s php.ini) and problem solved!