jQuery Problem

That line in load-scripts.php is..

function site_url() {}

It’s an empty function, i can’t see that being the source of your problem, load-scripts contains several empty functions.

What browser are you using? Have you tried another?

I get the error in Safari and Firefox. The code the error is happening on is this:

function tb_init(domChunk){
    jQuery(domChunk).live('click', tb_click);
}

That’s a thickbox function, it doesn’t run on the widget page (i’ve just checked on my install), so how did you come to relate this function to your issue using widgets?

Actually, the error shows no matter which page I load in admin. So, it prevents most javascript functions from operating such as loading the news feeds on the Dashboard. I just happened to notice the problem on the widgets page when I tried to move one.

The thickbox script should only be loading on given pages, not including the widgets page.

Try turning off concatenation and script compression to see if that helps, done by adding the following to your wp-config file.

define('CONCATENATE_SCRIPTS', false);

Hi all,

I got the same problem after I just installed the 3.01 >>

• I can’t drag and drop anymore my widgets on the dashboard page,
• I can’t drag and drop my widgets on the widget page
• Modalboxes doesn’t show anymore. The whole page is loaded in the browser instead. Quite annoying on the article pages when I try to insert an image

Surprisingly, I can drag and drop menus on the menu page

I tried Mark’ solution

define('CONCATENATE_SCRIPTS', false);

in my wp-config.php but nothing changed.

All my plugins are disabled.
This is a network installation.

Here is the console log on the dashboard:

load-scripts.php:2 ReferenceError: Can't find variable: jQuery
load-scripts.php:58 TypeError: Result of expression 'jQuery(domChunk).live' [undefined] is not a function

Any ideas ?

I think – on my case – this problem has something to do with the multi site update :
every blog I created after the update don’t have the javascrpit problem. My “legacy” blog is the only website where the problem described by macmage in the first post occurs. I guess this has something to do with the path (I had to fix the upload image folder path for the legacy blog).