robertneville73

You’re right. I re-downloaded WP2.1 and it had it in the right spot. Something was funky with my original tar file and it was missing a bunch of files.

Funny enough though, it turns out that there was another problem with one of my plug-ins: namely the king framework. They include a lite version of prototype.js in their plugin that seemed to stomp on the default one and it didn’t have all of the necessary functions so I had to change one of the files in that plugin to include the default version of the file instead of the one included with the plugin or I saw the same behavior.

I think I have everything playing nice now.

Thanks for the reply Otto. I don’t normally resort to hacking, but I’d already tried everything you just listed…with the exception of downloading the wp-scriptaculous.js file.

Just for completeness, I did everything you mentioned, in order. Since it’s not a live site, I redid the whole WP install, just to make sure and disabled all other plugins to rule-out that possibility.

Cleared the cache and did the ctrl-f5 as mentioned…I’m back to the beginning where the mouse cursor changes on a mouse-over, but click and drag doesn’t function.

Error console is giving me: ‘uncaught exception: script.aculo.us requires the Prototype JavaScript framework >= 1.5.0’. Now, this is what I was seeing before. When I inspect the protoype.js file, it says that it’s: “Version: ‘1.5.0_rc0′”.

All of the files are in the scriptaculous directory, there are no .js files in the widgets directory. All .js files are -rwxr-xr-x, so I don’t think it’s a permissions issue.

I know it’s not the ‘right’ way to solve whatever the underlying problem may be, but on a hunch, I moved the protoype.js up to the wp-includes/js directory and…..presto it works just fine now. I think I was on the right hack-track before but I was missing the wp-scriptaculous.js file or I just needed to reinstall everything from scratch. Either way, something’s definetly not right with WP2.1 + Widgets, out of the box – though I suppose that it could be something quirky about my install, though I don’t readily see what that could be…