theposterpreviouslyknownas

well, that example link you pasted is using a litle toy called lightbox, which isnt ajax. I know that doesnt answer your request, I just thought i would letcha know

you have files from both versions doing things.

You need to :

1. delete all the files inside wp-includes/
2. delete all the files inside wp-admin/

Not the files inside subdirectories, not the subdirectories themselves, JUST files.

then upload fresh copies of 2.1 files.

see my longer explanation of why in my last post in this thread:

https://www.ads-software.com/support/topic/102115?replies=11

and to answer that question, no you do not. You just need to delete the OLD files before you upload the NEW ones.

use the full url to the object (the .swf) both places that you call it.

welp, I went ahead with the change.

I noticed that line breaks were no longer being applied, so I made one small change to both the 2.0.x and the 2.1.x version to rectify that.

Permalink/Download page unchanged.

I need someone thats currently using this on either 2.0x or 2.1 to contact me if they would please. I found a bug in this and want to verify that its reproducable. I have the fix but need to check the other first.

email is whoo -(at)- village-idiot.org

Or if you want you can catch me on msn messenger via the following email:

whoooo and then put gmail.com at the end ?? (thats four oh’s btw) thanks!

I am running 2.0.7. THIS is what I did.

I took the same function that exists within 2.1 (ITS FIXED) and replaced the old fucntion. It works fine.

YOU DO NOT NEED TO RUN 2.1 TO FIX THAT HOLE.

This is the fucnction taken right out of 2.1, and it works perfectly within 2.0.7:


function wp_remote_fopen( $uri ) {
$timeout = 10;
$parsed_url = @parse_url($uri);
if ( !$parsed_url || !is_array($parsed_url) )
return false;
if ( !isset($parsed_url['scheme']) || !in_array($parsed_url['scheme'], array('http','https')) )
$uri = 'https://' . $uri;
if ( ini_get('allow_url_fopen') ) {
$fp = @fopen( $uri, 'r' );
if ( !$fp )
return false;
stream_set_timeout($fp, $timeout); // Requires php 4.3
$linea = '';
while( $remote_read = fread($fp, 4096) )
$linea .= $remote_read;
fclose($fp);
return $linea;
} else if ( function_exists('curl_init') ) {
$handle = curl_init();
curl_setopt ($handle, CURLOPT_URL, $uri);
curl_setopt ($handle, CURLOPT_CONNECTTIMEOUT, 1);
curl_setopt ($handle, CURLOPT_RETURNTRANSFER, 1);
curl_setopt ($handle, CURLOPT_TIMEOUT, $timeout);
$buffer = curl_exec($handle);
curl_close($handle);
return $buffer;
} else {
return false;
}
}

Its just fixed, it doesnt use any special additons from 2.1 and it would be nice if ppl gave decent advice instead of “working” to get ppl to upgrade to something they dont need to.

Im not neccessarily talking about you diane, btw, about the “working” thing, I just think ppl dont realize that they dont have to run that blasted bug ridden 2.1

attribute_escape() was introduced in 2.0.6, are you not upgraded to atleast 2.0.6?

Indeed you are not if the site in your profile is any indication.

>>I’m not about to subject myself to further grief by upgrading to WP 2.1 while it’s still in the state it’s in.

then upgrade to 2.0.7

follow the standard upgrade procedure to go from 2.0.4 > 2.0.6 then upload the couple new files that make up 2.0.7, then make the neccessary changes for that little hole.

piece of cake ??

validate_current_theme is defined inside wp-admin/admin-functions.php in 2.0.x and was moved to wp-includes/theme.php in 2.1.x

You need to delete the files you have inside wp-admin/ and reupload fresh copies – you have old files in there from the other version.

??