Admin Panel JQuery Includes

You already did that. The js in the includes directory is for your admin area. If you want your *theme* to use js, then you’re supposed to create a file within your theme directory, and call it in through your theme files.

I didn’t say it was fixed. What I said was that the js stuff in the /includes directory is for the *admin* area. if you edited the js stuff that’s inside the includes directory so the jQuery for your *theme* would work, you’ve just messed up your admin area (which, as per your question, you did.)

if there was an error in the jQuery for your *theme* them there was an error in that jQuery code that needed to be fixed. You shouldn’t have gone into the jQuery for the *admin* area (which is located in the /includes folder) and tried to mess with that. What you should have done is tried to fix the *theme* related jQuery code that belongs in your theme folder.

i.e. you fixed the wrong code, and messed it all up.

at least that’s what I’m getting from your question – that the jQuery you were using for your theme wouldn’t do what it needed to do. You say it kept “defaulting to the includes directory” – that sounds to me like you either put the code in the wrong place, or you didn’t use the right call in your header to find the file. So yes, it is here or there.

What you need to do now is reupload the files you messed with in the includes folder, and revert them back to what they were. Then figure out why the jQuery you put into your theme header was getting the error it was getting – rather than trying to rewrite WordPress.

When you’re working with the theme files, you stay in the wp-content/themes folder. You don’t go poking around in core code…you’re just asking to bang your head on a brick wall.

Well, WordPress and a static HTML site are two different things. There’s many things that could have gone wrong. I don’t know what you were trying to do, nor do I know what errors you were getting )you haven’t supplied any of that information) it could be that your static code was making calles with relative paths – that woudl be wrong, because wherever you are on your WP site, the relative path would change it would be right for one page and wrong for all others. it could be that you were trying to use something that conflicts with the core code. Who knows? You haven’t really told us much – save you were getting errors, and you think it would be best to rewrite core WP code than to try and figure out what’s conflicting with *your* code. but yes, you *can* have stuff working on a regular HTML site that will break using WP. That’s why, when you develop for WP, and you don’t want to do it in a live site, you have a testbed environment (either online or localhost) to do so.

To answer your original question, you will have to wade through all of the files in WordPress – starting with the JS stuff, to figure out where these things need to be changed. I’d put money on it that when you do, other errors will pop up related to the changes you just made, and you’ll wade through and try to fix those…in an endless cycle. OR you could just try and figure out why your original code is conflicting with WordPress. Fix your code – there’s nothing wrong with WP.